Refactored and improved PythonCodeStructuredTool, SearXNGTool, and RunnableExecutor

[goliath-yamon]

PythonCodeStructuredTool

• Inputs for function arguments description will be automatically added when updating tool_code.
• Added an input for global variables without having to declare them as arguments of function.
• Types of function arguments can be declared any types.
• If you want to declare custom Enum, you can declare it into tool_code.

SearXNGTool

• Created this tool to search through SearXNG.

RunnableExecutor

• Allowed the output to be streamed (The agent must have chat model such as LLM).
• Changed the build method to asynchronous.

[github-actions]

Pull Request Validation Report

This comment is automatically generated by Conventional PR

Whitelist Report

Whitelist	Active	Result
Pull request is a draft and should be ignored	✅	❌
Pull request is made by a whitelisted user and should be ignored	❌	❌
Pull request is submitted by a bot and should be ignored	✅	❌
Pull request is submitted by administrators and should be ignored	❌	❌

Result

Pull request does not satisfy any enabled whitelist criteria. Pull request will be validated.

Validation Report

Validation	Active	Result
All commits in this pull request has valid messages	❌	✅
Pull request does not introduce too many changes	❌	✅
Pull request has mentioned issues	❌	✅
Pull request has valid branch name	❌	✅
Pull request should have a non-empty body	✅	✅
Pull request has a valid title	✅	❌

Result

Pull request is invalid.

Reason

• Pull request title does not follow the desired pattern

_{Last Modified at 08 Aug 24 04:42 UTC}

[aws-amplify-sa-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-3239.dmtpw4p5recq1.amplifyapp.com

[YamonBot]

For RunnableExecutor, we are using LangChain's streaming attribute, which doesn't seem to be captured by the tracer since it is neither a callback nor an output parser. I would like to know the core team's opinion on separating this into a dedicated AgentStreamingExecutor.

[ogabrielluiz]

I think what you could do is use the callbacks's methods for each type of event.

[ogabrielluiz]

Hey @goliath-yamon

Sorry for the other PR ^^"

The RunnableExectutor needs some work it seems but the others look good to me. Let me know if you want to split them up into different PRs.

Also, if you create a new branch on your fork, it is easier for us to make any fixes

[goliath-yamon]

Hey @ogabrielluiz

Thank you for your answer.

Yes, if you can split them, do that please :)

After this, I will create a new branch to fix any issues or create any features.