fix(rnd): Added updated graph meta to include runs

[Swiftyos]

Background

Fixes the large number of requests on the monitoring page, by expanding the get graphs call to include minimal runs meta. Thus we get all the data for the monitoring page in a single request.

Also:

• Tidied up pyproject.toml file to remove none existent build steps
• Made sentry toggle able

[codiumai-pr-agent-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Possible Performance Issue The useEffect hook is called without dependencies, which may cause unnecessary re-renders. Consider adding the appropriate dependencies to the dependency array. Potential Memory Leak The setInterval is set up in a useEffect hook that depends on fetchAgents and agents. This might cause multiple intervals to be created if these dependencies change frequently. Consider using a useRef to store the interval ID and clear it properly.

[netlify]

✅ Deploy Preview for auto-gpt-docs ready!

Name	Link
🔨 Latest commit	c388385
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/66f1355849fb2e000887ef9a
😎 Deploy Preview	https://deploy-preview-8088--auto-gpt-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kcze]

This PR renames some things from flow to agent but there are still inconsistencies. I think using different words for the same thing is confusing for us and contributors.

[Swiftyos]

This PR renames some things from flow to agent but there are still inconsistencies. I think using different words for the same thing is confusing for us and contributors.

I agree, I was working on bring down the scope of concepts we have. We use Agent, Flow and Graph all interchangeable atm

Given we only talk to endusers with the term agent I was trying to standardise on that.

Would you like me to propagate the name change across the system?

[Swiftyos]

This PR renames some things from flow to agent but there are still inconsistencies. I think using different words for the same thing is confusing for us and contributors.

I agree, I was working on bring down the scope of concepts we have. We use Agent, Flow and Graph all interchangeable atm

Given we only talk to endusers with the term agent I was trying to standardise on that.

Would you like me to propagate the name change across the system?

I decided it was best to change the naming schema in a different PR

Can't find the request re-review button..

[majdyz]

I'm still seeing this:

Screen.Recording.2024-09-19.at.12.01.42.PM.mov

Also seeing another error:

Screen.Recording.2024-09-19.at.12.04.01.PM.mov

[majdyz]

oh nvm it's fixed on the latest changes

[Pwuts]

LGTM!

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

The base branch was changed.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[majdyz]

@Swiftyos This fix seems to be crucial.
I have resolved the conflict on this PR, try to rebase and let me know if it is working as expected.

[Swiftyos]

Tested these routes merging

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Edit an agent from monitor, and confirm it executes correctly