-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Installation script hangs at 100% without showing interactive prompt #692
Comments
@curlykay I ran this and it worked:
What shell are you using? I'm assuming zsh based on the snippet above. Can you try running the install script again with
|
I released 0.44.4 with some potential fixes for this. Let me know how it goes. |
I performed a reinstallation and obtained the following log: ~ % PROTO_DEBUG=true PROTO_LOG=trace bash -c 'curl -fsSL https://moonrepo.dev/install/proto.sh | bash'
######################################################################## 100.0%
[TRACE 2025-01-08 09:23:53.259] starbase_console::console Creating buffered console
[DEBUG 09:23:53.260] proto Running proto v0.44.4 bin="/Users/ck/.proto/bin/proto" args=["setup"] pid=44805
[TRACE 09:23:53.260] starbase::app Running startup phase
[DEBUG 09:23:53.260] proto_core::proto Creating proto environment, detecting store store="/Users/ck/.proto" home="/Users/ck"
[TRACE 09:23:53.260] starbase::app Running analyze phase
[DEBUG 09:23:53.260] proto::systems Loading configuration in upwards-global mode working_dir="/Users/ck"
[DEBUG 09:23:53.260] proto_core::proto_config Merging loaded configs with global
[DEBUG 09:23:53.261] proto_core::proto_config Merged 0 configs
[DEBUG 09:23:53.261] proto_core::proto_config Merging loaded configs without global
[DEBUG 09:23:53.261] proto_core::proto_config Merged 0 configs
[TRACE 09:23:53.261] starbase::app Running execute phase
[DEBUG 09:23:53.261] proto::commands::setup Determining the shell to use
[DEBUG 09:23:53.261] starbase_shell::shell Attempting to detect the current shell
[DEBUG 09:23:53.261] starbase_shell::shell Detecting from SHELL environment variable env="/bin/zsh"
[DEBUG 09:23:53.261] starbase_shell::shell Detected zsh shell
[DEBUG 09:23:53.261] proto::commands::setup Updating PATH in zsh shell
[DEBUG 09:23:53.261] proto::commands::setup Prompting the user to select a shell profile
[DEBUG 09:23:53.261] proto::shell Finding profile files for zsh After that, the only way to regain control of the terminal was still to forcibly close the terminal session. |
Hrmm so odd, let me try and recreate it somehow. |
Was able to reproduce it with this script!
It seems like piping is what causes it. If I remove the |
I temporarily updated the install.sh script to not prompt, so it should unblock people for now. |
When do I need to try again? |
I've just made the latest attempt and it's already installed without any problems, thanks for debugging! |
Fixed in the next version and once this lands: moonrepo/moon#1786 Had to change the command to install though so that stdin works correctly. |
What version?
0.44.3
Which command?
curl -fsSL https://moonrepo.dev/install/proto.sh | bash
What happened?
I'm experiencing an issue with the proto installation script:
When running the script:
curl -fsSL https://moonrepo.dev/install/proto.sh | bash
It hangs at 100% without any further output:
######################################################################## 100.0%
At this point, the terminal becomes unresponsive, and no further commands can be executed. The only way to regain control is to forcibly close the terminal session.
After restarting the terminal,the
~/.proto
binary is correctly downloaded, but there's no "interactive prompt" as mentioned in the documentation. The script seems unable to complete the installation process or display the expected prompt.However, I found a workaround: Using the command
curl -fsSL https://moonrepo.dev/install/proto.sh | bash -s -- --yes
skips the "interactive prompt". With this method, proto is correctly downloaded and the path is properly added to .zshrc. After restarting the terminal, I can use the proto command normally.Despite the workaround, could you please investigate why the original command doesn't show the interactive prompt as expected? This might confuse users who are following the standard installation instructions.
my context:
Trace logs?
No response
Operating system?
MacOS
Architecture?
arm64
The text was updated successfully, but these errors were encountered: