| Anonymous | Login | Signup for a new account | 12-18-2025 07:04 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0006300 | [Resin] | minor | always | 12-08-19 22:24 | 02-19-20 13:58 | ||||
| Reporter | nam | View Status | public | ||||||
| Assigned To | |||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 4.0.65 | Product Version | 4.0.64 | ||||
| Product Build | |||||||||
| Summary | 0006300: improve pdf-report downtime reporting at the beginning of the query range | ||||||||
| Description |
(rep by M. Shimomura) The pdf-report queries the internal log/stat database for downtimes. If the date for the query range cuts off some Resin lifecycle events, then Resin would report the beginning of the range as a downtime. It is misleading for downtime reporting to depend on the query range. The attached screenshot shows a 5-day downtime, which is not correct. We should: 1. improve docs and wording in pdf-report, and/or 2. do a backward scan of the database looking for the start event |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
| There are no notes attached to this issue. |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |