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

jobspb: mark ResolvedSpan_BoundaryType as SafeValue #137375

Merged

Conversation

andyyang890
Copy link
Collaborator

This patch marks jobspb.ResolvedSpan_BoundaryType as a SafeValue
so that it won't be redacted in the logs.

Informs #128597

Release note: None

@andyyang890 andyyang890 requested review from rharding6373, a team and xinhaoz and removed request for a team and xinhaoz December 13, 2024 02:07
@andyyang890 andyyang890 requested review from a team as code owners December 13, 2024 02:07
@andyyang890 andyyang890 requested review from kyle-a-wong and kev-cao and removed request for a team December 13, 2024 02:07
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@andyyang890 andyyang890 added backport-23.2.x Flags PRs that need to be backported to 23.2. backport-24.1.x Flags PRs that need to be backported to 24.1. backport-24.2.x Flags PRs that need to be backported to 24.2 backport-24.3.x Flags PRs that need to be backported to 24.3 labels Dec 13, 2024
Copy link
Collaborator

@rharding6373 rharding6373 left a comment

Choose a reason for hiding this comment

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

:lgtm: Nice!

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @kev-cao and @kyle-a-wong)

This patch marks `jobspb.ResolvedSpan_BoundaryType` as a SafeValue
so that it won't be redacted in the logs.

Release note: None
@andyyang890 andyyang890 force-pushed the 20241212-unredact-boundary-type branch from 8ccc1ce to 2e66bb2 Compare December 13, 2024 18:51
@andyyang890
Copy link
Collaborator Author

TFTR!

bors r=rharding6373

Copy link

blathers-crl bot commented Dec 13, 2024

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 2e66bb2 to blathers/backport-release-23.2-137375: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.2.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-23.2.x Flags PRs that need to be backported to 23.2. backport-24.1.x Flags PRs that need to be backported to 24.1. backport-24.2.x Flags PRs that need to be backported to 24.2 backport-24.3.x Flags PRs that need to be backported to 24.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants