View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007900 | Taler | exchange | public | 2023-08-02 22:18 | 2023-09-23 13:09 |
| Reporter | Windfisch | 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 | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.2 | ||||
| Fixed in Version | 0.9.3 | ||||
| Summary | 0007900: taler-exchange-wirewatch --longpoll-timeout option is in microseconds | ||||
| Description | The --longpoll-timeout option for taler-exchange-wirewatch needs to be given in microseconds, i.e. 1000000 for a 1 second timeout. While technically, the --help option does not even specify the unit, i would expect it to be either in seconds or milliseconds. Please clarify the --help string here :) | ||||
| Steps To Reproduce | run taler-exchange-wirewatch -f 1000 and be surprised that every millisecond(!), a long polling call is made (or, tried to...) | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-08-02 22:18 | Windfisch | New Issue | |
| 2023-08-02 22:18 | Windfisch | Status | new => assigned |
| 2023-08-02 22:18 | Windfisch | Assigned To | => Christian Grothoff |
| 2023-08-03 16:41 | Christian Grothoff | Note Added: 0020405 | |
| 2023-08-03 16:41 | Christian Grothoff | Status | assigned => informing |
| 2023-08-03 16:41 | Christian Grothoff | Resolution | open => fixed |
| 2023-08-03 16:41 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2023-09-23 13:09 | Christian Grothoff | Status | informing => closed |