Skip to content
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

Setting db_path errors "no rows" #1236

Closed
deas opened this issue Sep 17, 2023 · 1 comment
Closed

Setting db_path errors "no rows" #1236

deas opened this issue Sep 17, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@deas
Copy link

deas commented Sep 17, 2023

Describe the bug
In config.toml whenever I set db_path, such as

db_path = "~/.local/share/atuin/history-nu.db

I get errors:

Error: no rows returned by a query that expected to return at least one row

To Reproduce
Steps to reproduce the behavior:

  1. Customize db_path in config.toml

Expected behavior
No error ;)

Error logs
n/a

Device (please complete the following information):

  • OS: Linux
  • Shell n/a
  • Version : 16.0.0

Additional context
I am trying to keep separate histories for zsh and nushell as I am trying to migrate to the latter - because they are very different. ;) I use ATUIN_CONFIG_DIR to point the nushell instance to a dedicated config file.

I understand that to maintain separate histories for both shells, I most likely also need to customize key_path and session_path and create a separate registrations to get sync across machines to work.

@deas deas added the bug Something isn't working label Sep 17, 2023
@conradludgate
Copy link
Collaborator

I think I understand why you get this error. I will assume that you edited your config using a terminal based editor:

  1. You start your editor. The editor command is saved into the original database and the ID is saved for later
  2. You edit the config
  3. You exit the editor, the ID for the command is not found in the new database

I don't think this error is very actionable. I'm open to ignoring them

conradludgate added a commit that referenced this issue Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants