fix: missing current_role in build_messages_full + upstream sync#11
Merged
Conversation
build_messages_full used current_role at line 240 but never declared it as a parameter (unlike the sync build_messages). Caused NameError on every agent invocation after the upstream merge. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
NameError: current_role is not definedinbuild_messages_full— param existed in syncbuild_messagesbut was missed whenbuild_messages_fullwas merged with upstream changes. Caused every agent invocation to fail silently.upstream-drift.mdfor details.Test plan
nanobot.servicestarts and handles messages without NameErrortzfield🤖 Generated with Claude Code