You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to vet my solution for Fly's distributed system challenge #5a but maelstrom seems stuck analyzing: it's been doing so for 45 minutes now and has produced 1.3GB of log output.
Not sure if this was your issue, but I was seeing long "Analyzing..." times and OOMs when I was using large offset numbers. I saw this issue and it made me realize there was this graphing working downstream. Maybe some of the visualization generation scales with these numbers. Changing my offset generation fixed it for me.
Not sure what your issue is but maybe that is relevant. Good luck.
Hello.
I'm attempting to vet my solution for Fly's distributed system challenge #5a but maelstrom seems stuck analyzing: it's been doing so for 45 minutes now and has produced 1.3GB of log output.
It's dumping what looks to be internal state relevant to plotting; you can see it at the tail end of the gist at https://gist.github.com/chronoslynx/6e8ac74b11159ab07d6ad7ca1304e5ef. The log was full of output like
I've replicated the issue with:
I can reliably reproduce this issue with my code at https://github.com/chronoslynx/gossip-glomers/blob/main/kafka/main.go
The text was updated successfully, but these errors were encountered: