Skip to content

Conversation

avapirev
Copy link
Contributor

@avapirev avapirev commented Sep 9, 2025

No description provided.

Copy link
Contributor

@moravveji moravveji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have few remarks concerning the KUL-specifics:

  • The tunnel name that contains the user VSC id (the one limited to 20 chars) can be different between KUL and VUB; e.g. we use currently a template like vsc-vscXXXXX-wice which is different from that of VUB. This needs to be made clear in the documentation with site-specific tabs.
    Well ... we still have to internally agree on the tunnel name, which will happen outside this repo
  • The local VSCode terminal shows that the ttyd module belongs to the 2024a toolchain. This means that users who want to use the Python(-related) modules are restricted to the 2024a toolchain only. This must be made clear in a 'Warning' box
  • There is a mention of using Microsoft account, but I tried with my github connection, and it did not bite. The copilot worked as expected. So, perhaps this knot can be loosened a bit
  • We also need to clarify that at KUL, we do not offer GPUs for this specific app. Think of it as a 'Note' box
  • This may sound trivial but let's also mention that the same blue button at the bottom left also offers the 'Close Remote Connection' button to disconnect from the job when we're done. However, this does not terminate the job and release the resources. So, you may also think of another 'Warning' box.
  • Needless to say that while the job is running on the cluster, the tunnel can be resumed by following the same steps above

@moravveji moravveji self-requested a review September 17, 2025 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants