fix: patch duplicate starter messages #2123
Closed
Conversation
This file contains 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
sarahwooders
had a problem deploying
to
Deployment
GitHub Actions
Failure
mattzh72
approved these changes
Nov 30, 2024
sarahwooders
had a problem deploying
to
Deployment
GitHub Actions
Failure
…be the new code from the route
sarahwooders
had a problem deploying
to
Deployment
GitHub Actions
Failure
sarahwooders
had a problem deploying
to
Deployment
GitHub Actions
Failure
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.
Currently the server allows for multiple threads to load an agent, resulting in concurrent edits to the initial message sequence (duplicated init messages).
Note: this is not a complete solution, since anything that calls
server.load_agent(agent_id)should need to grab a lock, but I only patched a subset of routes.