feat(seer): Add lightweight RCA clustering endpoint integration by yuvmen · Pull Request #112229 · getsentry/sentry

yuvmen · 2026-04-03T20:22:41Z

Integrate Seer's new /v0/issues/supergroups/cluster-lightweight endpoint for lightweight root cause analysis and supergroup clustering.

When a new error issue is created, if the org is in the supergroups.lightweight-enabled-orgs sentry-option, we send the issue's event data to Seer. Seer generates a lightweight RCA via a single LLM call and clusters the issue into supergroups based on embedding similarity. This is separate from the existing Explorer-based agentic RCA flow.

Changes:

Register supergroups.active-rca-source and supergroups.lightweight-enabled-orgs sentry-options
Add LightweightRCAClusterRequest type and make_lightweight_rca_cluster_request() API function
Add trigger_lightweight_rca_cluster() core function and Celery task
Add kick_off_lightweight_rca_cluster pipeline step in post_process for new error issues
Rename existing lightweight_rca.py → explorer_lightweight_rca.py to clarify it's the Explorer-based flow

Call Seer's new /v0/issues/supergroups/cluster-lightweight endpoint on new issue creation, gated per-org via sentry-options. This sends issue event data to Seer for lightweight root cause analysis and clustering into supergroups. Also renames the existing explorer-based lightweight RCA files to explorer_lightweight_rca to avoid confusion with the new direct endpoint-based clustering approach. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/sentry/seer/supergroups/lightweight_rca_cluster.py

Serialized event data from EventSerializer can contain non-string dict keys (integer keys in _meta.entries). Without this option orjson.dumps raises TypeError.

github-actions · 2026-04-03T21:11:28Z

Backend Test Failures

Failures on 35a6636 in this run:

tests/sentry/taskworker/test_config.py::test_all_instrumented_tasks_registered — log

