-
Notifications
You must be signed in to change notification settings - Fork 165
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
Litestream error on restore #573
Comments
@danielmichaels - Thanks for the heads up! It looks like it was a breaking change in Litestream that I missed: Fix should just be to remove the |
danielmichaels
added a commit
to danielmichaels/picoshare
that referenced
this issue
Jun 7, 2024
Addresses mtlynch#573 Removing `-v` from the `litestream restore` command as it is now the default.
mtlynch
pushed a commit
that referenced
this issue
Jun 7, 2024
Addresses #573 Removing `-v` from the `litestream restore` command as it is now the default.
Fixed in #574 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey mate,
I updated my picoshare instance this morning and it failed to start.
The error I am getting is:
ERROR failed to run error="flag provided but not defined: -v"
I am using the docker image. Reverting from
1.4.3
(latest) to1.4.2
fixed the issue.Repro:
Working version:
docker run --rm -it --entrypoint bash mtlynch/picoshare:1.4.2
# /app/litestream restore -v -if-replica-exists database path or replica URL required
I have not provided the argument, this is expected behavior.
Error version:
docker run --rm -it --entrypoint bash mtlynch/picoshare:1.4.3
This is odd because the output indicates that
-v
is a valid flag.I suspect this could be an upstream issue but wanted to flag it here first.
Dan
The text was updated successfully, but these errors were encountered: