handle ctx cancel before handling read errors in streaming by akshaydeo · Pull Request #3522 · maximhq/bifrost

akshaydeo · 2026-05-15T09:05:16Z

Summary

This PR fixes a resource leak and incorrect error handling during streaming response cleanup when a client context is cancelled or times out. When a stream is forcibly closed due to context cancellation, the body stream is already closed, so attempting to drain it before releasing the response is unnecessary and can cause errors. A new context key (BifrostContextKeyConnectionClosed) is introduced to signal that the connection has already been closed, allowing ReleaseStreamingResponse to skip the drain step safely.

Additionally, context cancellation is now checked before the io.EOF check in all SSE/stream read loops, ensuring that a cancelled context causes an immediate clean exit rather than potentially logging spurious errors or sending error events downstream.

Changes

ReleaseStreamingResponse now accepts a *schemas.BifrostContext and skips draining the body stream if BifrostContextKeyConnectionClosed is set to true.
SetupStreamCancellation now accepts a *schemas.BifrostContext (instead of context.Context) and sets BifrostContextKeyConnectionClosed on the context when the body stream is closed due to cancellation or timeout.
All call sites across every provider (Anthropic, Azure, Cohere, ElevenLabs, Gemini, HuggingFace, Mistral, OpenAI, Replicate, Vertex, vLLM) are updated to pass the BifrostContext to ReleaseStreamingResponse.
In all SSE read loops, the ctx.Err() != nil early-return check is moved to execute before the io.EOF guard, so context cancellation is handled immediately regardless of the read error type.
In passthrough stream handlers (OpenAI, Gemini, Vertex), io.EOF read errors no longer incorrectly trigger ProcessAndSendError; the error path is now guarded with readErr != io.EOF.

Type of change

Affected areas

How to test

Initiate a streaming request and cancel the client context mid-stream (e.g., by closing the HTTP connection early). Verify that:

No "whitespace in header" or drain-related panics appear in logs.
No spurious stream error events are sent to the response channel after cancellation.
Response objects are properly released without goroutine leaks.

go test ./...

Breaking changes

Yes
No

Related issues

Security considerations

None.

Checklist

I read docs/contributing/README.md and followed the guidelines
I added/updated tests where appropriate
I updated documentation where needed
I verified builds succeed (Go and UI)
I verified the CI pipeline passes locally if applicable

coderabbitai · 2026-05-15T09:05:24Z

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 82fce783-5ca7-4bc1-8b16-872023b40a7e

📥 Commits

Reviewing files that changed from the base of the PR and between 6fe17ce and 8e9a74c.

📒 Files selected for processing (18)

core/providers/anthropic/anthropic.go
core/providers/azure/azure.go
core/providers/cohere/cohere.go
core/providers/elevenlabs/elevenlabs.go
core/providers/gemini/gemini.go
core/providers/huggingface/huggingface.go
core/providers/mistral/mistral.go
core/providers/openai/openai.go
core/providers/replicate/replicate.go
core/providers/replicate/utils.go
core/providers/utils/utils.go
core/providers/vertex/vertex.go
core/providers/vllm/vllm.go
core/schemas/bifrost.go
framework/go.mod
plugins/otel/go.mod
transports/bifrost-http/handlers/inference.go
transports/bifrost-http/lib/validator.go

📝 Walkthrough

Summary by CodeRabbit

Bug Fixes
- Made streaming response cleanup context-aware to avoid leaking resources when streams end or error.
- Stream read loops now prioritize context cancellation/timeouts, returning immediately on client disconnects to speed cleanup.
- Added a connection-closed marker to skip draining already-closed streams and prevent unnecessary work.

Walkthrough

This PR systematically updates streaming resource cleanup and cancellation handling across providers: ReleaseStreamingResponse now accepts a Bifrost context and stream defers mark/skip draining when connection-closed; stream read loops check ctx.Err() first and return immediately on cancellation before non-EOF error processing.

Changes

Stream Cancellation & Context-Aware Resource Release

