-
Notifications
You must be signed in to change notification settings - Fork 974
Tabbycat errors with uncaught exception. #9871
Comments
@diasdavid I was not able to reproduce the issues you experienced. If you like, we can hop on a call later (Skype or GoogleHangout) and run through the exercise together. I tested with the following configuration:
|
This is super weird. Just did a fresh clone and npm install from master. Went through the steps in the blog post and got the same erros: This screen happens as soon as I turn on tabbycat
Could this be a MacOS thing? Let me get a VM to try it again |
Ok, full vm installed all all the things that Windows needs. In windows it doesn't throw uncaught exceptions, but I also don't get any cat on new tabs.
|
@jonathansampson I take your invite for a Google Hangout / Zoom Call, I believe we could use some sync time to go through multiple things in the IPFS endeavour. I'm in Lisbon (UTC+1) and I'm free in the evening today |
Closing this after our call. I think the issue here was the state of the |
Did you search for similar issues before submitting this one? Yes
Describe the issue you encountered: tabbycat
Platform (Win7, 8, 10? macOS? Linux distro?): Mac OS X 10.12.15
Brave Version (revision SHA):
db1e1bc953e83c47a08235108576d0c1dc15e3ea
Steps to reproduce:
Actual result:
On step 3, we get an uncaught exception:
On step 4 we get an unlimited number of Uncaught Exceptions:
No errors. a new cat on each tab
Yes. I've repeated this process multiple times.
Yes
Yes
Extra QA steps:
1.
2.
3.
Screenshot if needed:
The text was updated successfully, but these errors were encountered: