Repository navigation
fix(template): recreate deleted default language contexts - #352
Apeksha9389 wants to merge 1 commit into
Conversation
|
We require contributors to sign our Contributor License Agreement, and we don't have @Apeksha9389 on file. You can sign our CLA at https://e2b.dev/docs/cla . Once you've signed, post a comment here that says '@cla-bot check' |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@cla-bot check |
|
The cla-bot has been summoned, and re-checked this pull request! |
|
Hey, appreciate the PR here, but it has to be done differently. |
|
Thanks for reviewing. Could you clarify the intended behavior after a default language context is deleted, and which part of this approach should change? |
Deleting a default language context removes its live connection but leaves its id in
default_websockets. The nextrun_code(..., language="python")resolves that stale id and returns HTTP 404 instead of creating a replacement. Executions without a language also need the same default-resolution path.Route implicit Python execution through the existing per-language lock and recreate a default when its cached id is absent from the live context registry. Refresh the Python default alias when creating its replacement. Explicit context ids retain their existing lookup and 404 behavior. Includes a template patch changeset.
Validation on Python 3.12:
404 Not Found: Context None not found.No cloud sandbox, other language kernels, or full integration-suite run was performed. The added tests use the existing
CodeInterpreterharness and standard client fixture, so they also run in the repository's sandbox test setup.Prepared with AI assistance; reproduced and tested locally.