mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[PR #4868] [MERGED] feat(desktop): update check timeout 2s -> 5s #4967
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#4967
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
📋 Pull Request Information
Original PR: https://github.com/hoppscotch/hoppscotch/pull/4868
Author: @CuriousCorrelation
Created: 3/10/2025
Status: ✅ Merged
Merged: 3/10/2025
Merged by: @jamesgeorge007
Base:
patch← Head:fix/desktop/fallback-timeout-after-builtin📝 Commits (1)
c23b0e4feat(desktop): increase updater timeout 5s📊 Changes
1 file changed (+10 additions, -5 deletions)
View changed files
📝
packages/hoppscotch-desktop/src/utils/updater.ts(+10 -5)📄 Description
This PR increases timeout for checking updates, mainly for slower internet connections. In most cases the update check returns almost immediately.
It also increases the fallback promise timeout to make sure there's indeed an issue with
checkand not a tie or other inconsistencies in the promise race.Notes to reviewers
You can test this out by connecting via slower network or network with major packet loss, sometimes the update check would fail and the app will continue with loading the main app.
Although even in that case it will work after a couple of restarts, so the worst case scenario is a delayed update.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.