Skip to content
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

Exception occurred when publish/rollback namespaces with gray release #4563

Closed
3 tasks done
nobodyiam opened this issue Sep 11, 2022 · 1 comment · Fixed by #4564
Closed
3 tasks done

Exception occurred when publish/rollback namespaces with gray release #4563

nobodyiam opened this issue Sep 11, 2022 · 1 comment · Fixed by #4564

Comments

@nobodyiam
Copy link
Member

  • I have checked the discussions
  • I have searched the issues of this repository and believe that this is not a duplicate.
  • I have checked the FAQ of this repository and believe that this is not a duplicate.

Describe the bug

When publish/rollback namespaces with gray release, the operation failed with the error message java.lang.IllegalStateException: Expected BEGIN_ARRAY but was NUMBER at line 1 column 20 path $..

The stacktrace in server log is as follows:

com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was NUMBER at line 1 column 20 path $.
	at com.google.gson.Gson.fromJson(Gson.java:975)
	at com.google.gson.Gson.fromJson(Gson.java:928)
	at com.google.gson.Gson.fromJson(Gson.java:877)
	at com.ctrip.framework.apollo.biz.service.ReleaseService.getBranchReleaseKeys(ReleaseService.java:333)

To Reproduce
Steps to reproduce the behavior:

  1. Create a grayscale version for some namespace, e.g. application
  2. Change some value in the grayscale version and publish the grayscale version
  3. Change some value in the main version
  4. Publish or rollback the main version, then you will see the error

Expected behavior
The publish/rollback operations should work with no error.

Screenshots
image

Additional Details & Logs

  • Version: 2.1.0-SNAPSHOT
@nobodyiam
Copy link
Member Author

It seesm related to #4502

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 a pull request may close this issue.

1 participant