Layer / File(s)	Summary
Core Context-Tracking Infrastructure `core/schemas/bifrost.go`, `core/providers/utils/utils.go`	Adds `BifrostContextKeyConnectionClosed`, updates `SetupStreamCancellation` to mark the flag on close/race paths, and changes `ReleaseStreamingResponse(ctx, resp)` to skip body draining when already closed while still calling `fasthttp.ReleaseResponse`.
Anthropic Provider: Chat, Responses & Passthrough Streaming `core/providers/anthropic/anthropic.go`	Replaces response-only release calls with `ReleaseStreamingResponse(ctx, resp)` across ChatCompletionStream, ResponsesStream, and PassthroughStream; read loops re-check `ctx.Err()` and return immediately on cancellation before EOF/non-EOF handling.
Azure Provider: Speech & Passthrough Streaming `core/providers/azure/azure.go`	SpeechStream and PassthroughStream defer cleanup via `ReleaseStreamingResponse(ctx, resp)` in request/error/goroutine paths.
Cohere Provider: Chat, Responses Streaming & StreamState Refactoring `core/providers/cohere/cohere.go`	Updates defer cleanup to `ReleaseStreamingResponse(ctx, resp)`, tightens read-error cancellation checks, and converts ResponsesStream to use a persistent `streamState` passed to `event.ToBifrostResponsesStream`.
ElevenLabs Provider: Speech Streaming `core/providers/elevenlabs/elevenlabs.go`	SpeechStream deferred cleanup updated to call `ReleaseStreamingResponse(ctx, resp)` at early-exit and goroutine defer points.
Gemini Provider: Chat, Responses, Speech, Transcription & Passthrough `core/providers/gemini/gemini.go`	Multiple handlers updated to use context-aware cleanup; read-error branches now re-check `ctx.Err()` and PassthroughStream avoids sending error chunks on clean EOF.
Hugging Face Provider: Image Generation & Image Edit Streaming `core/providers/huggingface/huggingface.go`	Image generation/edit streaming flows use `ReleaseStreamingResponse(ctx, resp)` and perform early `ctx.Err()` checks in read loops.
Mistral Provider: Transcription Streaming `core/providers/mistral/mistral.go`	TranscriptionStream defers now call `ReleaseStreamingResponse(ctx, resp)` and read-loop error handling reorders to check `ctx.Err()` before EOF/non-EOF branching.
OpenAI Provider: Text, Chat, Responses, Speech, Transcription, Image & Passthrough Streaming `core/providers/openai/openai.go`	Multiple streaming handlers updated to pass `ctx` to `ReleaseStreamingResponse`; SSE/body read loops short-circuit and return immediately when `ctx.Err()` is set.
Replicate Provider: Text, Chat, Responses, Image Generation & Image Edit Streaming `core/providers/replicate/replicate.go`, `core/providers/replicate/utils.go`	Stream goroutines and utils updated to call `ReleaseStreamingResponse(ctx, resp)` and to return immediately from read-error handling when `ctx.Err()` is set.
Vertex Provider: Passthrough Streaming `core/providers/vertex/vertex.go`	PassthroughStream now uses context-aware cleanup and treats `io.EOF` as clean termination without emitting an error chunk.
vLLM Provider: Transcription Streaming `core/providers/vllm/vllm.go`	TranscriptionStream defers updated to `ReleaseStreamingResponse(ctx, resp)` and read loops now re-check `ctx.Err()` before forwarding non-EOF errors.
Configuration & Dependency Reorganization `framework/go.mod`, `plugins/otel/go.mod`, `transports/bifrost-http/handlers/inference.go`, `transports/bifrost-http/lib/validator.go`	Reorders some go.mod entries, moves an OpenTelemetry proto dep to the primary require block, reorders imports, and adjusts schema candidate formatting.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related issues

[Bug]: Goroutines leak on context cancellation #828 — Similar streaming cancellation and ReleaseStreamingResponse(ctx, resp) changes to address cancellation/leak behavior.

Suggested reviewers

danpiths

Poem

🐰 I hopped through streams with tidy paws,

ctx in hand to mend the flaws.
When timeouts call and connections close,
I skip the drain and save you woes.
🌿✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The linked issue `#123` concerns Files API support for providers; this PR addresses streaming error handling and resource cleanup with no connection to File API functionality.	Verify that `#123` is the correct linked issue or link the appropriate issue related to streaming context cancellation and resource cleanup.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: reordering context cancellation checks before EOF checks in streaming read loops across multiple providers.
Description check	✅ Passed	The PR description provides a clear summary of the problem, detailed changes across all affected files, testing instructions, and completes most template sections appropriately.
Out of Scope Changes check	✅ Passed	The PR includes changes to streaming error handling, context-aware resource cleanup, and connection-closed tracking across 11 providers, plus schema additions—all directly supporting the stated streaming cancellation handling objectives.
Docstring Coverage	✅ Passed	Docstring coverage is 80.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch 05-15-handle_ctx_cancel_before_handling_read_errors_in_streaming

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

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

akshaydeo · 2026-05-15T09:05:33Z

This stack of pull requests is managed by Graphite. Learn more about stacking.