[gw1] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/taskworker/test_config.py:120: in test_all_instrumented_tasks_registered
    raise AssertionError(
E   AssertionError: Found 1 module(s) with @instrumented_task that are NOT registered in TASKWORKER_IMPORTS.
E   These tasks will not be discovered by the taskworker in production!
E   
E   Missing modules:
E     - sentry.tasks.seer.lightweight_rca_cluster
E   
E   Add these to TASKWORKER_IMPORTS in src/sentry/conf/server.py

Without this registration the task won't be discovered by the taskworker in production.

src/sentry/seer/supergroups/lightweight_rca_cluster.py

github-actions · 2026-04-03T21:30:40Z

Backend Test Failures

Failures on b442df5 in this run:

tests/sentry/taskworker/test_config.py::test_import_paths — log

[gw0] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/taskworker/test_config.py:25: in test_import_paths
    __import__(path)
src/sentry/tasks/seer/lightweight_rca_cluster.py:10: in <module>
    @instrumented_task(
E   TypeError: instrumented_task() missing 1 required positional argument: 'namespace'

tests/sentry/test_devimports.py::test_startup_imports[sentry] — log

[gw1] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/test_devimports.py:121: in test_startup_imports
    validate_package(pkg, EXCLUDED, XFAIL)
tests/sentry/test_devimports.py:116: in validate_package
    raise AssertionError(ret.stdout)
E   AssertionError: /home/runner/work/sentry/sentry/src/sentry/spans/consumers/process_segments/enrichment.py:38: DeprecationWarning: ATTRIBUTE_NAMES.SENTRY_BROWSER_NAME is deprecated.
E     ATTRIBUTE_NAMES.SENTRY_BROWSER_NAME,
E   error importing sentry.tasks.seer.lightweight_rca_cluster:
E   
E   Traceback (most recent call last):
E     File "<string>", line 35, in <module>
E       __import__(name)
E       ~~~~~~~~~~^^^^^^
E     File "<string>", line 15, in _import
E       return orig(name, globals=globals, locals=locals, fromlist=fromlist, level=level)
E     File "/home/runner/work/sentry/sentry/src/sentry/tasks/seer/lightweight_rca_cluster.py", line 10, in <module>
E       @instrumented_task(
E        ~~~~~~~~~~~~~~~~~^
E           name="sentry.tasks.seer.lightweight_rca_cluster.trigger_lightweight_rca_cluster_task",
E           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E       ...<2 lines>...
E           taskworker_namespace=issues_tasks,
E           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E       )
E       ^
E   TypeError: instrumented_task() missing 1 required positional argument: 'namespace'

src/sentry/options/defaults.py

cvxluo · 2026-04-03T21:42:16Z

src/sentry/options/defaults.py

 )

+# Supergroups / Lightweight RCA
+register(


does it make sense to duplicate the options between here and seer? i thought the original plan was to have seer do this check

yea I was conflicted about it, I think that now I got options in Seer I can have protections there, but I also dont want to queue tasks for all issues for nothing, seems very wasteful... and now I can basically have both be controlled by the same repo so I think its ok to protect from both sides using same config

we could just do the check only in sentry the? not sure it makes sense to duplicate the options, especially if the options have exactly the same name + purpose

This option is used on the Seer side, not in Sentry. Remove it until it's actually needed here.

src/sentry/seer/supergroups/lightweight_rca_cluster.py

github-actions · 2026-04-03T22:11:07Z

Backend Test Failures

Failures on c02c388 in this run:

tests/sentry/taskworker/test_config.py::test_import_paths — log

[gw1] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/taskworker/test_config.py:25: in test_import_paths
    __import__(path)
src/sentry/tasks/seer/lightweight_rca_cluster.py:10: in <module>
    @instrumented_task(
E   TypeError: instrumented_task() missing 1 required positional argument: 'namespace'

tests/sentry/test_devimports.py::test_startup_imports[sentry] — log

[gw1] linux -- Python 3.13.1 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/test_devimports.py:121: in test_startup_imports
    validate_package(pkg, EXCLUDED, XFAIL)
tests/sentry/test_devimports.py:116: in validate_package
    raise AssertionError(ret.stdout)
E   AssertionError: /home/runner/work/sentry/sentry/src/sentry/spans/consumers/process_segments/enrichment.py:38: DeprecationWarning: ATTRIBUTE_NAMES.SENTRY_BROWSER_NAME is deprecated.
E     ATTRIBUTE_NAMES.SENTRY_BROWSER_NAME,
E   error importing sentry.tasks.seer.lightweight_rca_cluster:
E   
E   Traceback (most recent call last):
E     File "<string>", line 35, in <module>
E       __import__(name)
E       ~~~~~~~~~~^^^^^^
E     File "<string>", line 15, in _import
E       return orig(name, globals=globals, locals=locals, fromlist=fromlist, level=level)
E     File "/home/runner/work/sentry/sentry/src/sentry/tasks/seer/lightweight_rca_cluster.py", line 10, in <module>
E       @instrumented_task(
E        ~~~~~~~~~~~~~~~~~^
E           name="sentry.tasks.seer.lightweight_rca_cluster.trigger_lightweight_rca_cluster_task",
E           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E       ...<2 lines>...
E           taskworker_namespace=issues_tasks,
E           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E       )
E       ^
E   TypeError: instrumented_task() missing 1 required positional argument: 'namespace'

The instrumented_task decorator requires `namespace` not `taskworker_namespace`, and doesn't accept `queue` or `max_retries`.

GroupEvent.group is typed as non-optional, so the None check is unreachable and mypy flags it.

…uster The org eligibility check is already done in the pipeline step before scheduling the task, so there's no need to check again in the function itself.

src/sentry/tasks/post_process.py

cvxluo · 2026-04-06T22:46:54Z

src/sentry/seer/signed_seer_api.py


+class LightweightRCAClusterRequest(TypedDict):
+    group_id: int
+    issue: dict[str, Any]


Suggested change

issue: dict[str, Any]

group: dict[str, Any]

Seer has this thing where issue is the word used in APIs, I am mimicking IssueSummary endpoint here, and its in other places as well, the model used in code there is IssueDetails, and so theres this weird thing of like Issue is the model, group_id is the number it gets...

cvxluo · 2026-04-06T22:47:25Z

src/sentry/tasks/seer/lightweight_rca_cluster.py

+    namespace=issues_tasks,
+)
+def trigger_lightweight_rca_cluster_task(group_id: int, **kwargs) -> None:
+    from sentry.seer.supergroups.lightweight_rca_cluster import trigger_lightweight_rca_cluster


does this import need to be in the func?

kick_off_seer_automation does it as well, I think its to avoid circular definitions

are you sure? kick_off_seer_automation is defined in post process and everything there has imports inside the functions, but all the other tasks in this folder don't follow that pattern

oh yea youre right, I had in mind like its in a different place, removing it

cvxluo · 2026-04-06T22:50:28Z

tests/sentry/seer/supergroups/test_lightweight_rca_cluster.py

+            trigger_lightweight_rca_cluster(self.group)
+
+    @patch("sentry.seer.supergroups.lightweight_rca_cluster.make_lightweight_rca_cluster_request")
+    def test_passes_viewer_context(self, mock_request):


do we have this type of test on the other seer endpoints?

hmm not really, guess it doesnt make sense, ill remove

cvxluo · 2026-04-06T22:51:36Z

tests/sentry/seer/supergroups/test_lightweight_rca_cluster.py

+from sentry.testutils.cases import TestCase
+
+
+class TriggerLightweightRCAClusterTest(TestCase):


shouldn't we have a test for the end to end actual flow? e.g. that triggering an event that creates a new issue will cause trigger_lightweight_rca_cluster to be sent?

agreed, will add

looked into it a bit, none of the other tests actually do this, as it forces you to sort of force the task to run synchronously and no tests do that right now, gonna follow the established pattern of asserting on the delay call being made, and letting the task tests verify that it does what is needs

cvxluo · 2026-04-06T22:52:05Z

src/sentry/conf/server.py

    "sentry.workflow_engine.tasks.cleanup",
    "sentry.tasks.seer.explorer_index",
    "sentry.tasks.seer.context_engine_index",
+    "sentry.tasks.seer.lightweight_rca_cluster",


we should probably name this lightweight_rca_embedding or just lightweight rca?

its like the command - to trigger clustering, because I basically treat the task as not a task to generate lgithweight-rca and a side effect of clustering, but instead of purposely triggering clustering, because before we didnt even save the lightweight-rca.
The endpoint I added is even called /cluster-lightweight, so thats like the command here, so I think the name fits. Does that make sense? I dont feel strongly about it though, just want it all to be coherent

maybe it should be more explicit like just "trigger_supergroup_clustering_lightweight"

i also don't feel too strongly, i think a slightly more consistent name would be 'lightweight rca embedding' / 'lightweight rca generation' but i think cluster also fits

I prefer cluster to both of these I think, like embedding is kinda technical, its not what the caller really intends, and generation is sort of inaccurate because of the way we set it up where the point is to cluster by lightweightRCA - not to generate it, we didnt even save the generated RCA until we realized we need it for resummarization, so its like a side effect now.

Just so were all on the same page - I am just trying to be consistent with the way I phrased and treated it up until now, I even leaned in the direction of making it all about lightweight RCA generation and the clustering being a side effect, but went the other way around in the API and flow, so I think we should stay consistent.

cvxluo · 2026-04-06T22:52:52Z

src/sentry/seer/supergroups/lightweight_rca_cluster.py

+    Sends issue event data to Seer, which generates a lightweight root cause analysis
+    and clusters the issue into supergroups based on embedding similarity.
+    """
+    event = group.get_recommended_event_for_environments()


shouldn't we always only have one event for this group, since we run this when the issue is created? just confused on any situation where we'd have >1 event

yea probably no need for this protection, will change to get_latest_event()

cvxluo · 2026-04-06T22:54:51Z

src/sentry/tasks/seer/lightweight_rca_cluster.py

+    from sentry.seer.supergroups.lightweight_rca_cluster import trigger_lightweight_rca_cluster
+
+    try:
+        group = Group.objects.get(id=group_id)


don't we have the group in post_process when we pass it here? do we need another fetch?

its standard for these tasks, you cant pass a model into them, they gotta refetch

cvxluo · 2026-04-06T22:56:53Z

src/sentry/tasks/seer/lightweight_rca_cluster.py

+
+@instrumented_task(
+    name="sentry.tasks.seer.lightweight_rca_cluster.trigger_lightweight_rca_cluster_task",
+    namespace=issues_tasks,


not necessarily blocking, is this the right namespace? i see that issues_tasks is technically labeled for 'issueplatform', while ingest_errors_postprocess_tasks exists and might fit slightly better

- Remove viewer_context test (not tested on other seer endpoints) - Switch to get_latest_event() since this runs on new issue creation - Change task namespace to ingest_errors_postprocess_tasks - Add post_process pipeline tests verifying task dispatch gating: dispatched when org enabled + new issue, skipped otherwise

No circular dependency exists, so the function-level import is unnecessary.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 87ecf74. Configure here.}

src/sentry/tasks/seer/lightweight_rca_cluster.py

cvxluo · 2026-04-07T17:22:08Z

tests/sentry/tasks/test_post_process.py

+
+    @patch("sentry.tasks.seer.lightweight_rca_cluster.trigger_lightweight_rca_cluster_task.delay")
+    def test_kick_off_lightweight_rca_cluster_skips_when_not_new(self, mock_task):
+        event = self.create_event(


i'm not sure, but isn't there a helper for creating an event and triggering the entire event lifecycle, including post process? basically, is there a way we remove the call_post_process_group while having the option enabled and have this test pass?

if there is I (and claude) couldnt find it, theres this , which saves a new event and triggers some stuff related to the group save but not post processing.
From what I can tell call_post_process_group is the way its done around other tests

cvxluo · 2026-04-07T17:23:34Z

tests/sentry/seer/supergroups/test_lightweight_rca_cluster.py

+        assert len(body["issue"]["events"]) == 1
+
+    @patch("sentry.seer.supergroups.lightweight_rca_cluster.make_lightweight_rca_cluster_request")
+    def test_raises_on_seer_error(self, mock_request):


similar to other test, do seer callers have this sort of test?

hmm actually they dont, this was generated as a response to some check I made though its sort of a good verification that if the request fails we throw something, however it did make me notice that the task itself just does logger.exception and swallows the error, which I think I will change - I want the task to fail outright, I think we agreed on this already in some other place.
So I am adding a raise there, regarding this test I feel like its harmless, dont mind removing

cvxluo · 2026-04-07T17:24:47Z

src/sentry/seer/signed_seer_api.py

+    return make_signed_seer_api_request(
+        seer_autofix_default_connection_pool,
+        "/v0/issues/supergroups/cluster-lightweight",
+        body=orjson.dumps(body, option=orjson.OPT_NON_STR_KEYS),


curious, what is this orjson option?

its to allow dict keys that are non string, in this case integers - from what I understand when we send event data it contains these kind of keys and its requried that we allow it, the issue summary endpoint does the same thing for the same reason I believe

Log the exception for Sentry visibility, then re-raise so the task is marked as failed in monitoring.

…ight-rca-cluster # Conflicts: # src/sentry/seer/signed_seer_api.py

This task makes an external API call with a 30s timeout, so it shouldn't run on the postprocess worker pool. Use ingest_errors_tasks to match generate_summary_and_run_automation which has the same dispatch pattern.

…ting (#112436) Add `rca_source` parameter to supergroup query APIs so Seer knows which embedding space (explorer vs lightweight) to query from. The source is determined by the `organizations:supergroups-lightweight-rca-clustering` feature flag. Also replaces the `supergroups.lightweight-enabled-orgs` sentry-option with this feature flag for both: - **Write path**: post_process task dispatch for lightweight RCA clustering - **Read path**: supergroup query endpoints (details + by-group) This is consistent with how all other supergroup features are gated (via feature flags, not options). Depends on #112229 (merged).

) Integrate Seer's new `/v0/issues/supergroups/cluster-lightweight` endpoint for lightweight root cause analysis and supergroup clustering. When a new error issue is created, if the org is in the `supergroups.lightweight-enabled-orgs` sentry-option, we send the issue's event data to Seer. Seer generates a lightweight RCA via a single LLM call and clusters the issue into supergroups based on embedding similarity. This is separate from the existing Explorer-based agentic RCA flow. **Changes:** - Register `supergroups.active-rca-source` and `supergroups.lightweight-enabled-orgs` sentry-options - Add `LightweightRCAClusterRequest` type and `make_lightweight_rca_cluster_request()` API function - Add `trigger_lightweight_rca_cluster()` core function and Celery task - Add `kick_off_lightweight_rca_cluster` pipeline step in post_process for new error issues - Rename existing `lightweight_rca.py` → `explorer_lightweight_rca.py` to clarify it's the Explorer-based flow --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

…ting (#112436) Add `rca_source` parameter to supergroup query APIs so Seer knows which embedding space (explorer vs lightweight) to query from. The source is determined by the `organizations:supergroups-lightweight-rca-clustering` feature flag. Also replaces the `supergroups.lightweight-enabled-orgs` sentry-option with this feature flag for both: - **Write path**: post_process task dispatch for lightweight RCA clustering - **Read path**: supergroup query endpoints (details + by-group) This is consistent with how all other supergroup features are gated (via feature flags, not options). Depends on #112229 (merged).

github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 3, 2026

vercel bot deployed to Preview April 3, 2026 20:23 View deployment

yuvmen force-pushed the yuvmen/feat/lightweight-rca-cluster branch from a949cd4 to 1b7c082 Compare April 3, 2026 21:00

vercel bot deployed to Preview April 3, 2026 21:02 View deployment

sentry-warden bot reviewed Apr 3, 2026

View reviewed changes

src/sentry/seer/supergroups/lightweight_rca_cluster.py Show resolved Hide resolved

fix(seer): Add OPT_NON_STR_KEYS to lightweight RCA cluster request

98a5f16

Serialized event data from EventSerializer can contain non-string dict keys (integer keys in _meta.entries). Without this option orjson.dumps raises TypeError.

fix(seer): Register lightweight RCA cluster task in TASKWORKER_IMPORTS

a3bbef2

Without this registration the task won't be discovered by the taskworker in production.

vercel bot deployed to Preview April 3, 2026 21:15 View deployment

yuvmen marked this pull request as ready for review April 3, 2026 21:20

yuvmen requested review from a team as code owners April 3, 2026 21:20

sentry bot reviewed Apr 3, 2026

View reviewed changes

src/sentry/seer/supergroups/lightweight_rca_cluster.py Show resolved Hide resolved

cursor bot reviewed Apr 3, 2026

View reviewed changes

src/sentry/options/defaults.py Outdated Show resolved Hide resolved

cvxluo reviewed Apr 3, 2026

View reviewed changes

ref(seer): Remove unused supergroups.active-rca-source option

6f9d2d1

This option is used on the Seer side, not in Sentry. Remove it until it's actually needed here.

vercel bot deployed to Preview April 3, 2026 21:56 View deployment

cursor bot reviewed Apr 3, 2026

View reviewed changes

src/sentry/seer/supergroups/lightweight_rca_cluster.py Outdated Show resolved Hide resolved

fix(seer): Use correct namespace param for instrumented_task

4905a86

The instrumented_task decorator requires `namespace` not `taskworker_namespace`, and doesn't accept `queue` or `max_retries`.

vercel bot deployed to Preview April 3, 2026 22:15 View deployment

fix(seer): Remove unreachable None check on GroupEvent.group

c984fcf

GroupEvent.group is typed as non-optional, so the None check is unreachable and mypy flags it.

vercel bot deployed to Preview April 3, 2026 22:49 View deployment

ref(seer): Remove duplicate org check from trigger_lightweight_rca_cl…

2b84529

…uster The org eligibility check is already done in the pipeline step before scheduling the task, so there's no need to check again in the function itself.

vercel bot deployed to Preview April 6, 2026 18:20 View deployment

sentry bot reviewed Apr 6, 2026

View reviewed changes

src/sentry/tasks/post_process.py Show resolved Hide resolved

cvxluo reviewed Apr 6, 2026

View reviewed changes

yuvmen added 2 commits April 6, 2026 17:05

ref(seer): Move import to top level in lightweight RCA cluster task

87ecf74

No circular dependency exists, so the function-level import is unnecessary.

vercel bot deployed to Preview April 7, 2026 17:12 View deployment

cursor bot reviewed Apr 7, 2026

View reviewed changes

src/sentry/tasks/seer/lightweight_rca_cluster.py Outdated Show resolved Hide resolved

cvxluo approved these changes Apr 7, 2026

View reviewed changes

fix(seer): Re-raise exceptions in lightweight RCA cluster task

ce103c2

Log the exception for Sentry visibility, then re-raise so the task is marked as failed in monitoring.

vercel bot deployed to Preview April 7, 2026 18:15 View deployment

Merge remote-tracking branch 'origin/master' into yuvmen/feat/lightwe…

aa18de9

…ight-rca-cluster # Conflicts: # src/sentry/seer/signed_seer_api.py

vercel bot deployed to Preview April 7, 2026 20:46 View deployment

ref(seer): Use ingest_errors_tasks namespace for lightweight RCA task

4270ced

This task makes an external API call with a 30s timeout, so it shouldn't run on the postprocess worker pool. Use ingest_errors_tasks to match generate_summary_and_run_automation which has the same dispatch pattern.

vercel bot deployed to Preview April 7, 2026 22:06 View deployment

cvxluo approved these changes Apr 7, 2026

View reviewed changes

yuvmen merged commit 615581d into master Apr 7, 2026
77 checks passed

yuvmen deleted the yuvmen/feat/lightweight-rca-cluster branch April 7, 2026 22:35

yuvmen mentioned this pull request Apr 7, 2026

feat(seer): Add rca_source to supergroup queries with feature flag gating #112436

Merged

		from sentry.testutils.cases import TestCase


		class TriggerLightweightRCAClusterTest(TestCase):

Uh oh!

Conversation

yuvmen commented Apr 3, 2026

Uh oh!

Uh oh!

github-actions bot commented Apr 3, 2026

Backend Test Failures

Uh oh!

Uh oh!

github-actions bot commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Backend Test Failures

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Backend Test Failures

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cursor bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Apr 3, 2026 •

edited

Loading

github-actions bot commented Apr 3, 2026 •

edited

Loading