Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@yanlinly
Copy link
Collaborator

Please do not create a Pull Request without creating an issue first.

What is the purpose of the change

merge 1.3.0 Beta

Brief changelog

[#2530] [#2758] Consistency protocol abstraction
[#2560] Nacos-client : ServerHttpAgent builds the unnormalized URL 
[#2569] Change NamingProxy#reqAPI method throw exception log describe
[#2577] Fix naming client http read timeout and connect timeout properties
[#2638] Support https
[#2647] Modify config service md5 generation method 
[#2661] Keep query criteria when config detail return to config list
[#2761] ProtocolManager class's getCpProtocol()/getApProtocol() method ' codes can be optimized.
[#2697] Fix the problem that properties have empty lines and cannot be edited
[#2733] Support service change event
[#2738] Tenant legality verification. #2785
[#2740] Modify the way of get remote state
[#2664] UI add groupName parameter
[#2765] Optimize MemberUtils class's kRandom method 

Verifying this change

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
  • Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
  • Run mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.

chuntaojun and others added 30 commits March 26, 2020 12:06
Change NamingProxy#reqAPI method throw exception log describe
[ISSUE#2577] Fix naming client http read timeout and connect timeout properties
zongtanghu and others added 24 commits May 11, 2020 18:13
…ure_tenant_verify

# Conflicts:
#	client/src/test/java/com/alibaba/nacos/client/BeatReactorTest.java
#	config/src/main/java/com/alibaba/nacos/config/server/controller/ConfigController.java
#	config/src/main/java/com/alibaba/nacos/config/server/service/PersistService.java
#	config/src/main/java/com/alibaba/nacos/config/server/utils/ParamUtils.java
refactor: jraft node removal logic optimization
@yanlinly yanlinly requested a review from chuntaojun May 15, 2020 10:48
mvn clean package -Pit-test
@yanlinly yanlinly requested a review from TsingLiang May 15, 2020 11:02
@yanlinly yanlinly merged commit 2cf0d40 into master May 15, 2020
@chuntaojun chuntaojun linked an issue May 26, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

nacos-config-client 里面的info日志输出过于平凡