Stalled / orphaned processes when offline

[jokeyrhyme]

@dex4er reported this over here: npm/npm#17453 (comment)

litomore earned $40.00 by resolving this issue!

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[sindresorhus]

Yeah, would make sense to have a timeout in https://github.com/yeoman/update-notifier/blob/adf7af05330704fa43b7658ff4b3b168428d0eab/check.js#L9 that does process.exit() if nothing happens after a set period. Any suggestions what the timeout period should be?

[jokeyrhyme]

15 seconds? 30 seconds? I'm trying to imagine what a reasonable request would look like, even over a cellular network

I feel that 60+ seconds would be too long, and less than 5 seconds would be too short

Mental note: @sindresorhus likes Issue titles to be capitalised :P

[sindresorhus]

I was thinking 30 seconds. Normally the request should be done in less than a second.

[IssueHuntBot]

@IssueHunt has funded $40.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[IssueHuntBot]

@sindresorhus has rewarded $28.00 to @LitoMore. See it on IssueHunt

• 💰 Total deposit: $40.00
• 🎉 Repository reward(20%): $8.00
• 🔧 Service fee(10%): $4.00