coderabbitai

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

core/providers/utils/utils.go (1)

2051-2077: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Only mark connection_closed when a close path actually ran.

Line 2077 sets the flag even when bodyStream implements neither io.Closer nor streamCloserWithError. In that case ReleaseStreamingResponse() will hit the early return on Line 2423 and skip the old drain/close fallback entirely, which can leave the body unread and hurt connection reuse for wrapped readers. Mirror the ctx.Done() branch and gate the flag on whether a close branch was actually taken.

🛠️ Suggested fix

 	case <-done:
 		// If context was also cancelled (race between done and ctx.Done),
 		// still close the body stream to unblock the drain in ReleaseStreamingResponse.
 		if ctx.Err() != nil {
+			closedStream := false
 			if closer, ok := bodyStream.(io.Closer); ok {
 				if err := closer.Close(); err != nil {
 					getLogger().Debug(fmt.Sprintf("Error closing body stream on done with cancelled context: %v", err))
 				}
+				closedStream = true
 			} else if wce, ok := bodyStream.(streamCloserWithError); ok {
 				if err := wce.CloseWithError(ctx.Err()); err != nil {
 					getLogger().Debug(fmt.Sprintf("Error closing body stream on done with cancelled context: %v", err))
 				}
+				closedStream = true
 			}
-			ctx.SetValue(schemas.BifrostContextKeyConnectionClosed, true)
+			if closedStream {
+				ctx.SetValue(schemas.BifrostContextKeyConnectionClosed, true)
+			}
 		}
 	}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@core/providers/utils/utils.go` around lines 2051 - 2077, The code sets
schemas.BifrostContextKeyConnectionClosed unconditionally in the done branch
even when no close occurred; change the done-case to mirror the ctx.Done()
branch by only setting ctx.SetValue(schemas.BifrostContextKeyConnectionClosed,
true) when a close path actually ran (i.e., when bodyStream asserts to io.Closer
or streamCloserWithError and the Close/CloseWithError call is executed), so gate
the flag behind the same type-assert checks for bodyStream (io.Closer and
streamCloserWithError) used above and avoid setting the flag when neither branch
matched; this will ensure ReleaseStreamingResponse behavior (and connection
reuse) remains correct for wrapped readers.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@core/providers/utils/utils.go`:
- Around line 2051-2077: The code sets schemas.BifrostContextKeyConnectionClosed
unconditionally in the done branch even when no close occurred; change the
done-case to mirror the ctx.Done() branch by only setting
ctx.SetValue(schemas.BifrostContextKeyConnectionClosed, true) when a close path
actually ran (i.e., when bodyStream asserts to io.Closer or
streamCloserWithError and the Close/CloseWithError call is executed), so gate
the flag behind the same type-assert checks for bodyStream (io.Closer and
streamCloserWithError) used above and avoid setting the flag when neither branch
matched; this will ensure ReleaseStreamingResponse behavior (and connection
reuse) remains correct for wrapped readers.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 066c8260-f22d-4522-bc97-7e4867bc8f17

📥 Commits

Reviewing files that changed from the base of the PR and between e48cb17 and 6fe17ce.

📒 Files selected for processing (18)

core/providers/anthropic/anthropic.go
core/providers/azure/azure.go
core/providers/cohere/cohere.go
core/providers/elevenlabs/elevenlabs.go
core/providers/gemini/gemini.go
core/providers/huggingface/huggingface.go
core/providers/mistral/mistral.go
core/providers/openai/openai.go
core/providers/replicate/replicate.go
core/providers/replicate/utils.go
core/providers/utils/utils.go
core/providers/vertex/vertex.go
core/providers/vllm/vllm.go
core/schemas/bifrost.go
framework/go.mod
plugins/otel/go.mod
transports/bifrost-http/handlers/inference.go
transports/bifrost-http/lib/validator.go

greptile-apps · 2026-05-15T09:15:32Z

Confidence Score: 4/5

Safe to merge with one fix: the ctx.Done() branch in SetupStreamCancellation sets the ConnectionClosed flag even when close returns an error, which can cause ReleaseStreamingResponse to skip draining on a stream that was never actually closed.

The ctx.Done() branch in SetupStreamCancellation unconditionally sets BifrostContextKeyConnectionClosed after calling closer.Close(), regardless of whether that call succeeded. The done branch was corrected in this same PR to only set the flag on successful close, but the same fix was not applied to ctx.Done(). When close fails in that branch, skipping the drain in ReleaseStreamingResponse can leave unread bytes on the connection, reintroducing the connection-corruption bug the drain is explicitly guarding against.

