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

atuin history list | head crashes #626

Closed
norpol opened this issue Nov 22, 2022 · 5 comments · Fixed by #927
Closed

atuin history list | head crashes #626

norpol opened this issue Nov 22, 2022 · 5 comments · Fixed by #927

Comments

@norpol
Copy link

norpol commented Nov 22, 2022

Running atuin history list | head will fail with the back-trace below.

atuin history list | head
2015-09-08 14:18:20     ping google.com      0s
2015-09-08 14:18:20     ping google.com      0s
2015-09-08 14:22:28     ass ftpfs       0s
2015-09-08 14:22:28     ass ftpfs       0s
2015-09-08 14:22:55     mkdir tmp-ftp   0s
2015-09-08 14:22:55     mkdir tmp-ftp   0s
2015-09-08 14:23:29     # curlftpfs google.at ./tmp-ftp/ -o user=google:password,allow_other    0s
2015-09-08 14:23:29     # curlftpfs google.at ./tmp-ftp/ -o user=google:password,allow_other    0s
2015-09-08 14:23:32     curlftpfs google.at ./tmp-ftp/ -o user=google:password,allow_other      0s
2015-09-08 14:23:32     curlftpfs google.at ./tmp-ftp/ -o user=google:password,allow_other      0s
thread 'main' panicked at 'failed to write history: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }', src/command/client/history.rs:115:50
stack backtrace:
   0:     0x55e797bbe1c3 - <unknown>
   1:     0x55e797be23ac - <unknown>
   2:     0x55e797bb8765 - <unknown>
   3:     0x55e797bbfa21 - <unknown>
   4:     0x55e797bbf6f3 - <unknown>
   5:     0x55e797bc00c3 - <unknown>
   6:     0x55e797bbffb7 - <unknown>
   7:     0x55e797bbe674 - <unknown>
   8:     0x55e797bbfce2 - <unknown>
   9:     0x55e7972d3f13 - <unknown>
  10:     0x55e7972d4063 - <unknown>
  11:     0x55e797319560 - <unknown>
  12:     0x55e797411c6c - <unknown>
  13:     0x55e79734ee68 - <unknown>
  14:     0x55e7973b9335 - <unknown>
  15:     0x55e79735e399 - <unknown>
  16:     0x55e7973b8fff - <unknown>
  17:     0x55e7973364d3 - <unknown>
  18:     0x55e7973ddf7b - <unknown>
  19:     0x55e79733a246 - <unknown>
  20:     0x55e7973bfe03 - <unknown>
  21:     0x55e79743fbc9 - <unknown>
  22:     0x55e797bb1db2 - <unknown>
  23:     0x55e79733d068 - <unknown>
  24:     0x7fa485a7d290 - <unknown>
  25:     0x7fa485a7d34a - __libc_start_main
  26:     0x55e7972d4245 - <unknown>
  27:                0x0 - <unknown>
@ellie
Copy link
Member

ellie commented Nov 22, 2022

Will dig into it later, but related: rust-lang/rust#46016

@mattgodbolt
Copy link
Contributor

Came here to report the same. Surprised rust doesn't have a solution to this. Low priority but an annoyance nonetheless :)

@conradludgate
Copy link
Collaborator

I can probably fix this pretty quickly, given the fix suggested in the issue (using fallible write apis)

@ellie
Copy link
Member

ellie commented May 1, 2023

Will dig into it later, but related: rust-lang/rust#46016

I guess I got distracted, sorry 😭

I can probably fix this pretty quickly

conradludgate added a commit that referenced this issue May 1, 2023
@mattgodbolt
Copy link
Contributor

I guess I got distracted, sorry

lol don't give yourself a hard time please :) Though I've never been distracted by anything before in my life, so I guess it's oh look over there! a squirrel

@ellie ellie closed this as completed in #927 May 2, 2023
ellie pushed a commit that referenced this issue May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants