View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010963 | Taler | libeufin-nexus | public | 2026-02-01 21:54 | 2026-02-01 21:56 |
| Reporter | Christian Grothoff | Assigned To | Antoine A | ||
| Priority | immediate | Severity | major | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.5 | ||||
| Summary | 0010963: incoming wire transfer with truncated subject did not get bounced | ||||
| Description | (psql) select * from libeufin_nexus.incoming_transactions where incoming_transaction_id=156; on *spec* (production!) shows an incoming wire transaction with a truncated wire transfer subject. However, there is no matching entry in the 'bounced_transactions' table, and (predictably) also none in the talerable_incoming_transactions table. I don't think that should be possible. Didn't check Postfinance activities yet, but would like an explanation/investigation. The logs are also not nice, the truncated wire transfer subject does not seem to have been logged at all. This should at least be a WARNING IMO. | ||||
| Tags | No tags attached. | ||||
|
|
select COUNT(*) from libeufin_nexus.incoming_transactions where incoming_transaction_id NOT IN (select incoming_transaction_id from libeufin_nexus.bounced_transactions) and incoming_transaction_id NOT IN (select incoming_transaction_id from libeufin_nexus.talerable_incoming_transactions); shows *12* transactions in this set right now. Antoine: Please explain or investigate! |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-01 21:54 | Christian Grothoff | New Issue | |
| 2026-02-01 21:54 | Christian Grothoff | Status | new => assigned |
| 2026-02-01 21:54 | Christian Grothoff | Assigned To | => Antoine A |
| 2026-02-01 21:56 | Christian Grothoff | Note Added: 0027535 |