core/providers/utils/utils.go — the ctx.Done() case in SetupStreamCancellation

Important Files Changed

Filename	Overview
core/providers/utils/utils.go	SetupStreamCancellation signature changed to *schemas.BifrostContext; ReleaseStreamingResponse gains ctx param and skips drain when ConnectionClosed flag is set. ctx.Done() branch sets the flag unconditionally even on close error, inconsistent with the done branch fix.
core/schemas/bifrost.go	Adds BifrostContextKeyConnectionClosed constant; missing inline comment unlike all neighboring constants.
core/providers/anthropic/anthropic.go	ctx passed to ReleaseStreamingResponse at all call sites; ctx.Err() check moved before io.EOF guard in SSE read loops.
core/providers/openai/openai.go	ctx passed to ReleaseStreamingResponse; ctx.Err() check moved before io.EOF in all SSE loops; PassthroughStream no longer calls ProcessAndSendError on io.EOF.
core/providers/gemini/gemini.go	ctx passed to ReleaseStreamingResponse; PassthroughStream io.EOF guard added; ctx.Err() check moved before io.EOF in SSE loops.
core/providers/vertex/vertex.go	ctx passed to ReleaseStreamingResponse at all call sites; PassthroughStream io.EOF guard correctly added.
core/providers/replicate/utils.go	ctx passed to ReleaseStreamingResponse in listenToReplicateStreamURL.
core/providers/cohere/cohere.go	ctx passed to ReleaseStreamingResponse; ctx.Err() check hoisted before io.EOF in both stream loops.

Comments Outside Diff (1)

core/providers/utils/utils.go, line 2051-2063 (link)

In the ctx.Done() branch, BifrostContextKeyConnectionClosed is set unconditionally after closer.Close() — even when the close returns an error. This is the mirror of the asymmetry the done branch was fixed for in this same PR. If closer.Close() fails (e.g., the connection is already in a half-closed state), the stream is not actually drained-safe, yet ReleaseStreamingResponse will skip the drain, potentially leaving unread bytes on the wire and reproducing the "whitespace in header" corruption the drain step is designed to prevent.

_{Reviews (2): Last reviewed commit: "handle ctx cancel before handling read e..." | Re-trigger Greptile}

CLAassistant · 2026-05-15T14:21:25Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

akshaydeo · 2026-05-15T14:21:45Z

Merge activity

May 15, 2:21 PM UTC: A user started a stack merge that includes this pull request via Graphite.
May 15, 2:22 PM UTC: @akshaydeo merged this pull request with Graphite.

## Summary This PR fixes a resource leak and incorrect error handling during streaming response cleanup when a client context is cancelled or times out. When a stream is forcibly closed due to context cancellation, the body stream is already closed, so attempting to drain it before releasing the response is unnecessary and can cause errors. A new context key (`BifrostContextKeyConnectionClosed`) is introduced to signal that the connection has already been closed, allowing `ReleaseStreamingResponse` to skip the drain step safely. Additionally, context cancellation is now checked *before* the `io.EOF` check in all SSE/stream read loops, ensuring that a cancelled context causes an immediate clean exit rather than potentially logging spurious errors or sending error events downstream. ## Changes - `ReleaseStreamingResponse` now accepts a `*schemas.BifrostContext` and skips draining the body stream if `BifrostContextKeyConnectionClosed` is set to `true`. - `SetupStreamCancellation` now accepts a `*schemas.BifrostContext` (instead of `context.Context`) and sets `BifrostContextKeyConnectionClosed` on the context when the body stream is closed due to cancellation or timeout. - All call sites across every provider (Anthropic, Azure, Cohere, ElevenLabs, Gemini, HuggingFace, Mistral, OpenAI, Replicate, Vertex, vLLM) are updated to pass the `BifrostContext` to `ReleaseStreamingResponse`. - In all SSE read loops, the `ctx.Err() != nil` early-return check is moved to execute *before* the `io.EOF` guard, so context cancellation is handled immediately regardless of the read error type. - In passthrough stream handlers (OpenAI, Gemini, Vertex), `io.EOF` read errors no longer incorrectly trigger `ProcessAndSendError`; the error path is now guarded with `readErr != io.EOF`. ## Type of change - [x] Bug fix - [ ] Feature - [ ] Refactor - [ ] Documentation - [ ] Chore/CI ## Affected areas - [x] Core (Go) - [ ] Transports (HTTP) - [x] Providers/Integrations - [ ] Plugins - [ ] UI (React) - [ ] Docs ## How to test Initiate a streaming request and cancel the client context mid-stream (e.g., by closing the HTTP connection early). Verify that: - No "whitespace in header" or drain-related panics appear in logs. - No spurious stream error events are sent to the response channel after cancellation. - Response objects are properly released without goroutine leaks. ```sh go test ./... ``` ## Breaking changes - [ ] Yes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [ ] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable

