Skip to content

Jupyterlab's responses "400 Bad Request" in version 2.6.0 #11672

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.

Sign up for GitHub

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

Jump to bottom
Closed
madhosoi opened this issue Jan 17, 2024 · 6 comments
Closed

Jupyterlab's responses "400 Bad Request" in version 2.6.0 #11672

madhosoi opened this issue Jan 17, 2024 · 6 comments
Labels
need-help Assign this label prompts an engineer to check the issue. Only humans may set this.

Comments

@madhosoi
Copy link

madhosoi commented Jan 17, 2024 •
edited
Loading

After upgrade of Coder OSS to version 2.6.0, we are experiencing these errors accessing to any feature related to websockets (I suppose) of jupyterlab instantiated in a given template running on Kubernetes:

image

With previous version, it is running as expected.

I have this setup:

/opt/miniconda/bin/python3.11 /opt/miniconda/bin/jupyter-lab --no-browser --ServerApp.password= 
--ServerApp.token= --JupyterApp.config_file=~/.jupyter/jupyter_notebook_config.py 
--ServerApp.port=8888 --ServerApp.base_url=@<user>/<workspace>.main/apps/jupyter --ip='*'

# jupyter
resource "coder_app" "jupyter" {
  count        = local.jupyter-count
  agent_id     = coder_agent.main.id
  display_name = "Jupyter Lab"
  slug         = "jupyter"
  icon         = "/icon/jupyter.svg"
  url          = "http://localhost:8888/@${lower(data.coder_workspace.me.owner)}/${lower(data.coder_workspace.me.name)}.main/apps/jupyter/"
  subdomain    = false
  share        = "owner"
}

I cannot see any clue in the logs of coder, of the proper workspace's container neither in the jupyterlab logs (running it manually to get them).

Could you help me to understand the error?
If you need more info, just ask me.
Thanks

Miguel
@cdr-bot cdr-bot bot added the bug label Jan 17, 2024
@madhosoi madhosoi changed the title Jupyterlab's responses "400 Jupyterlab's responses "400 Bad Request" in version 2.6.0 Jan 17, 2024
@matifali matifali added the need-help Assign this label prompts an engineer to check the issue. Only humans may set this. label Jan 17, 2024
@ericpaulsen
Copy link
Member

thank you for reporting @madhosoi - here is another issue that is likely related: #11406

we have a fixed merged against this issue: #11656

@madhosoi
Copy link
Author

Thanks for letting me know.
Do you know when it will be released to test it?

@matifali
Copy link
Member

@madhosoi we plan to cut a release by end of week.
Closing this as duplicate of #11406
Please request to reopen if it's not solved with the new release.

@matifali matifali closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2024
@madhosoi
Copy link
Author

Thanks for confirming @ericpaulsen & @matifali !

@madhosoi
Copy link
Author

Hi,
After upgrade to version 2.7.0 (also tested with coder-preview:latest), this error is fixed.
But, now, when I have 2 workspaces that has jupyterlab, it seems the traffic of services is not redirecting properly, e.g:
image

The behaviour is weird, the first jupyter I open, is open perfectly. The second is opeing the content of the first one:
image

If you need me to open a new one, of course I can do it.

Thanks!

@matifali
Copy link
Member

matifali commented Jan 20, 2024 •
edited
Loading

Yes please move it to a new issue. And link this issue as related

@madhosoi madhosoi mentioned this issue Jan 23, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
need-help Assign this label prompts an engineer to check the issue. Only humans may set this.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@madhosoi @ericpaulsen @matifali