Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Remote] Session history refreshes too slowly

Open
#2,361 0 comments 0 reactions 0 assignees View on GitHub

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

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

  1. Open BitFun Remote.
  2. Create or update a session in the desktop client.
  3. Watch the remote session history without manually reloading the page.
  4. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GCWing/OpenBitFun

All issues in GCWing/OpenBitFun

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.