Repository navigation
Conversation
Seer endpoints read the caller through `sentry.auth.principal`: user ids sent to Seer, run lookups and coding-agent polling use `acting_user_id()`; autofix, push-changes and issue summary get `acting_user()`; the agent-approve grant uses `require_user()`. - A service account can start and read autofix runs (new test), and issue summary, issue-view titles, chat suggestions and supergroups send Seer no user id instead of a service-account id. Continuing or updating a chat and search-agent state deny it like token callers. - Users, agents and token callers see no change. Left: `organization_agent_token.py` passes the caller to `resolve_minting_principal`, which should reject callers with no user explicitly; today a service account is denied only because its id fails as an int.
github-actions
Bot
added
the
Scope: Backend
Contributor
Sentry Snapshot Testing
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seer endpoints read the caller through
sentry.auth.principal: user ids sent to Seer, run lookups and coding-agent polling useacting_user_id(); autofix, push-changes and issue summary getacting_user(); the agent-approve grant usesrequire_user().Left:
organization_agent_token.pypasses the caller toresolve_minting_principal, which should reject callers with no user explicitly; today a service account is denied only because its id fails as an int.mypy allowlist: 83 → 70 files.