rays/ipx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 18 Wiki Activity

Refresh buttons should turn from the press to the end of that scan #233

New Issue
Closed
opened 2026-10-14 07:58:21 -07:00 by rays · 1 comment
rays commented 2026-10-14 07:58:21 -07:00
Owner
Copy Link

The refresh buttons (check every feed, a feed's or folder's own) turned while any feed they cover was being checked, so between feeds they stopped (#231), and a 600 ms hold papered over it. They should start when pressed and stop when the scan asked for ends: scan_done says which feed it was limited to and whether it was asked for (forced), so a scheduled scan ending first does not stop a button whose scan is queued behind it. Asked for 2026-10-14.

The refresh buttons (check every feed, a feed's or folder's own) turned while any feed they cover was being checked, so between feeds they stopped (#231), and a 600 ms hold papered over it. They should start when pressed and stop when the scan asked for ends: scan_done says which feed it was limited to and whether it was asked for (forced), so a scheduled scan ending first does not stop a button whose scan is queued behind it. Asked for 2026-10-14.
rays added the enhancement label 2026-10-14 07:58:21 -07:00
rays commented 2026-10-14 08:03:34 -07:00
Author
Owner
Copy Link

Fixed in a5e64e5, deployed (ipx 1.1.1-dev, ipx-web 1.0.2-dev): pressing a refresh button starts it; scan_done now carries only and forced (live: {"ev":"scan_done","feeds":1,"only":"gizmodo","forced":true}), and the page stops the button at the end of the scan it asked for, or on an error event. Replaces 7ecbe82's 600 ms hold.

Fixed in a5e64e5, deployed (ipx 1.1.1-dev, ipx-web 1.0.2-dev): pressing a refresh button starts it; scan_done now carries only and forced (live: {"ev":"scan_done","feeds":1,"only":"gizmodo","forced":true}), and the page stops the button at the end of the scan it asked for, or on an error event. Replaces 7ecbe82's 600 ms hold.
rays closed this issue 2026-10-14 08:03:35 -07:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
rays
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#233
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?