Conversation
Because they yell at us because of blocked serialization nonsense
shellygr
approved these changes
Apr 15, 2026
Contributor
shellygr
left a comment
shellygr
left a comment
There was a problem hiding this comment.
discussed concerns etc. on slack but permitting the ship to sail
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.
ValidationError, and rethrows it as aToolInvocationError. So, whitelist theToolInvocationErrorto be passed back to the agents (THANKS LANGGRAPH)|when used as a regex character; the documentation intended the opposite. I've also seen the tool try to be used to find file names, clarifies this in the tool descriptionDeserializing unregistered type...error message the langgraph devs "helpfully" added to make sure we aren't pwned by someone with write access to our production database (???!?!?!?!)The way we accomplish 3 is... unfortunate and relies on an implementation detail that I'm sure the langgraph devs would prefer we didn't exploit. I would prefer the langgraph devs didn't play nanny and force us to rearchitect our whole application over a complete nothing security scenario.