View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010578 | Taler | documentation | public | 2025-11-10 22:00 | 2025-11-11 11:28 |
| Reporter | htgoebel | 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 | text | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.0 | ||||
| Target Version | 1.2 | Fixed in Version | 1.2 | ||
| Summary | 0010578: microseconds? | ||||
| Description | Followup to "0010565: nanoseconds?", just to be sure: RelativeTime { // Duration in microseconds or "forever" Timestamp uses seconds, but RelativeTime uses microseconds? | ||||
| Tags | No tags attached. | ||||
| Yes, that's correct. Timestamps can be large values (so microseconds would not fit in JavaScript constraints!). OTOH, for relative times, it is often good to be able to have high precision and GNUnet internally uses microseconds. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-10 22:00 | htgoebel | New Issue | |
| 2025-11-11 11:28 | Christian Grothoff | Note Added: 0026371 | |
| 2025-11-11 11:28 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-11-11 11:28 | Christian Grothoff | Status | new => informing |
| 2025-11-11 11:28 | Christian Grothoff | Resolution | open => no change required |
| 2025-11-11 11:28 | Christian Grothoff | Fixed in Version | => 1.2 |
| 2025-11-11 11:28 | Christian Grothoff | Status | informing => closed |
| 2025-11-11 11:28 | Christian Grothoff | Product Version | => 1.0 |
| 2025-11-11 11:28 | Christian Grothoff | Target Version | => 1.2 |