akshaydeo marked this pull request as ready for review May 15, 2026 09:05

coderabbitai Bot requested a review from danpiths May 15, 2026 09:06

coderabbitai Bot reviewed May 15, 2026

View reviewed changes

coderabbitai Bot previously approved these changes May 15, 2026

View reviewed changes

greptile-apps Bot reviewed May 15, 2026

View reviewed changes

Comment thread core/schemas/bifrost.go

Comment thread core/providers/utils/utils.go

This was referenced May 15, 2026

handle raw request absent in error scenarios if raw request is enabled #3523

Closed

test case fixes #3525

Merged

handle ctx cancel before handling read errors in streaming

8e9a74c

akshaydeo dismissed coderabbitai[bot]’s stale review via 8e9a74c May 15, 2026 14:21

akshaydeo force-pushed the 05-15-handle_ctx_cancel_before_handling_read_errors_in_streaming branch from 6fe17ce to 8e9a74c Compare May 15, 2026 14:21

akshaydeo merged commit ad7e37c into dev May 15, 2026
11 of 14 checks passed

akshaydeo deleted the 05-15-handle_ctx_cancel_before_handling_read_errors_in_streaming branch May 15, 2026 14:22

coderabbitai Bot approved these changes May 15, 2026

View reviewed changes

coderabbitai Bot mentioned this pull request May 19, 2026

fix: fasthttp panic fix #3595

Merged

18 tasks

coderabbitai Bot mentioned this pull request May 20, 2026

fix: llm tests tokens #3630

Merged

18 tasks

akshaydeo mentioned this pull request May 20, 2026

v1.5.3 #3531

Merged

This was referenced May 20, 2026

[Bug]: Anthropic streaming emits wrong stop_reason after mixed text + tool-call turns #3638

Closed

adds created_by for virtual keys #3672

Merged

[Bug]: HTTP access log accidentally disabled in CorsMiddleware since transports/v1.5.3 #3719

Closed

This was referenced Jun 1, 2026

fix: passthrough budgets #3941

Merged

[Bug]: Simple transcription routing rule with fallback not working #4005

Open

coderabbitai Bot mentioned this pull request Jun 11, 2026

[Bug]: Model parameters can't be configured locally #4305

Closed

2 tasks

coderabbitai Bot mentioned this pull request Jun 19, 2026

[Bug]: duplicate message_start SSE frame on Anthropic passthrough (responses_stream) #4556

Closed

2 tasks

coderabbitai Bot mentioned this pull request Jul 12, 2026

[Bug]: Gemini/Vertex streaming responses stop emitting web_search_call items after the first grounded request per pooled stream state #5113

Closed

2 tasks

Navigation Menu

Uh oh!

handle ctx cancel before handling read errors in streaming - #3522

handle ctx cancel before handling read errors in streaming#3522
akshaydeo merged 1 commit into
devfrom
05-15-handle_ctx_cancel_before_handling_read_errors_in_streaming

akshaydeo commented May 15, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented May 15, 2026 •

edited

Loading

Review failed

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Possibly related issues

Suggested reviewers

Poem

❌ Failed checks (1 warning)

Uh oh!

akshaydeo commented May 15, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

greptile-apps Bot commented May 15, 2026 •

edited

Loading

Comments Outside Diff (1)

Uh oh!

Uh oh!

Uh oh!

CLAassistant commented May 15, 2026

Uh oh!

akshaydeo commented May 15, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

akshaydeo commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Type of change

Affected areas

How to test

Breaking changes

Related issues

Security considerations

Checklist

Uh oh!

coderabbitai Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review failed

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Possibly related issues

Suggested reviewers

Poem

❌ Failed checks (1 warning)

Uh oh!

akshaydeo commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 4/5

Important Files Changed

Comments Outside Diff (1)

Uh oh!

Uh oh!

Uh oh!

CLAassistant commented May 15, 2026

Uh oh!

akshaydeo commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge activity

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

akshaydeo commented May 15, 2026 •

edited

Loading

coderabbitai Bot commented May 15, 2026 •

edited

Loading

akshaydeo commented May 15, 2026 •

edited

Loading

greptile-apps Bot commented May 15, 2026 •

edited

Loading

akshaydeo commented May 15, 2026 •

edited

Loading