Rft : merge 1.4 #716
Merged
Rft : merge 1.4 #716
Conversation
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
2、fix some nacos config bug
Update Nacos SDK version
Merge pull request apache#548 from lzp0412/1.4
fix not inovke nacos destroy when graceful shutdown
Fix: apollo data change listener
…rn error immediately
Ftr: Update getty and hessian2
# Conflicts: # common/constant/key.go # common/url.go # config_center/apollo/impl.go # config_center/apollo/listener.go # config_center/nacos/client.go # config_center/nacos/listener.go # go.mod # go.sum # protocol/rest/rest_invoker.go # registry/nacos/registry.go # registry/protocol/protocol.go
AlexStocks
approved these changes
Aug 16, 2020
|
@zouyx pls fix the travis failure. |
Patrick0308
approved these changes
Aug 16, 2020
Fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: