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

chore: upgrade to iroh@v0.31.0 #15

Merged
merged 2 commits into from
Jan 14, 2025
Merged

chore: upgrade to iroh@v0.31.0 #15

merged 2 commits into from
Jan 14, 2025

Conversation

ramfox
Copy link
Contributor

@ramfox ramfox commented Jan 7, 2025

Description

upgrade iroh, portmapper, netcheck, etc dependencies

Change checklist

  • Self-review.

@Arqu
Copy link
Contributor

Arqu commented Jan 7, 2025

For me this wasn't required to test. Doctor worked as expected regardless. It was purely the relay behavior that got stuck for me.

@ramfox
Copy link
Contributor Author

ramfox commented Jan 7, 2025

totally! I just did the update to rule out that being part of the issue.

@matheus23 matheus23 marked this pull request as ready for review January 13, 2025 10:29
@ramfox ramfox changed the title chore: point to the main branch of iroh chore: upgrade to iroh@v0.31.0 Jan 14, 2025
@ramfox ramfox merged commit 49ebd64 into main Jan 14, 2025
14 checks passed
@ramfox ramfox deleted the ramfox/iroh-main branch January 14, 2025 20:01
matheus23 added a commit that referenced this pull request Jan 29, 2025
Depends on #15 
(I need new iroh APIs.)

## Description

<!-- A summary of what this pull request achieves and a rough list of
changes. -->

Shows a close reason when the connection closes. E.g:
```
Test finished after 1.238599231s: connection lost (reason: closed by peer: 0)
```

This error message indicates that it's an *intentional* closing of the
connection.
Otherwise it's something like:
```
Test finished after 1.238599231s: connection lost (reason: timed out)
```

This makes it easier to identify how the connection was lost.

## Notes & open questions

<!-- Any notes, remarks or open questions you have to make about the PR.
-->
Additionally, we ideally know if *we* closed the connection or if that
was our peer. That info would be nice (but it's not as clear-cut,
technically both could have closed the connection).
Also - using different error codes might be nice, but `Endpoint::close`
doesn't support that yet. I'd like to at least separate a close from
Ctrl+C with a close from e.g. a panic/Err.

## Change checklist

- [x] Self-review.
- ~~[ ] Documentation updates following the [style
guide](https://rust-lang.github.io/rfcs/1574-more-api-documentation-conventions.html#appendix-a-full-conventions-text),
if relevant.~~
- ~~[ ] Tests if relevant.~~
- [x] All breaking changes documented.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants