shell-pool / shell-pool/shpool

error message does not identify source

Open
#383 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2k
Forks
67
Avg merge
3d 1h
Merged PRs (30d)
15

Description

AI Policy: acknowledged

What happened
When I connect into my remote host, I see:
warning: client protocol ("0.4.1") is newer than daemon protocol (version "0.3.5"), try restarting your daemon

This is apparently #377 , originating from shpool. but I am not here to report that there is a mismatch. Instead I am reporting that the error message is not helpful. there is no indication that shpool is the source of this message. because I am using shpool through another layer (an internal tool called "roadwarrior" invokes it), and because my shell is starting up so it runs through .bash_profile and so on, it was not clear to me, immediately, what program or tool was issuing this message.

What I expected to happen
Something like
shpool warning: client protocol ("0.4.1") is newer than daemon protocol (version "0.3.5"), try restarting your daemon

or

warning: shpool client protocol ("0.4.1") is newer than daemon protocol (version "0.3.5"), try restarting your daemon

More info
I restarted the shpool daemon and the message went away.

I am not sure WHY shpool needed to be restarted. My machine had just restarted two days ago as part of periodic maintenance. I had the latest shpool already. Anyway I'm not interested in spending time to diagnose that.

The main point here is to suggest the message is less than 100% helpful when shpool is used in this way.

Version info

$ shpool version
shpool 0.10.2 (cl/929545807)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the Rust source for the exact client/daemon protocol warning shown in the issue, then inspect nearby error-reporting code and any related tests. Done means the warning identifies shpool as its source while preserving the protocol versions and restart guidance, with the relevant tests still passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.