View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007725 | Taler | mechant backend | public | 2023-02-24 01:51 | 2023-09-23 15:09 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | ||
| Summary | 0007725: merchant logs regarding reserve queries are non-actionable | ||||
| Description | Here's what I get in my deployment from the merchant. The private HTTP does not give any information about the error, and the logs do not give any information about which reserve or URL is concerned. Logs like this would make it totally impossible to know what's going on in production. 2023-02-24T00:45:38.813801+0000 taler-merchant-httpd-66(ZS6Z9GN0SEPRKAVCRT1M7ZMRT8) WARNING External protocol violation detected at exchange_api_reserves_get.c:167. 2023-02-24T00:45:38.813807+0000 taler-merchant-httpd-66(ZS6Z9GN0SEPRKAVCRT1M7ZMRT8) ERROR Unexpected response code 504/10 for reserves get 2023-02-24T00:45:47.704662+0000 taler-merchant-httpd-66(ZS6Z9GN0SEPRKAVCRT1M7ZMRT8) WARNING Did NOT detect response `<html>^M | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-02-24 01:51 | Florian Dold | New Issue | |
| 2023-02-24 01:51 | Florian Dold | Status | new => assigned |
| 2023-02-24 01:51 | Florian Dold | Assigned To | => Christian Grothoff |
| 2023-03-08 12:04 | Christian Grothoff | Note Added: 0019931 | |
| 2023-03-08 12:04 | Christian Grothoff | Status | assigned => resolved |
| 2023-03-08 12:04 | Christian Grothoff | Resolution | open => fixed |
| 2023-03-08 12:04 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2023-03-08 12:05 | Christian Grothoff | Product Version | => git (master) |
| 2023-03-08 12:05 | Christian Grothoff | Target Version | => 0.9.3 |
| 2023-09-23 15:09 | Christian Grothoff | Status | resolved => closed |
