We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No atuin output.
atuin
After updating to 18.x from 17.x, I now see
Error: migration 20231127090831 was previously applied but is missing in the resolved migrations
after every command. I came across this post https://forum.atuin.sh/t/migration-was-previously-applied-but-is-missing-in-the-resolved-migrations/84 but it says do not delete for post 17.2. Is there a recommended action for 18.3.0?
❯ atuin doctor Atuin Doctor Checking for diagnostics Please include the output below with any bug reports or issues { "atuin": { "version": "18.3.0", "sync": null, "sqlite_version": "3.46.0" }, "shell": { "name": "zsh", "default": "zsh", "plugins": [ "atuin" ], "preexec": "built-in" }, "system": { "os": "Darwin", "arch": "x86_64", "version": "14.6.1", "disks": [ { "name": "Macintosh HD", "filesystem": "apfs" }, { "name": "Macintosh HD", "filesystem": "apfs" }, { "name": "OWC", "filesystem": "apfs" } ] } }
The text was updated successfully, but these errors were encountered:
Have you ever ran any builds from source, or only ever binary releases from our releases page or your package manager?
Sorry, something went wrong.
Only binary releases using curl on macOS.
curl
No branches or pull requests
What did you expect to happen?
No
atuin
output.What happened?
After updating to 18.x from 17.x, I now see
after every command. I came across this post https://forum.atuin.sh/t/migration-was-previously-applied-but-is-missing-in-the-resolved-migrations/84 but it says do not delete for post 17.2. Is there a recommended action for 18.3.0?
Atuin doctor output
Code of Conduct
The text was updated successfully, but these errors were encountered: