-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Clean install of v9.1.0.42520: Nothing happens. No error. No logs. #16683
Milestone
Comments
Regression of #16566. |
dkocher
added a commit
that referenced
this issue
Dec 18, 2024
Register AutoServiceLoader in Terminal
Thanks @dkocher for the prompt response (and fix). Newbie here. Is there some kind of nightly build available for testing this? Or when can we expect a 9.1.1 release? Just asking because I'm in the middle of a process wanting to adopt duck cli. |
Hey @fdcastel, the update 9.1.1 was just released, and fixes the issue you've reported. |
Thank you guys. It is working now! 👍🏻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Nothing happens on duck cli. Not even
duck --help
works.To Reproduce
choco install duck -y
duck --help
. Nothing happens.$LASTEXITCODE
returns 1.duck --upload ...
. Nothing happens.$LASTEXITCODE
returns 1.duck --upload ... --verbose
. Nothing happens.$LASTEXITCODE
returns 1.duck --upload ... --debug
. Nothing happens.$LASTEXITCODE
returns 1.Expected behavior
Program should at least display SOME error information about what is going wrong.
Desktop (please complete the following information):
Log Files
There is no
%AppData%\cyberduck
folder (!)Additional context
Tried to reboot the computer. Still doesn't work.
However, I did notice that running just
duck
without parameters produces some output:I also created the
%AppData%\cyberduck
folder manually. Problem still persists.Nothing is logged on Windows Event Viewer / Administrative Events.
At least some error message should be produced whenever the last exit code is non-zero.
The text was updated successfully, but these errors were encountered: