Problem
After updating to 0.1.0-dev1 via the dashboard, clicking Rollback sometimes shows a toast "rollback failed" (no overlay) and the version stays on the current release. Backups exist (e.g. 20251211-034204, 20251211-034350), and rollback succeeds when called directly via the API/CLI, so failure seems specific to the dashboard-triggered background job/overlay timing.
Steps observed
Update to latest release from the dashboard (shows overlay).
Refresh page.
Click Rollback.
Toast reports failure; version does not change.
Current behavior
UI sometimes reports rollback failed; version remains at 0.1.0-dev1.
/api/update/rollback via curl or CLI sometimes works, so it may be a transient/background job timing or UI poll issue.
Expected
Overlay shows during rollback, and system reverts to previous backup reliably.
Notes
Backups on device: 20251211-034204, 20251211-034350 (both version 0.1.0-dev).
PIKIT_MANIFEST_URL and PIKIT_AUTH_TOKEN are set via systemd override; update/download works.
Need to inspect systemd-run rollback unit and UI poll/overlay timing for race conditions.
**Problem**
After updating to 0.1.0-dev1 via the dashboard, clicking Rollback sometimes shows a toast "rollback failed" (no overlay) and the version stays on the current release. Backups exist (e.g. 20251211-034204, 20251211-034350), and rollback succeeds when called directly via the API/CLI, so failure seems specific to the dashboard-triggered background job/overlay timing.
**Steps observed**
1. Update to latest release from the dashboard (shows overlay).
2. Refresh page.
3. Click Rollback.
4. Toast reports failure; version does not change.
**Current behavior**
- UI sometimes reports rollback failed; version remains at 0.1.0-dev1.
- /api/update/rollback via curl or CLI sometimes works, so it may be a transient/background job timing or UI poll issue.
**Expected**
- Overlay shows during rollback, and system reverts to previous backup reliably.
**Notes**
- Backups on device: 20251211-034204, 20251211-034350 (both version 0.1.0-dev).
- PIKIT_MANIFEST_URL and PIKIT_AUTH_TOKEN are set via systemd override; update/download works.
- Need to inspect systemd-run rollback unit and UI poll/overlay timing for race conditions.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
After updating to 0.1.0-dev1 via the dashboard, clicking Rollback sometimes shows a toast "rollback failed" (no overlay) and the version stays on the current release. Backups exist (e.g. 20251211-034204, 20251211-034350), and rollback succeeds when called directly via the API/CLI, so failure seems specific to the dashboard-triggered background job/overlay timing.
Steps observed
Current behavior
Expected
Notes