Deno workarounds #73
Deno workarounds #73
Conversation
mishushakov
commented
Mar 25, 2025
mishushakov
commented
- Updated to the latest version of Deno
- Added a warmup script that runs Deno session once
mishushakov
requested review from
0div,
ValentaTomas and
jakubno
as code owners
| fi | ||
|
|
||
| deno_session_id=$(echo "${deno_response}" | jq -r '.id') | ||
| curl -s -X DELETE "localhost:8888/api/sessions/${deno_session_id}" |
There was a problem hiding this comment.
curious: why are deleting the session here but not for the python kernel?
|
|
||
| # Deno Kernel | ||
| COPY --from=denoland/deno:bin-2.0.4 /deno /usr/bin/deno | ||
| COPY --from=denoland/deno:bin-2.2.5 /deno /usr/bin/deno |
There was a problem hiding this comment.
so this solves the import problem correct?
|
I converted to draft, I still need to do some further investigation, particularly I have to make it start reliable on new context |
|
Please improve the name to express what the PR will achieve. |
|
What is the status on this PR? I need to use the Deno runtime and the current version in the code interpreter is very flaky |
|
I am closing this as there appears to be an underlying issue with Deno where the kernel gets stuck in the "starting" state with no ability to restart. I have tried multiple approaches, including retries, but this does not fix the underlying issue. A bug report on the Deno issue tracker was created: denoland/deno#28634 |
|
@ebramanti what particular features of Deno do you need? We might have a fix soon that may make Deno unnecessary (typescript, top-level await, es modules) |
