Timestamp value is represented incorrectly (All versions) #1159

Closed
dmumladze opened this Issue Aug 17, 2016 · 8 comments

Comments

Projects
None yet
3 participants
@dmumladze

This issue has been spotted in all version and reported for version 8 previously. The issue is in mongo shell it's Timestamp(1454752004, 743), but Robomongo displays it as Timestamp(6248112280970461, 743), which is exactly 4294967.296 times more than what it's suppose to be.

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Aug 17, 2016

Collaborator

@August2008 thanks for reporting! I managed to reproduce the issue. We will fix it during the next releases as now we are working on new Robomongo version with SSL feature. We will get back to you with any news!

Collaborator

juliashibalko commented Aug 17, 2016

@August2008 thanks for reporting! I managed to reproduce the issue. We will fix it during the next releases as now we are working on new Robomongo version with SSL feature. We will get back to you with any news!

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
Collaborator

juliashibalko commented Aug 17, 2016

@dmumladze

This comment has been minimized.

Show comment
Hide comment
@dmumladze

dmumladze Nov 22, 2016

This is still not fixed as of 0.9.0.

This is still not fixed as of 0.9.0.

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Nov 26, 2016

Collaborator

Hi @dmumladze , we are really sorry for delay. We have been snowed under for some time to deliver some critical features. We delivered SSL and now we are focused on delivering Replica Sets and Export/Import asap. This ticket is tagged as "major", we will provide a fix as soon as we have a chance.

Collaborator

simsekgokhan commented Nov 26, 2016

Hi @dmumladze , we are really sorry for delay. We have been snowed under for some time to deliver some critical features. We delivered SSL and now we are focused on delivering Replica Sets and Export/Import asap. This ticket is tagged as "major", we will provide a fix as soon as we have a chance.

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Nov 26, 2016

Collaborator

Also, original ticket #501 is tagged as "high vote" which makes it more likely to be fixed sooner than other issues.

Collaborator

simsekgokhan commented Nov 26, 2016

Also, original ticket #501 is tagged as "high vote" which makes it more likely to be fixed sooner than other issues.

@dmumladze

This comment has been minimized.

Show comment
Hide comment
@dmumladze

dmumladze Dec 15, 2016

In the meantime the workaround to show correct date is to divide by 4294967.296:

print(new Date(Timestamp(6363665786204061/4294967.296, 2).t/1000))

In the meantime the workaround to show correct date is to divide by 4294967.296:

print(new Date(Timestamp(6363665786204061/4294967.296, 2).t/1000))

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Dec 19, 2016

Collaborator

@dmumladze , thanks a lot for sharing. Best Regards.

Collaborator

simsekgokhan commented Dec 19, 2016

@dmumladze , thanks a lot for sharing. Best Regards.

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Apr 27, 2017

Collaborator

Hi @dmumladze ,
There are some fixes related to Timestamp type on latest release Robomongo 1.0.
I hope it will solve your problem:
https://robomongo.org/download
http://blog.robomongo.org/robomongo-1-0/ -> section "c. Bug fixes"

Collaborator

simsekgokhan commented Apr 27, 2017

Hi @dmumladze ,
There are some fixes related to Timestamp type on latest release Robomongo 1.0.
I hope it will solve your problem:
https://robomongo.org/download
http://blog.robomongo.org/robomongo-1-0/ -> section "c. Bug fixes"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment