harden runtime recovery and observability - #220
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Summary
Root causes
The affected paths mixed per-attempt and overall timeout budgets, allowed normal MCP refreshes to bypass a scheduled reconnect, and treated some failed scheduled or A2A outcomes as immediately retryable without accurate classification. A test also inherited the production managed-browser default and leaked a Docker sidecar on every full suite run.
The CI follow-up was caused by newly reported npm advisories in existing dependency locks. Safe transitive releases fixed the Desktop and most Web findings. The remaining React Router advisories covered all published 7.x releases, so the dashboard now uses the audited 8.3.0 package and direct imports.
Impact
Long provider calls can complete their configured retry/fallback policy, broken MCP servers no longer reconnect on every prompt, scheduled external failures stop hot-looping, memory retrieval decisions become observable without logging content or memory identifiers, and the test suite no longer creates persistent browser containers. Web and Desktop dependency audits now report zero vulnerabilities.
Validation
uv run pytest -quv run ruff checkon all changed Python filesuv run black --checkon all changed Python filesgit diff --checknpm ci && npm audit --audit-level=moderate && npm run build && npm testinwebappnpm ci && npm audit --audit-level=moderate && npm run build && npm testindesktop