-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[Bug]: Can't run the NPM release - shows 404 #4900
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.
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
Comments
Happy to try any command/debug thing, I'm mostly running out of ideas... Running with No errors on the install either - happy to upload somewhere the complete install logs with silly log-level activated if that can help? |
"doman" - This is funny typo 😂 "The Lesser Known Superhero" - steals your cookie do[ugh] Hmm...to clarify, does this only happen when accessing it through a local SSH tunnel? |
Happens in all cases, not only SSH tunnel. Even happens when using The SSH tunnel is just easier to reproduce on a brand-new instance, which makes it easier to be reproducible ;D |
This was broken and should be fixed in the next version. Hmm...this look similar to what @code-asher and I were seeing. Can you try running |
Sorry not sure what's being fixed 😂 I wasn't really raising a problem, mostly just saying that I tried all the ways I could think of to access
Yes - still same, just ran the reproduction steps posted above using using This specific version: |
Ah, sorry I was referencing the HTTPS cert stuff (#4693). The self-signed certificate logic was broken and should be fixed soon.
Thanks for trying! This is very odd...We received a similar report here: #4896 (comment) Thanks for raising! I'm really not sure what it could be. I need to finish #4822 before I'll have time to investigate. |
I'll keep an eye on #4822 and try installing the beta again when finished, in case it came from vscode itself though I don't think so... I'd be happy helping troubleshooting/investigate/provide logs, but I'm a bit stuck/lost on where to start or what can be helpful. Feel free to hit me up if there's anything I can help with. |
That's so nice! Thank you! I am stumped too to be honest. I vaguely ran into something similar when talking to @code-asher earlier this week...but he couldn't reproduce. This is the only clue I have (thanks to @aptalca):
It's possible we updated a npm package that broke something 🤔 But other than that, I'm not 100%. @code-asher might have some tips on debugging though. |
@jawnsy did address some security vulnerabilities and republish to Docker on Feb 23rd: https://github.com/coder/code-server/actions/runs/1884619798 (that wouldn't affect NPM), but that shouldn't have broken anything 🤔
Hmm...We've published to npm since then but haven't changed the 4.0.2 tag. I'm trying to think what else could have changed. |
Ok, did diff of the versions of the dependencies between ls111 and ls112 images of the linuxserver image: https://editor.mergely.com/WfQ5xHTn/ After trying couple things, the culprit seems to be I'll try to do the change in git, build, release an npm package and install and report back. If it works, I'll send a PR. |
@edvincent 😮 Wow, I'm impressed at how fast you found that! That just made this Friday 10x better!
You rock 🙌 |
w00t w00t 🎉 It's all running well! Sent a PR pinning the version of At some point someone might want to check what the breaking change was... but at least NPM installs aren't blocked until then.
I mostly needed a working one to be able to do some comparisons, already suspected a problem with versions as there's no lockfile.
Glad to be able to help and give back to the project and community! |
@edvincent Thanks for the contribution, we'd love to send you a Coder t-shirt and some other goodies if you're interested. If so, can you send your mailing address and shirt size to ben @ coder dot com |
Is there an existing issue for this?
OS/Web Information
Version 98.0.4758.102 (Official Build) (x86_64)
MacOS 12.2.1 (21D62)
Linux ip-172-26-9-167 5.4.0-1018-aws #18-Ubuntu SMP Wed Jun 24 01:15:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
x86_64
code-server --version
:4.0.2
&4.0.1
14.19.0
&14.18.3
Steps to Reproduce
On a brand-new Ubuntu 20.04 instance:
And then accessing it through a local SSH tunnel using
ssh -i Downloads/LightsailDefaultKey-us-west-2.pem ubuntu@UBUNTU_INSTANCE_IP -L 8080:localhost:8080
(for this brand new repro - but still happened when exposing the port directly, or with a reverse proxy etc... The SSH tunnel happens to be more light-weight to setup to be able to try with multiple versions of NodeJS and of code-server ;P)Expected
Able to launch and access code-server.
Actual
I can log-in completely fine, but get a 404 once logged in. If
--auth none
is passed, I straight go to the error page.Logs
Screenshot/Video
Does this issue happen in VS Code?
Are you accessing code-server over HTTPS?
Notes
--link
.npm WARN @coder/[email protected] requires a peer of @google-cloud/logging@^4.5.2 but none is installed. You must install peer dependencies yourself.
g++ libx11-dev libxkbfile-dev libsecret-1-dev
before installing the package, which gets rid of some of the WARN during the install for lack of node-gyp -warning Error running install script for optional dependency
.Possibly Related
There have been other 404 reports using yarn.
@parcel/watcher
#4896 (comment)@parcel/watcher
#4896 (comment)The text was updated successfully, but these errors were encountered: