Changes in 3.1.8 that affect VSCode app

We are running into an odd issue with an update done yesterday to OOD 3.1.8. We upgraded virtualGL and turboVNC during a maintenance outage and tested these last week with OOD 3.1.7 in our dev environment and everything worked. Yesterday we accidentally updated to 3.1.8 without testing and now have an issue with VSCode. It looks like the URL construction is broken and when I searched through Discourse I found some older posts referring to a similar problem so I wanted to ask if this might possibly be causing an unintended issue with the VSCode app. What I’m seeing in the output.log file is something like this (it’s missing the hostname and has this string of numbers):

debug got cookie domain [38;2;140;140;140m{“host”:“ood-dev.int.ccr.buffalo.edu”}[0m

I’m seeing these odd characters and numbers in the handshake debug of the output.log too:

debug parent:38238 got message e[38;2;140;140;140m{“message”:{“type”:“handshake”}}e[0m
[2024-09-25T21:16:10.496Z]
debug child:38266 got message e[38;2;140;140;140m{“message”:{“type”:“handshake”,“args”:{“bind-addr”:“0.0.0.0:62506”

What happens when I click to start the VSCode app is I get a 401 error in the browser. When I click the “home” link I get prompted for the password. If I try to enter that from the connection.yml file it authenticates but then returns “not found” The log says it can’t find the home directory and then after a few refreshes in the browser it gives an “unsupported method post” error. This experience is the same in both our production and dev systems but the odd thing is that in the production output.log file the host string appears to be correct:

debug got cookie domain {“host”:“cpn-i14-39.core.ccr.buffalo.edu”}

and the handshake looks correct (like it did last week when testing before the upgrade):

debug parent:19019 got message {“message”:{“type”:“handshake”}}
[2024-09-25T16:48:25.641Z]
debug child:19067 got message {“message”:{“type”:“handshake”,“args”:{“bind-addr”:“0.0.0.0:32472”…

That’s why I’m really unsure if it’s something from the upgrade of OOD or something else causing it. If you have any advice, I’d appreciate it!

Thanks!
Dori

Update: We tried reverting just that one change that I linked to in my original post but that didn’t fix anything. Reverting to our older version of turboVNC also didn’t change anything. We also had reports of really odd problems with the RStudio app - background color changes, colorization in the terminal and files wasn’t working, couldn’t copy/paste, could use the “knit” feature, and plots and graphs generated were not colorized right. We didn’t think these things were related at all but after trying a bunch of things, decided to downgrade to OOD 3.1.7 in our dev environment. This fixed all of these issues. We’re not sure what of the upgrade to 3.1.8 could be conflicting for us but for now we’re back to happy users.

1,000 apologies for that. But yes, 3.1.8 is buggy so it won’t make it to the 3.1 stable release repo. Sorry you picked it up on accident!

1 Like

Note that you are pulling from the latest repo, but there’s an actual 3.1 repository that may be better to have enabled in production. 3.1.8 for example, won’t make it to that repository and would have shielded you from this.

https://yum.osc.edu/ondemand/3.1/web/el8/x86_64/

1 Like