[IOTDM-33] "child" and "latest" of container does not work properly Created: 14/Sep/15 Updated: 04/Apr/17 Resolved: 04/Apr/17 |
|
| Status: | Resolved |
| Project: | iotdm |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Cangji Wu | Assignee: | Juraj Kosmel |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4305 |
| Priority: | Normal |
| Description |
|
If the container has an attribute “mni”, let’s say 1, And I notice that the creating contentInstance still shows "success" and the parent container does updated (the "st" and "lt" updated), but the "ch" stop updating. You can try it yourself with the following collection. https://www.getpostman.com/collections/943a20019fec1abb7231 How to test: My python script that can create ContentInstance each second. Not sure whether this was caused by setting the "mni". |
| Comments |
| Comment by Lionel Florit [ 22/Feb/17 ] |
|
can't replicate the scenario below. It is possible this has been fixed |
| Comment by Juraj Kosmel [ 04/Apr/17 ] |
|
can't reproduce |