Jeremy Cline 80e950c648 fix(daemon): Add context to error when unable to connect (#2394) ... Recently, it seems, the socket location for the daemon moved and this caused me to scratch my head briefly since I saw errors from the client connecting to the daemon, but the daemon was clearly running and the socket seemed to exist. This patch includes more context when the client fails to connect to the daemon. The path is included to help the user understand where the client was looking, and `wrap_err_with()` is used to show the user the cause of the error. This changes the error message from: Error: failed to connect to local atuin daemon. Is it running? to: Error: failed to connect to local atuin daemon at /run/user/1001/atuin.sock. Is it running? Caused by: 0: transport error 1: No such file or directory (os error 2) 2: No such file or directory (os error 2)		2024-10-02 17:44:22 -07:00
..
proto	chore: remove unnecessary proto import (#2120)	2024-06-12 16:07:41 +01:00
src	fix(daemon): Add context to error when unable to connect (#2394)	2024-10-02 17:44:22 -07:00
build.rs	chore(build): compile protobufs with protox (#2122)	2024-06-12 16:45:38 +01:00
Cargo.toml	chore(release): prepare for release v18.4.0-beta.3 (#2305)	2024-07-23 13:38:41 +01:00