Fix connection errors not being reflected for jobs #254
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Ensures connection failures are captured and cleaned up correctly in eval contexts.
_eval_enter()before connecting the environment so traces are registered even if connection fails__aexit__for unified cleanup/reporting (context vars reset, backend notified), ensuring errors reflect in jobs/telemetryWritten by Cursor Bugbot for commit 93837af. This will update automatically on new commits. Configure here.