Arun Babu Neelicattu

More a heads up that anything - SemVer in practice is not necessarily always compatible with PEP440.

@tomchristie - hoping that the implementation in a7f8518 is aligned to what you had in mind for the TODO. The other two commits are not related to that change but...

@tomchristie no worries; I will get it rebased soon-ish.

Adding some context since @malcolmgreaves mentioned the poetry thread. For tools like poetry, because we do dependency resolution ahead of time, we rely on metadata first (when available). This means...

@appilon @radeksimko I've rebased the change, would be great to get this one merged.

Rebased. Not sure if it helps anyone though. :smile:

@apparentlymart I have attempted a resolution in #10, happy to take any feedback.

@kmoe To be honest, my memory of the original use case is a bit shoddy. But, as the description says, the particular case that lead to this was since we...

Looks like this is a race condition issue. Having the label [`nvidia.com/mig.config`](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/gpu-operator-mig.html#configuring-mig-profiles) set on the node in question should trigger the `mig-manager` allowing the device plugin to succeed.

@M-J-Murray can you try this with the current pre-release or `master`? Attempted to reproduce this with `master` and was unable.