Repository navigation
Conversation
rius.mark_run_skipped(reason) and Observation.mark_skipped(reason) set rius.run.skipped_reason on a recording AGENT span, so Rius's empty-run detection reports a run that had nothing to do on purpose as informational instead of a warning. The reason is whitespace-collapsed and cut to 200 characters; it is metadata, so it survives capture_content=False. Any other span is left unmarked and the call returns False.
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.
Why
Rius's empty-run detection (CF-05) flags a finished, OK agent run with no LLM or tool call when the agent usually does work. A run that had nothing to do on purpose (empty queue, a guard deciding no work is needed) needs a way to say so. Linear: RIUS-1917.
What
rius.mark_run_skipped(reason)marks the current span;Observation.mark_skipped(reason)marks a held one. Both setrius.run.skipped_reasononly on a recording AGENT span and returnTrue; any other span (or none) returnsFalsewith a debug log, never raises (reliability contract). An empty/whitespace reason raisesValueError, a non-stringTypeError.capture_content=Falseand masking. The README section says to keep it operational and never put user input or secrets in it.rius/run.pyasRUN_SKIPPED_REASONfor now. It is planned in rius-semconv (feat: plan rius.run.skipped_reason, the intentional-skip marker on an agent root rius-semconv#121); after this merges, that row flips toshipped, a semconv release follows, and the SDK syncs the generated constant and drops the literal.Backend side: glassflow/argus-core#782 reads the marker (bounded, sanitized, quoted), excludes marked runs from baselines and reports them as info.
Testing
uv run ruff check .,ruff format --check .,mypy,pytest: 3145 passed. Newtests/test_run_skipped.py: current AGENT span,@observeagent, heldObservationinside a child span, non-agent span, no span, empty and non-string reasons, oversized reason cut, marker survives content masking.