This repository was archived by the owner on Sep 24, 2025. It is now read-only.
Fix java serialization conflict during agent update #688
Conversation
This file contains hidden or 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
junoyoon
changed the title
junoyoon
approved these changes
Nov 11, 2020
songeunwoo
approved these changes
Nov 11, 2020
imbyungjun
approved these changes
Nov 11, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
After clean up all of the codes, the agent update message mistakenly became not-compatible b/w current controller and old agent. It's because the generated serialVersionUIDs were different from previous version. so I roll back the
AgentUpdateGrinderMessageto make compatibility of old version agents.