[SERVER-22053] Insertion of Array with undefined/null components. Created: 04/Jan/16 Updated: 08/Jan/24 Resolved: 04/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | 3.2.14, 3.3.11 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Paul Reed | Assignee: | Waley Chen |
| Resolution: | Done | Votes: | 0 |
| Labels: | bkp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v3.2
|
||||||||||||||||||||||||
| Steps To Reproduce: | Previously to 3.2 when this happened var s = [] ) you would get a doc like this: { mys: [ null, 1] }now in v3.2 you get this document: { mys: [1] }So the data has shifted up an index. Is this a new BUG or an old BUG fixed - cannot find any reference to it elsewhere. ==== fyi: I think that there might be an insert between the map and reduction where the array is restructured. |
||||||||||||||||||||||||
| Sprint: | Platforms 18 (08/05/16) | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||
| Description |
|
Inserts of arrays with undefined/null content in positions are being treated differently in version 3.2. |
| Comments |
| Comment by Githook User [ 04/May/17 ] |
|
Author: {u'username': u'WaleyChen', u'name': u'Waley Chen', u'email': u'waleycz@gmail.com'}Message: (cherry picked from commit af198512c7dbb00442fb5115aeac661bf85535c8) lint fix |
| Comment by Githook User [ 04/Aug/16 ] |
|
Author: {u'username': u'WaleyChen', u'name': u'Waley Chen', u'email': u'waleycz@gmail.com'}Message: lint fix |
| Comment by Githook User [ 04/Aug/16 ] |
|
Author: {u'username': u'WaleyChen', u'name': u'Waley Chen', u'email': u'waleycz@gmail.com'}Message: |
| Comment by Kelsey Schubert [ 27/Jan/16 ] |
|
Hi paul.reed, Sorry for the delay publicly responding. We have identified that this bug was introduced by the switch from V8 to SpiderMonkey as the default JS engine ( Thank you for the clear reproduction steps, |
| Comment by Paul Reed [ 26/Jan/16 ] |
|
Any news this? |
| Comment by Paul Reed [ 04/Jan/16 ] |
|
Just checked and it is only when an item is undefined that the array is truncated. Nulls get passed correctly [ undefined, 1 ] inserts to [1] |