TypeError: Cannot read property 'Muon' about overmind HOT 8 CLOSED

Are you on a shard other than shard2? The assimilator looks for my public memory segment to exchange validation keys, and I currently only have a presence on shard2.

from overmind.

Yes, people on shard 3 have been experiencing this problem

from overmind.

Correct was testing on shard3

from overmind.

I'll fix this in the 0.5.1 release, which I should have time to work on at the end of this quarter in mid December. Thanks for pointing it out.

from overmind.

@michaelblasdel Can you download the latest commit and see if this is still a problem? (The error would be thrown within 10 ticks of every 1000th tick.) I believe I've fixed the issue, but I can't test myself. If the error is still showing up, can you attach a screenshot of the fully expanded Memory.assimilator object?

from overmind.

Looks like it's still happening with the latest commit:

Memory.assimilator seems to be empty:

from overmind.

Thanks, that was helpful in isolating the problem. I think I have fixed the issue in the latest commit. Can you confirm this is working now? The problem appears to be that the Memory.assimilator.clearanceCodes property would get overwritten with undefined when trying to fetch my public memory from a shard I am not present on.

from overmind.

Yeap looks like it's working now.

from overmind.