2026-07-11 - 2026-10-11
Overview
7 pull requests proposed by 1 user
Proposed
#55 Make all migrations idempotent
Proposed
#56 Lightning payment idempotency gate + listener resilience
Proposed
#57 Settlement balance guards, per-currency netting, Decimal rates
Proposed
#58 Fava client hardening: write-lock coverage, shared HTTP client, JSON assertions
Proposed
#59 Auth exact-matching, review-race guards, centralized account-name validation
Proposed
#60 Hygiene sweep: dead code, role-assignment race, cached user lookup, stale files
Proposed
#61 Split views_api into a domain package; unshadow /accounts/hierarchy
17 unresolved conversations
Open
#36
crud.create_account leaks sqlalchemy IntegrityError on duplicate name
Open
#35
JournalEntry.flag in API response misreports receivable/revenue as PENDING
Open
#53
add-account makes two serialized Fava round-trips (add_account, then get_all_accounts)
Open
#54
Cleanup: single source of truth for account roots; drop no-op per-test rate-limit reset
Open
#52
Escape Beancount strings at the add_account writer boundary, not just the metadata-value branch
Open
#39
POST /api/v1/assertions broken — submits Beancount source string to Fava JSON API
Open
#51
Centralize account-name validation into a shared module; apply to all creation paths
Open
#23
reject_pending_entry bypasses FavaClient write lock
Open
#38
validate_metadata leaks decimal.InvalidOperation on bad fiat_amount
Open
#18
Design: choose unit-of-account convention (fiat-first vs bitcoin-first) and migration path
Open
#16
Allow income receipt to settle another user's receivable (debt assumption)
Open
#15
Permission dropdown allows mismatched account-type / permission-type combinations
Open
#7
Obscure user IDs in accounting display
Open
#19
Outstanding Balances actions: per-currency settlement when directions diverge
Open
#8
Security: User ID exposure in Beancount ledger accounts
Open
#2
Add Refund entry type to accounting spec
Open
#10
Add team budget system with spending limits