Hacker News Reader

I'm sorry you have such a painful bug, that must be frustrating. Here's hoping you get it soon :)

That’s great to hear, and glad the team is working on it! Thanks!

How can you know something is unrelated and yet still be trying to track it down? Are you running two versions of the code, in production, where this live action comparison is possible? Because if not this response reeks of Google/Microsoft engineers who always shift the blame.

It's not the Reason sections; if you've seen BuckleScript's output you'd know that the JS artifacts are almost like hand-written code. I've checked almost every diff.

Not sure how much I can say, but the leak is somewhere in the subscriptions, which isn't in Reason. Ironically the goal is to convert that section to Reason so that refactoring can finally be done (I've left that part out of the blog post just in case). Messenger produced the grandfather of Flux; it's not the easiest thing to refactor.

Proving that a given error isn't caused by X is a very different matter from working out what does cause it, and even after that, fixing it is another matter again.

What is the last part of your comment in reference to?

Try having an issue with Google or Microsoft services and get back to me on that.