Repository navigation
Fix Canvas reply hook startup with SDK 1.56 - #35
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
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.
SDK 1.56 adds a keyword-only
run_slotargument toEventService.send_message. The factory reply hook rejected that signature and prevented the Canvas Agent Server from starting. Forward the original run-slot permit and check hook installation against the real EventService during both image build and regression testing.Validation: 673 regressions passed; Ruff and exact-release secret scan passed; committed source matches the retained IntentBond evidence (external semantic review remains pending). The corrected deployed controller returns HTTP 200 from Agent Server readiness, its saved workflows match the source, and the original six schedules are restored.