fix(frontend): Prevent errors in Sentry LaunchDarkly flag handler from breaking the app

[seer-by-sentry]

Changes 🏗️

Fixes BUILDER-496. The issue was that: Sentry's LaunchDarkly integration failed to validate _url type before calling indexOf, causing a TypeError.

• Updates @sentry/nextjs from 10.15.0 to 10.20.0.
• Implements a defensive wrapper around Sentry's LaunchDarkly flag handler to catch and prevent errors from breaking the application. This involves creating a createSafeLaunchDarklyFlagHandler function that attempts to build the Sentry handler and wraps it in a try-catch block. If building the handler or executing it results in an error, the error is logged to the console, but the error is prevented from propagating and breaking the application.

This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 2067983

Not quite right? Click here to continue debugging with Seer.

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • N/A

Example test plan

• 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
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

For configuration changes:

• .env.default is updated or already compatible with my changes
• docker-compose.yml is updated or already compatible with my changes
• I have included a list of my configuration changes in the PR description (under Changes)

Examples of configuration changes

• Changing ports
• Adding new services that need to communicate with each other
• Secrets or environment variable changes
• New or infrastructure changes such as databases

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	9046070
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/68f6a754f54656000891eb33

[github-actions]

This PR targets the master branch but does not come from dev or a hotfix/* branch.

Automatically setting the base branch to dev.

[deepsource-io]

Here's the code health analysis summary for commits eba67e0..9046070. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	❗ 1 occurence introduced	View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

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

[AutoGPT-Agent]

Thanks for this PR to fix the Sentry LaunchDarkly integration issue. A couple of items need attention before this can be merged:

1. The checklist in the PR description isn't fully completed. Please check the "N/A" box in the test plan section, or provide an actual test plan if appropriate.

2. There appear to be backend changes in backend/util/metrics.py (commenting out LaunchDarkly integration code) that aren't mentioned in your PR description. These changes seem potentially significant as they disable LaunchDarkly integration on the backend. Please update your PR description to explain why these changes are necessary and how they relate to the frontend fix.

Once these items are addressed, the PR should be ready for review again.

[AutoGPT-Agent]

Thank you for this PR to fix the Sentry LaunchDarkly flag handler issue! The changes look good overall, with a clear defensive programming approach to prevent errors from breaking the application.

A couple of notes:

1. The PR description clearly explains the frontend changes, but doesn't mention the backend changes (commenting out LaunchDarkly integration in backend/util/metrics.py). Could you please explain the rationale for these changes?

2. For changes like this that don't directly impact user-facing functionality, marking the test plan as N/A is reasonable. However, it might be helpful to note how we can verify the fix works (e.g., by checking Sentry for absence of these errors after deployment).

Otherwise, the approach of creating a defensive wrapper around the Sentry LaunchDarkly flag handler is a solid fix for this issue.

[github-actions]

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

[majdyz]

@ntindle @Pwuts this will clash with https://github.com/Significant-Gravitas/AutoGPT-Agent-Generator/blob/master/agent_builder.py