Closed aaronklaassen closed 6 years ago
SON OF A
Haha, well I guess that one is extra fixed now.
Oops, well I pushed it to the wrong branch anyway. I know how to Git
@mrmwiebe Hah sorry - I filed the issue, walked away, came back and went "ohhhhhhhhhhh".
I'll roll my commit into a PR that deals with #83 too (that's how I found this).
No prob!
error reporting broken lol
I'm not sure yet if this happens with all Oopses or just this early one. You can replicate it by forcing an error connecting to the Network (e.g., enter a garbage URL in the
sync.libraryURL
option). The GET fails, tries to Oops, and throws the above exceptions.