@rohit nice job tracking that down. weird how it would affect the hash of :version as that is clearly not nil, but I guess we should not question JS. 😉

@thheller: as part of calculating the hash of a keyword, you need to calculate hash-string of its ns which in most cases is null. that was the root of the bug.

ah! that makes sense

nice catch, I was ready to blame imul again 😉

lol

so this is the sequence of things:

1. When the system starts cache contains nil as ”null" and its value is 0 2. We compute hash of :version taking that 0 into account. 3. Loads of operations such that the cache is reset. 4. We calculate the hash of ”null” as it is in a set. Now the value in the cache of ”null" is something other than 0 5. We create a new :version taking the new value of ”null" cache entry and try to compare its hash to earlier one and they do not match. 6. The whole system is now unstable.

yeah

seems obvious if you go through the steps 🙂

but not at all obvious at first

my colleague @skapoor pointed out the length of maps and imports affected point 3. hence the issue was only showing up under some very specific conditions.

luckily/unluckily we were hitting that magic number of cache entries

yeah it was extremely confusing that removing the def COLOURS in your example "fixed" the problem

but it created more hash keys so pretty obvious in hindsight

still, nice job.

cheers. and thanks for pointing to where to look. 🙏