I'm getting a horrendous amount of panics with the new version release 👀 Update: Nothing wrong with the new version, but having a cluster that installs getdaft in the ray runtime env without specifying the version could cause unexpected panics when there's version mismatches within the cluster

What’s going on? Any chance you could share the error message?

There's a whole bunch of things being printed I have no idea about, but rolling back to 0.3.5 seems to work

Yeah panics are usually internal errors so they wouldn’t make much sense to a user. This is helpful let me take a look

image.png

Ok we’re investigating now

This is done via the Ray Job so there shouldn't be a dependency

related: https://stackoverflow.com/questions/76658610/how-to-avoid-breaking-serialized-data-where-enum-variants-are-going-to-be-modifi

I usually just leave it as getdaft[all] in my runtime env yaml so today it got upgraded when i sent my job in

Could you do us a favor and run again with the Ray job, on a fresh Ray cluster specifying specifically

getdaft==0.3.6

across the entire job? Trying to rule out a version mismatch issue which would almost definitely cause problems that look like these

Might need to let you know again later! It's currently running a few jobs 🫠

😛 alright

Np!!! Thanks for the quick action!

Ahhhh good. Thanks @Kyle!

Yep! Haha