-
Notifications
You must be signed in to change notification settings - Fork 273
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 key format for node #568
Conversation
The change looks awsome, Is there a migration strategy to migrate production db gradually? |
This pull request introduces 2 alerts when merging 5924e7e into 9cf5d7a - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging 99aeb4b into ae4aeee - view on LGTM.com new alerts:
|
I don't know yet, I'll look into it after fixing all the tests |
This pull request introduces 2 alerts when merging 33ceaf3 into ae4aeee - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging ca2ac94 into 797c8a9 - view on LGTM.com new alerts:
|
node.go
Outdated
} | ||
|
||
var _ cache.Node = (*Node)(nil) | ||
|
||
var dmm = []byte{226, 95, 219, 92, 42, 16, 81, 37, 50, 22, 7, 121, 82, 211, 57, 104, 2, 130, 61, 76, 80, 124, 97, 236, 13, 231, 44, 35, 206, 183, 207, 214} |
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.
what's this?
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.
It's for debugging, I'll remove it
This pull request introduces 2 alerts when merging 68ebd97 into 797c8a9 - view on LGTM.com new alerts:
|
closing this |
closing this |
No description provided.