-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
Errors on installing uber-juno
#482
Comments
Thanks a ton for opening an issue for this one. It sounds almost like Pulsar is having trouble finding your pulsar configuration location, do you have a But otherwise I'll test with installing it to a custom location and see if I can reproduce this |
Also just noticed on the other issue you commented on you asked if native modules can be compiled with So native modules being built to be consumable by node isn't a process controlled by Pulsar, it's really a Node thing. Which Node uses So it'd depend on if a |
yep, the whole folder exists pretty well. $ ls "$USERPROFILE/.pulsar"
blob-store config.cson init.js packages storage
compile-cache github.cson keymap.cson snippets.cson styles.less |
@goyalyashpal So I noticed you used the Linux way to specify the directory location, I wonder if this is something to do with, I'm assuming you are using WSL? I have it setup to without any issues, but might depend a bit on how Pulsar is being launched. Otherwise, tbh I'd thinking this may be related to setting Is |
nope, i am not using WSL. It's msys2 - it provides linux/gnu utils like bash etc - which i find much much more pleasant to work with. It's totally standalone, it works with local system, doesn't require entering in any special environment like WSL or any other such thing.
ohkay, i will see
yes: $ where cmd
C:\Windows\System32\cmd.exe
D:\msys64\usr\bin\cmd
$ which -a cmd
/c/Windows/system32/cmd
/c/WINDOWS/system32/cmd
/d/msys64/usr/bin/cmd |
yep, setting (but i will reset it back to bash, as i can't stand MS cmd 😅) |
/usr/bin/bash: /s: No such file or directory
ComSpec
causes issues: /usr/bin/bash: /s: No such file or directory
So I'll take a look into this, but do want to mention that it may not be something we can totally resolve. Since it looks like this issue occurs when Now hopefully there is a way to rework this in a way that works for existing users and users like yourself. But I do want to ask @pulsar-edit/core is this something we want to work to support? Keep in mind that the first Google Result for setting Although the simplest solution might be to see if either we can launch PPM via a specified CLI, or if we can otherwise optionally change the |
So a follow-up here, in In This would effectively ignore any other terminals being used, but might be a good idea, to keep things working. |
Just for records: After @ savetheclocktower 's input, I checked the file in VSCodium, and under "Problems" it showed following Error:
Copy Error in VSCodium
one more thing, on trying to install that [FIXED UPSTREAM] Failed to load the uber-juno package: Unexpected reserved word packageThough fixed upstream, as of 2023.04.17, fix hasn't been tagged, or new version of package with fix hasn't been released. VersionsAtom: 1.103.0 x64 Stack TraceFailed to load the uber-juno package
Show Stack Trace
Non-Core Packages
[FIXED UPSTREAM] Failed to activate the ink Package: subs is not definedThough fixed upstream, as of 2023.04.17, fix hasn't been tagged, or new version of package with fix hasn't been released. After replacing VersionsAtom: 1.103.0 x64 Stack TraceFailed to activate the ink package
Show Stack Trace
Non-Core Packages
Unfilled Prerequisites Checklist
Unfilled templateDescriptionSteps to ReproduceExpected behavior: Actual behavior: Commands
Additional Information |
That's not a fun one. Open the the |
Also, the colors here are very beautiful, i gotta say that. good job :) I don't know why it's showing internet related thing, i have a perfectly working internet connection. But also, at this point, I think it's not really Pulsar's thing... so, i will leave it at that.
|
Man, that's a bit sloppy on the package author's part — using a variable without declaring it first. https://github.com/JunoLab/atom-ink/blob/master/lib/linter/pane.js#L14 You can change both instances of |
@savetheclocktower Fyi it does look like @sertonix has already tried contacting the author of this package to fix some of this issues. @goyalyashpal Because this package has been neglected for so long, I do want to mention it may be a good idea to see if there are any other community packages that can accomplish the same thing. Since it seems this one isn't fully functional, which is unfortunate, but otherwise hopefully this is the last issue to arise. |
Maybe |
@savetheclocktower It may also be beneficial to add a badge to this package, since it does not work at all without manual edits. |
@goyalyashpal So I've talked further with the team about this issue. Essentially the conclusion we've come to, is that while I understand it might be frustrating for things to not work properly, like I mentioned the only resource I can find about users changing the And there's no realistic way to support this. If we go out of the way to support this particular program, that would also mean we need to support users changing this value to cygwin, gitbash, or a dozen other possible applications that might be used. And tbh, Pulsar itself never calls on So all in all, I'm glad we were able to pursue some other issues with specific packages, but as for the reason you made this issue I don't believe we will be able to support it. Thanks a ton for reporting this issue though and contributing! |
btw, i just noticed that i never mentioned what the expected outcome is / solution can be... supporting non-cmd is not an option as u noted, but maybe on the event of occuring a failure, comspec can be checked and if found guilty, then a more helpful error might be raised; smth like "ComSpec found to be non-compliant, try resetting it back to cmd" but yeah, to be honest, thus is too corner of a use-case (& that too which's broken anyway - see comment below) - so even this may not be worth doing it... |
yeah, lots of things break on changing comspec i.e. are dependent on it being cmd...
|
ComSpec
causes issues: /usr/bin/bash: /s: No such file or directory
uber-juno
Important info containing links:
uber-juno
#482 (comment)uber-juno
#482 (comment)uber-juno
#482 (comment)New title:
Errors on installing
uber-juno
Old title was:
Dependence on
ComSpec
causes issues:/usr/bin/bash: /s: No such file or directory
Old report
well, this wasn't going to reach anywhere in the first place.
but, meanwhile, some other issues got some of the attention they needed. so, i thought to reframe just this description & title part of the issue to reflect that.
the new title will also look relatable elsewhere wherever this issue has appeared so far lol - all of which were about this new title: "Error on installing uber-juno"
Old title was:
Dependence on
ComSpec
causes issues:/usr/bin/bash: /s: No such file or directory
On clicking/expanding this para, the old report will appear under this horizontal line:
Thanks in advance for your bug report!
What happened?
Pulsar version
1.103.0
Which OS does this happen on?
🪟 Windows
OS details
Win 10 22H2
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
Open Settings (bottom right gear icon) > go to any (one or more) of the following:
atom://
protocol, example here):Installing “uber-juno@0.3.0” failed. Hide output…
Themes > Installed themes: ``Fetching outdated packages and themes failed. Hide output…
Fetching featured packages failed. Hide output…
Additional Information:
ComSpec: ...\bash.exe
The text was updated successfully, but these errors were encountered: