James Cropcho

Tomáš, Now that we've got this Docker stuff mostly figured out, are you able to reproduce Luke's issue or not so much? James

Luke, Please pardon—we don't seem able to reproduce. Are you still experience this issue? Any insight it weirdness of this collection which might cause an usual error? Or if not,...

Luke and Tomáš, I'm going to close this ticket/issue for now. By all means please feel free to re-open when we get more information or insights. Hope you two are...

Thank you for letting us know, David ( @hdavidzhu ). Wow, this sounds like it's likely quite a commonly encountered bug, and it's been around for two years! (Hence, our...

Hello Lucas, Thank you for writing to Variety. Hmm…I don't have any experience with MongoDB Shell (`mongosh`). Does anyone else here know what might be going on? Also, Lucas, if...

Hello, Charles: Thank you for using Variety, and on behalf of everyone involved than for your kind words! Indeed, what you reference is there in the documentation (https://github.com/variety/variety#see-progress-when-analysis-takes-a-long-time). I'm not...

@todvora I noticed that no checks ran for this PR—is that expected behavior?

Thank you, Michael. That is very helpful, as well as interesting. For the `lighthouse beacon_node` instance I was using a Xeon CPU with a whopping 4 GHz clock speed, however...

Again, thank you for the valuable guidance, Michael. Expecting no noticeable difference in performance I built the executable, on the `beacon_node` target/production machine (the aforementioned 3.5 GHz Ice Lake CPU)...

> Having a fast CPU helps, particularly one that supports ADX and SHA256 native instructions (e.g. all AMD Ryzen CPUs support this, and most modern Intel ones). Does this describe...