[Remote] Session history refreshes too slowly
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- full-stack
Research direction
Start by tracing the web client's fixed-interval session-list polling and its relay requests, then inspect the session create, update, and delete paths. The change is done when newly created or modified sessions appear promptly without manual refresh, requests do not overlap, and the behavior is verified during active use.
Written by the indexing model from the issue text.
Description
Bug
The BitFun Remote session history is noticeably stale during active use. Newly created sessions and recent activity do not appear promptly.
Expected behavior
The session history should update promptly after a session is created or changed, without requiring a manual page refresh.
Actual behavior
The web client refreshes the session list on a fixed interval of roughly 10 seconds through relay requests. Network/relay queue latency can make the visible delay even longer.
Reproduction
- Open BitFun Remote.
- Create or update a session in the desktop client.
- Watch the remote session history without manually reloading the page.
- Observe that the change may remain missing for several seconds.
Environment
- BitFun 0.2.17
- macOS desktop client
- BitFun Remote web UI via relay
Suggested direction
Use a session-list event/push signal, or trigger targeted invalidation immediately after session create/update/delete operations. If polling remains necessary, avoid a fixed long interval and prevent overlapping list requests.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 236
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 619
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GCWing/OpenBitFun
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GCWing/OpenBitFun#3213 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
GCWing/OpenBitFun#2363 ·
-
question
Difficulty 1/5 Under an hour Newbie friendliness 78/100
GCWing/OpenBitFun#2340 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
GCWing/OpenBitFun#3210 ·
-
GCWing/OpenBitFun#3195 · 2 comments · 1 assignee ·
All issues in GCWing/OpenBitFun
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
zed-industries/zed#64680 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RustPython/RustPython#8802 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TheLarkInn/aipm#2390 ·