Skip to content

fix(tracing): actually use span on permissioning #48

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

Merged
merged 4 commits into from
Jul 2, 2025

Conversation

Evalir
Copy link
Member

@Evalir Evalir commented Jul 2, 2025

We were not actually entering the span, so the logs show up pretty empty.

We were not actually entering the span, so the logs show up pretty empty.
Copy link
Member Author

Evalir commented Jul 2, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@Evalir Evalir enabled auto-merge (squash) July 2, 2025 10:26
@Evalir Evalir requested review from rswanson and prestwich July 2, 2025 10:26
@Evalir Evalir merged commit 0414b72 into main Jul 2, 2025
7 checks passed
#[error(
"builder not permissioned for this slot: requesting builder {0}, permissioned builder {1}"
)]
NotPermissioned(String, String),
Copy link
Member Author

Choose a reason for hiding this comment

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

@prestwich you ended up being right here that the messages on this error should've been made more useful. This was merged but we can keep working on this on a new PR.

return Err(BuilderPermissionError::NotPermissioned);
return Err(BuilderPermissionError::NotPermissioned(
sub.to_owned(),
self.current_builder().sub.to_owned(),
Copy link
Member

Choose a reason for hiding this comment

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

subs are not secrets right @rswanson

Copy link
Member

Choose a reason for hiding this comment

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

correct

@@ -187,6 +194,8 @@ where

info!("builder permissioned successfully");

drop(guard);

this.inner.call(req).await
Copy link
Member

Choose a reason for hiding this comment

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

should we instrument this future with the perms span?

@prestwich
Copy link
Member

ugh didn't see this was merged before commenting

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