nicohman/wyvern

Crash

Closed this issue · 1 comments

Because I wanted to see what error message I got I altered the refresh_token and got the following error. Exit code 101,

It asked to file a bug report, so here it is.

I am guessing it should rather detect that he login information is not valid, and ask you to login again?

Well, this is embarrassing.

wyvern had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "/tmp/report-a20b3f83-f898-4b04-9992-87539dcec20f.toml". Submit an issue or email with the subject of "wyvern Crash Report" and include the report as an attachment.

- Authors: nicohman <nicohman@demenses.net>

We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!

Crash report

name = 'wyvern'
operating_system = 'unix:Unknown'
crate_version = '1.2.0'
explanation = '''
Panic occurred in file 'src/libcore/result.rs' at line 1009
'''
method = 'Panic'
backtrace = '''
stack backtrace:
   0: <no info> (0x55ff3e3723b6)
   1: <no info> (0x55ff3e371387)
   2: <no info> (0x55ff3e3712ad)
   3: <no info> (0x55ff3e2c9ca2)
   4: <no info> (0x55ff3e2c9187)
   5: <no info> (0x55ff3dfbcecb)
   6: <no info> (0x55ff3e3e21e9)
   7: <no info> (0x55ff3e3e1ca1)
   8: <no info> (0x55ff3e3e1b85)
   9: <no info> (0x55ff3e41449c)
  10: <no info> (0x55ff3dfe3c79)
  11: <no info> (0x55ff3dfb4dfb)
  12: <no info> (0x55ff3dfbe4ef)
  13: <no info> (0x55ff3e3e1b22)
  14: <no info> (0x55ff3e4064d9)
  15: <no info> (0x55ff3e3ee85a)
  16: <no info> (0x55ff3dfbcf44)
  17: <no info> (0x7fd72b670412)
  18: <no info> (0x55ff3dfaa15d)
  19: <no info> (0x0)'''

Just pushed commit 5042c44 that prints a clear error message and prompts the user to log into wyvern again when refreshing the GOG token fails. Thanks for letting me know!