[SERVER-6079] v8 and spidermonkey handle Timestamps differently Created: 13/Jun/12 Updated: 11/Jul/16 Resolved: 04/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Seems like v8 doesn't pass Timestamp objects from commands to the shell - instead is uses the object representation ( { t : #, i : # })? Basically the test was running a comparison of: Timestamp( 1000, 2 ) + "" == admin.runCommand( { getShardVersion : coll + "" }).version + "" In spidermonkey, both are timestamps. In v8, the second is an object, and the comparison fails. If nothing else, we should be consistent between both javascript engines. |
| Comments |
| Comment by auto [ 08/Apr/13 ] |
|
Author: {u'date': u'2013-04-08T16:50:58Z', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: |
| Comment by Shaun Verch [ 04/Apr/13 ] |
|
I think this should be backported because Spidermonkey did it correctly and this bug was found after v8 was made the default. |
| Comment by auto [ 04/Apr/13 ] |
|
Author: {u'date': u'2013-04-03T21:01:28Z', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: |