Congrats to the team for the launch! I helped build a part of this in the past.
The repo is complex but at its core, this is software to record execution without the performance & storage penalty that would usually come with recording all of production.
To do that, they need to make sure that they record anything this is not deterministic, while leaving code that is deterministic to be executed during replay time.
To be honest, I think this is a really hard problem, almost impossible I'd say. There's just so many things that can cause the same execution to cause different results. But last I've seen, the team is slowly squashing each of the edge cases. I think they've now gotten it to be quite stable.
If everything goes well, this is very exciting and I think can revolutionise how we debug production code as an industry. I unfortunately don't run Python code so I can't meaningfully test this. Here's hoping it takes off and one day it'll be ported to the languages I use!
Congrats to the team for the launch! I helped build a part of this in the past.
The repo is complex but at its core, this is software to record execution without the performance & storage penalty that would usually come with recording all of production.
To do that, they need to make sure that they record anything this is not deterministic, while leaving code that is deterministic to be executed during replay time.
To be honest, I think this is a really hard problem, almost impossible I'd say. There's just so many things that can cause the same execution to cause different results. But last I've seen, the team is slowly squashing each of the edge cases. I think they've now gotten it to be quite stable.
If everything goes well, this is very exciting and I think can revolutionise how we debug production code as an industry. I unfortunately don't run Python code so I can't meaningfully test this. Here's hoping it takes off and one day it'll be ported to the languages I use!
[dead]
[dead]
[dead]