-
Notifications
You must be signed in to change notification settings - Fork 189
Setting deterministic encoding id output, just sorting the keys #303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hi, I tried myself with cmd |
Sure, let me do the update :) |
Please don't forget to sign our CLA https://www.mongodb.com/legal/contributor-agreement |
Hi @coderGo93 removed the skipImportTest function, and it worked, previous execution failed with the capacity error, but that's independent |
@leofigy Thank you so much, indeed there are not errors about import state id or related, if there are similar error about capacity, probably need to change the region to |
@coderGo93 let's do that work, fix any tests not using larger regions and ensure existing project/new project is use to avoid conflicts, in another PR. We can create a Jira ticket for it and then schedule some time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Please have Abraham create a ticket for the work noted but not yet covered to fix tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
behaviour found by Edgar, sometimes the encodeStateID function generates a different ID with the same input.
This is given it encodes iterating over a map, and maps are unordered, the iteration sequence is not ensure.
So quick fix, sort the keys and access in that way to encode the ID.
Link to any related issue(s):
Type of change:
Required Checklist:
Further comments