SpaceMoehre-i-nator™ Comments

SpaceMoehre-i-nator™

•Created by SpaceMoehre-i-nator™ on 11/29/2024 in #help

Access Workspace Web does not work with returning Code 302

this is why on clicking the jupyterlab button, the new window displayed coders 502 code with "connection refused", since jupyterlab was unable to start due to misconfigured pipx

21 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/29/2024 in #help

Access Workspace Web does not work with returning Code 302

no prob, i fixed it. installing pipx via debian bookworms apt package defaulted to python3.13. installing via python -m pip install pipx fixed my issue

21 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/29/2024 in #help

Access Workspace Web does not work with returning Code 302

ok i guess i found the issue somewhere non network related the log /tmp/jupyterlab.log showed

sh: 29: /home/simon/.local/bin/jupyter-lab: not found

sh: 29: /home/simon/.local/bin/jupyter-lab: not found

turns out juypter-lab has python3.13 in the shebang, which is not installed on my system since i need 3.9 for dependencies. is there a jupyter module version that uses python3 or <=python3.9 ?

21 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/29/2024 in #help

Access Workspace Web does not work with returning Code 302

ok so the problem must originate from an incorrect tunnel to tailscale...

21 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/29/2024 in #help

Access Workspace Web does not work with returning Code 302

weird is that i dont use ipv6 anywhere, so where is that address coming from?

21 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/29/2024 in #help

Access Workspace Web does not work with returning Code 302

i found out that i can use the jupyter module and choose the sage interpreter in there

module "jupyterlab" {
  source   = "registry.coder.com/modules/jupyterlab/coder"
  version  = "1.0.24"
  agent_id = coder_agent.main.id
  subdomain = false
}

module "jupyterlab" {
  source   = "registry.coder.com/modules/jupyterlab/coder"
  version  = "1.0.24"
  agent_id = coder_agent.main.id
  subdomain = false
}

but for some reason i get this error for the last weeks:

502 - Bad Gateway

Failed to proxy request to application: dial context: connect tcp [fd7a:115c:a1e0:44c4:9ff1:9036:a3df:c529]:19999: connection was refused

502 - Bad Gateway

Failed to proxy request to application: dial context: connect tcp [fd7a:115c:a1e0:44c4:9ff1:9036:a3df:c529]:19999: connection was refused

21 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/10/2024 in #help

VSCode Desktop hangs after workspace update

well i finished my template so it doesnt bother me anymore but i assume the bug still persists

19 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/29/2024 in #help

Access Workspace Web does not work with returning Code 302

well i guess using the jupyter module i can still use sage, but the problem with http codes 302 persists

21 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/10/2024 in #help

VSCode Desktop hangs after workspace update

Changed this Dockerfile from ubuntu to rust:latest

FROM rust:latest

RUN apt-get update \
    && apt-get install -y \
    curl \
    git \
    sudo \
    vim \
    wget \
    cargo \
    && rm -rf /var/lib/apt/lists/*

ARG USER=coder
RUN useradd --groups sudo --no-create-home --shell /bin/bash ${USER} \
    && echo "${USER} ALL=(ALL) NOPASSWD:ALL" >/etc/sudoers.d/${USER} \
    && chmod 0440 /etc/sudoers.d/${USER}
USER ${USER}
WORKDIR /home/${USER}

FROM rust:latest

RUN apt-get update \
    && apt-get install -y \
    curl \
    git \
    sudo \
    vim \
    wget \
    cargo \
    && rm -rf /var/lib/apt/lists/*

ARG USER=coder
RUN useradd --groups sudo --no-create-home --shell /bin/bash ${USER} \
    && echo "${USER} ALL=(ALL) NOPASSWD:ALL" >/etc/sudoers.d/${USER} \
    && chmod 0440 /etc/sudoers.d/${USER}
USER ${USER}
WORKDIR /home/${USER}

Then published the template as active and updated the workspace

19 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/10/2024 in #help

VSCode Desktop hangs after workspace update

after a bit of experimenting this seems to occure due to exchanging the image from "ubuntu:latest" -> "rust:latest", Dockerfile updates with the same image still work

19 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/10/2024 in #help

VSCode Desktop hangs after workspace update

yes i replicated the error, confirmed the same error message and hit f5 in my browser

19 replies

CCoder.com

•Created by SpaceMoehre-i-nator™ on 11/10/2024 in #help

VSCode Desktop hangs after workspace update