Corey O'Connor

I've been on the lookout for this occurring again. So far: Nothing. Working as expected!

Unfortunately just ran into this again. This code is not open source but the setup is about the same: A dependency hash that was working (probably 6 months ago?) that...

The corruption I've been observing is: Message added to the wrong thread. EG: A thread for number 123-5455 will get messages added to it that should have gone to thread...

An example of one type of "corruption". The selected thread is "20..." while the number for the thread is "(30...". Which is a number for a different thread.  This...

Right when I thought I would be unable to repro this after deleting messages: Found a case. This persists across application restarts. The screenshot is redacted but hopefully shows the...

@Gedochao ah darn. I did the revert wrong. The issue seems to the reverts to `Recurse` that were included incorrectly. I will fix shortly.

the mimi revision is incorrect.

The latest commit resolves the bin compat check (probably.. just realized I should try it myself presuming I can) The commit "resolved" the issue by re-adding the changes to the...

@Gedochao oof I'm sorry. I will fully investigate. I suspect I either have to: 1. change the bincompat target ; 2. Or actually implement Recurse with prefix properly and not...

also applies to 3.6. Tho the error message is now `No given instance of type fastparse.ParsingRun[$]` The change I applied is: ``` parse("a", parseA(using _)) ``` which is easier than...