View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010541 | Taler | merchant backend | public | 2025-10-30 18:03 | 2025-11-22 22:07 |
| Reporter | Florian Dold | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.2 | Fixed in Version | 1.2 | ||
| Summary | 0010541: merchant response to /private/kyc flaky due to timing issues | ||||
| Description | Immediately after having added a bank account to a merchant backend instance the GET /private/kyc request sometimes returns a 204 No content response, even when we expect a 200 Ok response. Whether we get 204 or 200 seems to depend on the timing, the merchant temporarily claims that no KYC is required, but maybe simply wasn't able to contact the exchange yet. | ||||
| Steps To Reproduce | Use taler-harness to run one of the tests below. Only happens sometimes / on some machines, depending on the timing. { "name": "tops-aml-custom-addr-postal", "timeSec": 1.763, "status": "fail" }, { "name": "tops-aml-custom-addr-sms", "timeSec": 1.751, "status": "fail" }, { "name": "tops-aml-kyx-natural", "timeSec": 1.759, "status": "fail" }, { "name": "tops-aml-measures", "timeSec": 1.766, "status": "fail" }, { "name": "tops-aml-legi", "timeSec": 1.753, "status": "fail" }, { "name": "tops-challenger-twice", "timeSec": 1.762, "status": "fail" }, | ||||
| Tags | No tags attached. | ||||
| e4d78aa6..f1af21e4 fixes this in the backend, alas the tests still fail like this: "" FATAL: test failed with exception AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: + actual - expected + 'exchange-unreachable' - 'kyc-wire-required' "" Note that "exchange-unreachable" is a perfectly good answer if we didn't have time to reach the exchange yet, and should obviously be acted on by waiting + trying again. | |
| Already fixed a while ago. kyc-merchant-deposit-rewrite still fails, but for a completely different reason. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-10-30 18:03 | Florian Dold | New Issue | |
| 2025-10-30 18:03 | Florian Dold | Status | new => assigned |
| 2025-10-30 18:03 | Florian Dold | Assigned To | => Christian Grothoff |
| 2025-10-30 20:40 | Christian Grothoff | Note Added: 0026286 | |
| 2025-10-30 20:40 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2025-11-17 13:25 | Florian Dold | Status | assigned => informing |
| 2025-11-17 13:25 | Florian Dold | Resolution | open => fixed |
| 2025-11-17 13:25 | Florian Dold | Note Added: 0026506 | |
| 2025-11-22 22:07 | Christian Grothoff | Fixed in Version | => 1.2 |
| 2025-11-22 22:07 | Christian Grothoff | Status | informing => closed |