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

[Bug]: No commands being stored #2511

Open
1 task done
sazzer opened this issue Dec 30, 2024 · 0 comments
Open
1 task done

[Bug]: No commands being stored #2511

sazzer opened this issue Dec 30, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@sazzer
Copy link

sazzer commented Dec 30, 2024

What did you expect to happen?

When running shell commands, the command should be stored into the history for later retrieval.

What happened?

The fact that a command was run is being stored, but the command itself isn't. This is making the tool pretty useless :(

When I run atuin history list I get output like this:

-> % atuin history list --format "{time} - {duration} - {command}"
2024-12-30 13:05:38 - 5ms -
2024-12-30 13:05:39 - 4ms -
2024-12-30 13:05:39 - 4ms -
2024-12-30 13:07:13 - 1m -
2024-12-30 13:08:37 - 4m -
2024-12-30 13:13:10 - 20ms -
2024-12-30 13:13:20 - 15s -
2024-12-30 13:13:37 - 0s -

And the timestamps correspond to when commands were run. However, as you can see there is no command stored against any of the entries.

I've also manually opened the SQLite database to have a look, and this is what's being stored:

-> % sqlite3 ~/.local/share/atuin/history.db
SQLite version 3.43.2 2023-10-10 13:08:14
Enter ".help" for usage hints.
sqlite> select id, timestamp, command from history;
019417ac0a6e7ca0875f296b8d87b704|1735563938414779000|
019417ac0cd57cf38c37ede81d461e91|1735563939029984000|
019417ac0eb471c29e772d1a1abb5126|1735563939508478000|
019417ad7ee27fe283c411f08f4a7229|1735564033762788000|
019417aec7b37fc3b9530aeb8ddb5923|1735564117939667000|
019417b0ebce7d719ff6911b0f8e4ca3|1735564258254438000|
019417b0edce74c38857c4fa85982bf2|1735564258766361000|
019417b0efc77413a662d3a81fdbc082|1735564259271386000|
019417b2f14c7ea28861f8f2d332dedb|1735564390732376000|
019417b315f27c00a55c5516f1d44b74|1735564400114849000|
sqlite> ^D

So you can see that the command column is just blank.

Things that I've tried to see if it made any difference - and none of them did:

  • Using both zsh and bash
  • Using both iTerm2 and Terminal.app
  • Using the recommended installation approach, cargo install atuin and brew install atuin (Uninstalling between each of those)
  • Deleting ~/.local/share/atuin in case anything was corrupted in there

The only thing I haven't done is to configure sync - which I'm less interested in using, and which I don't believe is relevant to what's going on here...

Atuin doctor output

{
  "atuin": {
    "version": "18.4.0",
    "sync": null,
    "sqlite_version": "3.46.0"
  },
  "shell": {
    "name": "zsh",
    "default": "zsh",
    "plugins": [
      "atuin"
    ],
    "preexec": "built-in"
  },
  "system": {
    "os": "Darwin",
    "arch": "arm64",
    "version": "14.7.2",
    "disks": [
      {
        "name": "Untitled",
        "filesystem": "apfs"
      },
      {
        "name": "Untitled",
        "filesystem": "apfs"
      }
    ]
  }
}

Code of Conduct

  • I agree to follow this project's Code of Conduct
@sazzer sazzer added the bug Something isn't working label Dec 30, 2024
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

1 participant