-
Notifications
You must be signed in to change notification settings - Fork 74
Refactor shared storage. #98
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
Signed-off-by: mathetake <takeshi@tetrate.io>
Signed-off-by: mathetake <takeshi@tetrate.io>
Signed-off-by: mathetake <takeshi@tetrate.io>
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.
Could you avoid mixing big refactoring / moving code with bug fixes? While I don't mind the refactoring, it makes it impossible to review the fix.
right. Thanks. I will narrow down this PR scope only to refactoring and adding tests |
Signed-off-by: mathetake <takeshi@tetrate.io>
@PiotrSikora updated the PR description and title, and made ready for review! PTAL |
Thanks! Since, as you noted, they are completely independent, should we split them into |
I will split them! Thanks for the comment |
Signed-off-by: mathetake <takeshi@tetrate.io>
Signed-off-by: mathetake <takeshi@tetrate.io>
Signed-off-by: mathetake <takeshi@tetrate.io>
Signed-off-by: mathetake <takeshi@tetrate.io>
This is just split + tests, right? No code changes? |
YES, no code changes |
Thanks! |
refactor the shared storage code:
In a sequel PR, I would tackle the leakage issue