• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

payjoin / rust-payjoin / 13355590759
83%

Build:
DEFAULT BRANCH: master
Ran 16 Feb 2025 01:44PM UTC
Jobs 1
Files 36
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

16 Feb 2025 01:42PM UTC coverage: 79.127% (-0.1%) from 79.269%
13355590759

push

github

web-flow
Handle receiver contribution errors as `unavailable` (#534)

Our reference must not panic if input contribution fails, but instead
show best practice for a non-automated receiver where the sender may
choose to try to payjoin again or broadcast the transaction extracted
from the original PSBT.

This is an implementation of my best idea for receiver error handling in
[my
comment](https://github.com/payjoin/rust-payjoin/issues/403#issuecomment-2651486357)
in #403

After this I think the only things to stabilize receiver errors is to
decide whether the single-variant `ContributionError` is correct and to
mark errors as non-exhaustive, and potentially expose variants as
public.

12 of 23 new or added lines in 3 files covered. (52.17%)

4007 of 5064 relevant lines covered (79.13%)

908.39 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
11
15.65
-1.27% payjoin/src/receive/error.rs
Jobs
ID Job ID Ran Files Coverage
1 13355590759.1 16 Feb 2025 01:44PM UTC 36
79.13
GitHub Action Run
Source Files on build 13355590759
  • Tree
  • List 36
  • Changed 6
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #13355590759
  • 39cfaff2 on github
  • Prev Build on master (#13312127351)
  • Next Build on master (#13375398808)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc