-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: change type ID to Bytes #8
Open
shiyasmohd
wants to merge
1
commit into
edgeandnode:main
Choose a base branch
from
shiyasmohd:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Small caveat with this function, there are some cases (unsure if it happens in this particular subgraph though) where you can end up with ID collision by using this approach (no separator when joining IDs).
It happened in the activity subgraph, where we had an ID generation logic that took an address and 2 numbers (which I can't recall if it was an address + log index and a counter, or the other way around).
You could have multiple collisions as long as
logIndex.concat(counter)
would be equals, which can happen in many different ways, like having a log index of 11 and a count equals to 0, and a log index of 1 and a count equals to 10.There are 2 different ways of avoiding such collisions, one is to simply use a separator (when using strings it was often times quite easy since you simple used
-
and that's it, but with bytes you can't, so you need to use a random set of characters that you know) or use fixed bytes length for each different type of data (that way, if you know you are having 32 bytes for each number, 11 + 0 and 1 + 10 won't collide, since the padding will be different).