8000 `next` tracking PR for `3.1.0` by augustoccesar · Pull Request #229 · mentimeter/linkup · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

next tracking PR for 3.1.0 #229

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

Merged
merged 7 commits into from
Apr 14, 2025
Merged

next tracking PR for 3.1.0 #229

merged 7 commits into from
Apr 14, 2025

Conversation

augustoccesar
Copy link
Collaborator
@augustoccesar augustoccesar commented Apr 9, 2025

When trying to run `local` or `remote` when either have never ran
`start` or when the local server is not running, the error that the
users face is not great.
This should improve the understanding of what is wrong.

### Current errors

When calling before an initial `start`:
```
Error: Failed to read state file
```

When calling with local server stopped:
```
Error: WorkerClientErr(Reqwest(reqwest::Error { kind: Request, url: "http://localhost:8080/linkup/local-session", source: hyper_util::client::legacy::Error(Connect, ConnectError("tcp connect error", Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })) }))
```

### New errors
When calling before an initial `start`:
```
Seems like you don't have any state yet to point to local.
Have you run `linkup start` at least once?
```

When calling with local server stopped:
```
Seems like your local Linkup server is not running. Please run `linkup start` first.
```

Closes SHIP-2024
@augustoccesar augustoccesar self-assigned this Apr 9, 2025
augustoccesar and others added 6 commits April 9, 2025 16:09
This should improve the feedback when running `status` and `health` for
the first time. Instead of erroring out when missing the state, this
should point the users to the reason why information is wrong/missing.

Closes SHIP-2060

---------

Co-authored-by: Charlotte Andersson <charlotte.andersson@mentimeter.com>
This should make it easier to see from which version to which version
you are going when updating.
The update message was previously interfering with j
9426
son outputs, for
example. This changes so that the message doesn't show on cases where it
is not relevant. Those being:
- `completion` command.
- `health` command when the json output is requested.
- `status` command when the json output is requested.
- `uninstall` command, since the user is already uninstalling.
- `update` command, since the user is already updating.

Closes SHIP-2028
@augustoccesar augustoccesar marked this pull request as ready for review April 14, 2025 07:07
@augustoccesar augustoccesar changed the title feat: next tracking next tracking PR for 3.1.0 Apr 14, 2025
@augustoccesar augustoccesar merged commit 5ee51b0 into main Apr 14, 2025
11 checks passed
@augustoccesar augustoccesar deleted the next branch April 14, 2025 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0