Ben Allen
Ben Allen
Playing around with it I made a minimal check on my fork just checking send/v2 https://github.com/benalleng/rust-payjoin/blob/mutants-out/mutants.out/missed.txt. But ultimately I am wondering how we should organize the outputs for tracking these...
How do we feel about including the flag `test_workspace = true` in our mutants workflow? This would include tests from all of our crates within the repo as laid out...
Baseline mutation test on all of `payjoin/src` ``` Found 533 mutants to test ok Unmutated baseline in 26.3s build + 16.3s test INFO Auto-set test timeout to 1m 22s MISSED...
Following our latest release https://github.com/payjoin/rust-payjoin/releases/tag/payjoin-1.0.0-rc.0 our msrv has been bumped to `1.85.0` alongside the debian-stable bump to the same msrv
I wanted to pose a question as to why we really need to have these 2 seperate instead of just having application devs use `fail()` OR `cancel()` and provide a...
In adding some coverage in #928 spacebear found that our spec has perhaps an unclear directive on what to do in the case of a malicious modification of the pjos...
with the redis stuff merged in what commits remain from this PR?
Closed as rebased into #1210
Feel free to open a PR on the ohttp-relay so we can take a look
The original intention from 4926384a655d0defdca9948babfaf218dc3bc1b1 was application dev convenience