View Issue Details
Category | |||||
---|---|---|---|---|---|
SSPBT:本体(SSP) | |||||
Severity | major | Reproducibility | always | ||
Status | closed | ||||
Fixed in Version | 2.6 (リリース) | ||||
Summary | 0000578: Update full check does not report 404 errors and sometimes does not report MD5 errors | ||||
Description | When doing an update full check, I've noticed on multiple occasions that issues in the network updates aren't actually reported, so I end up having to fix updates after the fact. In the first screenshot attached, this was an example of MD5 errors showing as a warning while it was checking, but the end result was "Update OK" even though there were errors. In ghosts with a lot of files, the errors may go unnoticed because of the log limit, so it is an issue to me that the end result doesn't notify me that there were errors in the process. Additionally, it does not flag up 404 errors for me at all. The file simply does not appear in the log, which is very easily missed. This is demonstrated in the last two screenshots (the ones for the ghost "Balloons") SSP/2.6.30 (20230212-8; Windows NT 10.0.19045) | ||||
Tags | No tags attached. | ||||
Attach Tags | |||||
Attached Files | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2023-02-16 06:38 | guest | New Issue | |
2023-02-16 06:38 | guest | File Added: image.png | |
2023-02-16 06:38 | guest | File Added: image-2.png | |
2023-02-16 06:38 | guest | File Added: image-3.png | |
2023-02-16 13:58 | ponapalt | Assigned To | => ponapalt |
2023-02-16 13:58 | ponapalt | Status | new => assigned |
2023-02-16 13:58 | ponapalt | Status | assigned => confirmed |
2023-03-01 16:01 | ponapalt | Status | confirmed => closed |
2023-03-01 16:01 | ponapalt | Resolution | open => fixed |
2023-03-01 16:01 | ponapalt | Fixed in Version | => 2.6 (リリース) |
2023-03-01 16:01 | ponapalt | Note Added: 0001391 |