Repository navigation
Conversation
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
1 participant
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.
Enrolled engines attach a control service and write gate containing thread locks. PredBat debug downloads and periodic history serialize nonexcluded instance members, so the new service caused TypeError: cannot pickle '_thread.lock' object. Exclude both live controller objects through the shared debug/state filter, preserving normal debug data and keeping runtime credentials outside serialization.
Based on #5515. Regression invokes actual UserInterface.create_debug_yaml with real service/gate objects and a synthetic credential; output loads, ordinary fields survive, both objects and credential are absent. All30 control/service cases and pre-commit checks pass. GitNexus staged detection: two expected files, LOW; new-test insertion is attributed to the adjacent unchanged registry runner by the base index. Actual debug path impact HIGH (two direct callers, three scheduled/debug flows), reviewed before the narrow exclusion edit. No production changes.