Rob Gilson

@krisnye You didn't mention a solution and then you closed the bug. If you have fixed this bug then please post your solution. If the bug is not fixed then...

@michaelficarra I suspect this bug was closed by mistake. I am seeing this same issue in 2.0.0-beta 6. Can you reopen it please?

@krisnye Ahh, my mistake. Sorry about that!

Removing ActiveUUID fixes the problem. So the uuid column type patch should not be applied for rails 4.0.2+ (and possibly earlier versions as well).

@claude Sorry, that was all from a year ago on my end. I can't recall the details of the issue any more then what I wrote above. **Edit:** Not sure...

Yeah. It's actually baked into Rails 4 so we just use the built in helpers now (instead of activeuuid). Here's an example: http://johnkolovos.blogspot.ca/2014/10/rails-4-uuid.html

np, good luck!

I'll add my use case as well then, I'm porting a ECDH Triple Diffie–Hellman key exchange to wasm - targeting the browser. I'm using it (implemented in JS atm) for...

@ooflorent Thanks! I had a think last night and there's a bunch of changes I want to make which would break all sorts of backwards compatibility. So I'm thinking it...

> At the end of the day though, if you cannot churn through messages fast enough given the external constraints, you have to start dropping them eventually and that case...