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

fix: properly use --trace flag #16827

Merged
merged 4 commits into from
Jul 4, 2023
Merged

fix: properly use --trace flag #16827

merged 4 commits into from
Jul 4, 2023

Conversation

julienrbrt
Copy link
Member

@julienrbrt julienrbrt commented Jul 4, 2023

Description

blocked on #16825
using a pseudo version for now to at least fix the issue with the trace flag.
the pseudo dep will be bump after #16829.


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

@julienrbrt julienrbrt added backport/v0.47.x PR scheduled for inclusion in the v0.47's next stable release backport/v0.50.x PR scheduled for inclusion in the v0.50's next stable release labels Jul 4, 2023
@julienrbrt julienrbrt changed the title fix: properly use --trace flag fix: properly use --trace flag Jul 4, 2023
@julienrbrt julienrbrt marked this pull request as ready for review July 4, 2023 17:08
@julienrbrt julienrbrt requested a review from a team as a code owner July 4, 2023 17:08
Copy link
Contributor

@alexanderbez alexanderbez left a comment

Choose a reason for hiding this comment

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

LGTM!

@julienrbrt julienrbrt added this pull request to the merge queue Jul 4, 2023
Merged via the queue into main with commit 8d80df8 Jul 4, 2023
@julienrbrt julienrbrt deleted the julien/fix-trace branch July 4, 2023 19:14
mergify bot pushed a commit that referenced this pull request Jul 4, 2023
(cherry picked from commit 8d80df8)

# Conflicts:
#	CHANGELOG.md
mergify bot pushed a commit that referenced this pull request Jul 4, 2023
(cherry picked from commit 8d80df8)

# Conflicts:
#	CHANGELOG.md
#	go.mod
#	go.sum
#	server/util.go
#	simapp/go.mod
#	simapp/go.sum
#	tests/go.mod
#	tests/go.sum
julienrbrt added a commit that referenced this pull request Jul 4, 2023
Co-authored-by: Julien Robert <julien@rbrt.fr>
julienrbrt added a commit that referenced this pull request Jul 4, 2023
Co-authored-by: Julien Robert <julien@rbrt.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.47.x PR scheduled for inclusion in the v0.47's next stable release backport/v0.50.x PR scheduled for inclusion in the v0.50's next stable release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants