Repository navigation
Jupyter Extension: Not working with code-server versions ≥ 4.118.0 when accessing with Safari #7803
Copy link
Copy link
Closed
Labels
browser-safariSafari relatedSafari relatedbugSomething isn't workingSomething isn't workingcode-server
Description
Is there an existing issue for this?
- I have searched the existing issues
OS/Web Information
- Web Browser: Safari
- Local OS: macOS
- Remote OS: Linux (Debian 14)
- Remote Architecture: amd64
code-server --version: 4.118.0 871f1d9 with Code 1.118.0
Steps to Reproduce
- Open https://coder.jupyter.b-data.ch
- Login with your GitHub account
- Click on
code-server - Create a Jupyter Notebook
- Try to execute a cell
Expected
Cell output visible and no errors in browser console.
Actual
Cell output invisible and errors in browser console.
Logs
Browser console:
[Error] SyntaxError: Can't create duplicate variable: 'SafariAppExtensionPage'
write (index.html:1064)
(anonymous function) (index.html:1064)[Error] ERR (1)
Underlying ArrayBuffer has been detached from the view or out-of-bounds: subarray
slice — workbench.js:406:97283
read — workbench.js:1032:107876
A9e — workbench.js:1032:108820
onRawMessage — workbench.js:1032:109929
_deliver — workbench.js:405:3275
_deliverQueue — workbench.js:405:3367
fire — workbench.js:405:3707
fire — workbench.js:1034:9643
_receiveMessage — workbench.js:1034:14559
_deliver — workbench.js:405:3275
fire — workbench.js:405:3597
acceptChunk — workbench.js:1034:6504
_deliver — workbench.js:405:3275
fire — workbench.js:405:3597
(anonymous function) — workbench.js:4907:27780
error (workbench.js:414:17825)
error (workbench.js:414:18886)
error (workbench.js:4907:19806)
handleUnexpectedError (workbench.js:4904:113744)
onUnexpectedError (workbench.js:383:377)
pt (workbench.js:383:600)
_deliver (workbench.js:405:3289)
_deliverQueue (workbench.js:405:3367)
fire (workbench.js:405:3707)
fire (workbench.js:1034:9643)
_receiveMessage (workbench.js:1034:14559)
_deliver (workbench.js:405:3275)
fire (workbench.js:405:3597)
acceptChunk (workbench.js:1034:6504)
_deliver (workbench.js:405:3275)
fire (workbench.js:405:3597)
(anonymous function) (workbench.js:4907:27780)
[Error] ERR (1)
Underlying ArrayBuffer has been detached from the view or out-of-bounds: subarray
slice — workbench.js:406:97283
_read — workbench.js:1034:4586
acceptChunk — workbench.js:1034:5869
_deliver — workbench.js:405:3275
fire — workbench.js:405:3597
(anonymous function) — workbench.js:4907:27780
error (workbench.js:414:17825)
error (workbench.js:414:18886)
error (workbench.js:4907:19806)
handleUnexpectedError (workbench.js:4904:113744)
onUnexpectedError (workbench.js:383:377)
pt (workbench.js:383:600)
_deliver (workbench.js:405:3289)
fire (workbench.js:405:3597)
(anonymous function) (workbench.js:4907:27780)
Screenshot/Video
No response
Does this bug reproduce in native VS Code?
No, this works as expected in native VS Code
Does this bug reproduce in VS Code web?
This cannot be tested in VS Code web
Does this bug reproduce in GitHub Codespaces?
No, this works as expected in GitHub Codespaces
Are you accessing code-server over a secure context?
- I am using a secure context.
Notes
A similar issue has been reported for the Jupyter Extension itself when connected to JupyterHub 5.x via remote:
Metadata
Metadata
Assignees
Labels
browser-safariSafari relatedSafari relatedbugSomething isn't workingSomething isn't workingcode-server
Activity
benz0li commentedon May 18, 2026
See also:
[-]Jupyter Extension: Not working with code-server versions ≥ 4.118.0 when accessed with Safari[/-][+]Jupyter Extension: Not working with code-server versions ≥ 4.118.0 when accessing with Safari[/+]benz0li commentedon May 18, 2026
No (visible) issue1 when accessing with Firefox.
Footnotes
There are some error messages in the browser console, though. ↩
benz0li commentedon May 18, 2026
Same issue when running
codercom/code-server:4.118.0and accessing directly with Safari.IMHO this issue is not related to code-server being run behind a JupyterHub (proxy).
code-asher commentedon May 19, 2026
Oh wait I remember now I did actually see flaky Webkit issues with 4.118.0 (because of the e2e tests) but since it seemed to be an upstream bug and I found an issue was filed about it I went ahead with the release.
In hindsight, that might have been a bad idea. Might hold off on 4.120.0 until I see if we might be able to patch it.
smerschjohann commentedon May 31, 2026
sounds related to this? #7801
benz0li commentedon Jun 18, 2026
Tested with code-server version 4.125.0 fade53f with Code 1.125.0.
It is working again now.