Test suite trips LNbits rate limiter (429) when run in one pass #44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Symptom
Running the full suite in a single pytest invocation, the alphabetically-last test files (
test_settlement_api.py,test_void_reject_api.py) error in fixture setup:All affected tests pass when their file is run in isolation. The full suite (~120 tests in ~25s) simply exceeds LNbits' default
200 per 1 minuteslowapi limit from 127.0.0.1.Fix
Raise/disable the rate limit in the test session — conftest's
settingsfixture should set the relevant settings field (e.g.lnbits_rate_limit_no/lnbits_rate_limit_unit, whatever the dev branch exposes) so the suite isn't load-order sensitive. One-line change once the right knob is identified.Observed 2026-06-12 running the suite against lnbits/dev per tests/README.md.
🤖 Generated with Claude Code