Skip to content

feat: add shared failure-kind registry - #2728

Draft
ananthsub wants to merge 1 commit into
NVIDIA-NeMo:mainfrom
ananthsub:ansubramania/failure-kind-registry
Draft

feat: add shared failure-kind registry#2728
ananthsub wants to merge 1 commit into
NVIDIA-NeMo:mainfrom
ananthsub:ansubramania/failure-kind-registry

Conversation

@ananthsub

@ananthsub ananthsub commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add an optional failure_kind machine key to BaseVerifyResponse while allowing namespaced environment extensions
  • register active failure strings already produced on main and reserve vocabulary from the in-flight recovery PRs
  • deliberately keep retryability, delivery state, policy attribution, and masking out of the registry because those vary per failure event

Test plan

  • uv run --extra dev pre-commit run --files nemo_gym/failure_kinds.py nemo_gym/base_resources_server.py tests/unit_tests/test_failure_kinds.py tests/unit_tests/test_base_resources_server.py
  • uv run --extra dev pytest tests/unit_tests/test_failure_kinds.py tests/unit_tests/test_base_resources_server.py -q

Give rollout tooling stable machine-readable failure keys while keeping masking and retry policy on individual failure records. Reserve vocabulary for in-flight recovery changes so producers converge before the strings become public artifact contracts.

Signed-off-by: Ananth Subramaniam <ansubramania@nvidia.com>
@ananthsub
ananthsub marked this pull request as draft August 24, 2026 20:57
@copy-pr-bot

copy-pr-bot Bot commented Aug 24, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

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.

1 participant