Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

image.png

Hey, can anybody help with this error during registration?

What steps did you take to get this, registering twice in a row? What flytekit version are you using and are you using maptasks?

You might have luck inquiring about this error on this issue: <https://github.com/flyteorg/flyte/issues/4762> :slightly_smiling_face:

Yes, im using maptasks and not double registering. updated from 1.11 to 1.12 and it worked:slightly_smiling_face:  thanks!

We're also seeing this error, and we are on flytekit 1.12, with a very basic workflow + custom python task.

From what I understand, it's potentially easy to have this kind of version string conflict – the version string generation in flytekit takes in the md5_bytes, serialization settings, etc. – but should it also take in the task config (esp. for custom tasks)?

Did anything change recently around the version string generation in flytekit?

<@U06FVMEJR6X> put up a PR to address this at <https://github.com/flyteorg/flytekit/pull/2417> -- any feedback from maintainers on this approach? (cross-posting to <#C04NJPLRWUX|>)