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

[CLI] fix nil pointer issue in domain migration command rendering #5378

Merged
merged 4 commits into from
Aug 29, 2023

Conversation

shijiesheng
Copy link
Contributor

What changed?

  • correct empty response
  • refactor long running checker a little and add long running definition in the output

Why?

Empty response should include Value field otherwise it's going to cause nil pointer error in the rendering.

How did you test it?
tested locally

Potential risks

Release notes

Documentation Changes

@@ -332,12 +336,20 @@ func (d *domainMigrationCLIImpl) migrationDynamicConfigCheck(c *cli.Context) Dom
currResp, err := d.frontendAdminClient.GetDynamicConfig(ctx, currRequest)
if err != nil {
// empty to indicate N/A
currResp = &types.GetDynamicConfigResponse{}
currResp = &types.GetDynamicConfigResponse{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it might be worth creating a global empty variable

@shijiesheng shijiesheng enabled auto-merge (squash) August 29, 2023 15:50
@shijiesheng shijiesheng merged commit 99daa45 into uber:master Aug 29, 2023
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.

3 participants