mirror of
https://github.com/agrinman/tunnelto.git
synced 2026-04-26 01:06:01 +03:00
[GH-ISSUE #13] Crash handling #11
Labels
No labels
Need more info
bug
duplicate
enhancement
good first issue
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tunnelto#11
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?
Originally created by @jchristn on GitHub (Jul 20, 2020).
Original GitHub issue: https://github.com/agrinman/tunnelto/issues/13
Improve the user experience by automatically sending crash reports (rather than requesting the user do it) and restarting the tunnel. I don't have a way to see that a tunnel is down unless I look at my console window, and finding the crash report is tedious. Cheers
@agrinman commented on GitHub (Jul 21, 2020):
Noted thanks. It's not entirely clear how to do this in a privacy preserving way. Maybe a command
tunnelto send-crash-reportsor something...@agrinman commented on GitHub (Jul 21, 2020):
Btw looking into your crash reports -- these should never be happening in the first place so something is wrong...
@jchristn commented on GitHub (Jul 21, 2020):
What other information can I provide to help debug?
@jchristn commented on GitHub (Aug 11, 2020):
Dunno what you did but it's been steady forever now. Thanks!