Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport 5.3.9104] completions: recover from panics in writeEvent #61755

Merged
merged 1 commit into from
Apr 10, 2024

Conversation

sourcegraph-release-bot
Copy link
Collaborator

I timeboxed some time to work out why we call writeEvent once the request is done. My main idea is around request cancellation and the first event being an attribution error. However, I could not nail down an exact cause. Instead this is a change to isolate panics to the request it is happening in rather than taking down the whole process.

Test Plan: go test

Part of #60439
Backport c40b376 from #61754

I timeboxed some time to work out why we call writeEvent once the
request is done. My main idea is around request cancellation and the
first event being an attribution error. However, I could not nail down
an exact cause. Instead this is a change to isolate panics to the
request it is happening in rather than taking down the whole process.

Test Plan: go test

(cherry picked from commit c40b376)
@keegancsmith keegancsmith merged commit da58d41 into 5.3.9104 Apr 10, 2024
10 of 15 checks passed
@keegancsmith keegancsmith deleted the backport-61754-to-5.3.9104 branch April 10, 2024 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants