Repository navigation
Include readable user identity in activity and stream logs - #12
Merged
pushpinderbal merged 1 commit intoOct 19, 2026
Merged
Conversation
pushpinderbal
deleted the
feat/user-context-in-activity-and-stream-logs
branch
October 19, 2026 03:42
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.
Activity logs now include a readable
userfield alongside the stableuser_id: display name or preferred username when available, otherwise the internal ID. Requests without sign-in are labeledanonymous.Stream sessions retain their owner's logger, so readiness, processing, failures, seeks, stops, timeouts, and shutdown logs include the same user and session context after the original request has finished. Provider URLs, credentials, and raw upstream errors remain excluded.
Validation:
go test ./...,go build ./..., and the existing activity/authentication and FFmpeg lifecycle integration checks pass, including name/username/ID fallback and ownership across seeks and failures. No database migration is required.