Repository navigation
Describe actual published Nexus caller coverage - #181
Merged
Merged
Conversation
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
2 participants
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.
Part of #122.
The Nexus inventory still describes the published SDK workflow as admission-only. Its existing workers now execute terminal results, handled typed failure, direct target cancellation, caller SIGKILL/replacement and backend interruption in all four PHP/Python caller/service directions, in same and cross namespaces.
Describe those actual checks and provide the existing GitHub Actions command and artifact inspection path. Keep waiting-caller cancellation propagation, external payload recovery, embedded execution and complete-manifest qualification open under Workflow #753. The focused workflow's success does not change missing full-suite cells into passes.
Documentation only. Existing published evidence includes Server runs 38150642914, 38151756740, 38154473976, 38185586993 and 38189317511. No fixture, package tuple or runtime behavior changes, and no new experiment or controller.