View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006967 | Taler | exchange | public | 2021-07-29 17:24 | 2021-09-02 16:14 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | 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 | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.8 | Fixed in Version | 0.8 | ||
| Summary | 0006967: bad error reporting in taler-exchange-offline | ||||
| Description | taler-exchange-offline@buster:/home/vagrant/repos$ taler-exchange-offline download Jul 29 03:51:50-834402 taler-exchange-offline-15436 WARNING External protocol violation detected at json.c:781. Jul 29 03:51:50-834522 taler-exchange-offline-15436 WARNING External protocol violation detected at json.c:807. Jul 29 03:51:50-834552 taler-exchange-offline-15436 ERROR Unexpected response code 0/10 for exchange management get keys Jul 29 03:51:50-834574 taler-exchange-offline-15436 ERROR Failed to download keys: (null) (HTTP status: 0/10) | ||||
| Tags | No tags attached. | ||||
| Actually, the taler-exchange-offline tool tries to connect to [exchange]/base_url. The default for this is a port on localhost that is unbound in my environment, but the error message doesn't make *anything* clear. taler-exchange-offline@buster:/home/vagrant/repos$ taler-config -s exchange -o base_url http://localhost:8081/ | |
| Well, technically an HTTP status of '0' always means that we could not talk to the HTTP server. | |
| Sure, but how is a sysadmin supposed to find out easily which server the program is trying to talk to, if we don't print any of this information? Also, I'm not sure why we're doing JSON parsing here. | |
| d821db36..c0d4a35a fixes this, avoiding both the JSON parse logging and also now reporting the bogus URL in the log. | |
| Fix committed to master branch. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-07-29 17:24 | Florian Dold | New Issue | |
| 2021-07-29 17:24 | Florian Dold | Status | new => assigned |
| 2021-07-29 17:24 | Florian Dold | Assigned To | => Christian Grothoff |
| 2021-07-29 17:28 | Florian Dold | Note Added: 0018025 | |
| 2021-07-29 21:04 | Christian Grothoff | Note Added: 0018026 | |
| 2021-07-30 09:37 | Florian Dold | Note Added: 0018030 | |
| 2021-07-30 12:24 | Christian Grothoff | Status | assigned => informing |
| 2021-07-30 12:24 | Christian Grothoff | Resolution | open => fixed |
| 2021-07-30 12:24 | Christian Grothoff | Fixed in Version | => 0.8 |
| 2021-07-30 12:24 | Christian Grothoff | Note Added: 0018031 | |
| 2021-07-30 12:24 | Christian Grothoff | Product Version | => git (master) |
| 2021-07-30 12:24 | Christian Grothoff | Target Version | => 0.8 |
| 2021-08-24 14:22 | Christian Grothoff | Status | informing => closed |
| 2021-09-02 16:13 | Christian Grothoff | ||
| 2021-09-02 16:14 | Christian Grothoff | Note Added: 0018223 |