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

{.async: (raises).} for relay/utils.nim #1058

Merged
merged 1 commit into from
Mar 7, 2024

Conversation

etan-status
Copy link
Contributor

Annotate relay/utils module with {.async: (raises).}. These build on top of writeLp and can be updated independently of the rest of libp2p.

Annotate `relay/utils` module with `{.async: (raises).}`. These build on
top of `writeLp` and can be updated independently of the rest of libp2p.
Copy link

codecov bot commented Mar 6, 2024

Codecov Report

Attention: Patch coverage is 95.65217% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 82.77%. Comparing base (ae13a0d) to head (a7fa2dc).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##           unstable    #1058      +/-   ##
============================================
- Coverage     82.79%   82.77%   -0.03%     
============================================
  Files            91       91              
  Lines         15749    15753       +4     
============================================
- Hits          13040    13039       -1     
- Misses         2709     2714       +5     
Files Coverage Δ
libp2p/protocols/connectivity/relay/utils.nim 94.44% <95.65%> (-2.11%) ⬇️

... and 3 files with indirect coverage changes

@arnetheduck arnetheduck merged commit 61b299e into unstable Mar 7, 2024
11 checks passed
@arnetheduck arnetheduck deleted the dev/etan/ex-relayutils branch March 7, 2024 09:45
@etan-status
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: done
Development

Successfully merging this pull request may close these issues.

2 participants