TimPietrusky
commented
2 months ago :tada: This issue has been resolved in version 1.0.0-alpha.66 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Closed pixelass closed 2 months ago
TimPietrusky
commented
2 months ago :tada: This issue has been resolved in version 1.0.0-alpha.66 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Describe the bug When attempting to update from Captain v1.0.0-alpha.60 to v1.0.0-alpha.61, the update process fails due to a 404 error on downloading the block map for the old version. The logs indicate an attempt to download block maps for differential updates, but because the block map for the older version (alpha.60) cannot be found on the server, the system falls back to a full download. The exact error message is:
Expected behavior The update process should smoothly transition between versions without errors. If differential updates cannot be performed, the system should handle such cases gracefully, perhaps with a retry mechanism or a clearer user notification about what is happening.
Versions (please complete the following information):
Additional context This issue may lead to user confusion and an interrupted update experience, which can negatively affect the perception of the platform's reliability. It might be beneficial to ensure that all necessary files for updates are available on the server before releasing updates or to improve the error handling and user notification system within the update process.