<@U027UBSSBRC> <@U01NGJ0GA0J> Unfortunate timing o...
# dev-metaflow
e
@bulky-afternoon-92433 @User Unfortunate timing on this given the recent release, but I found a bug that was introduced in this PR: https://github.com/Netflix/metaflow/pull/1442 TLDR the new annotation logic isn't populating the project, flow_name, or user annotations in kubernetes https://github.com/Netflix/metaflow/issues/1515 Ran out of time today to figure out where in the logic is failing but wanted to let you know
1
a
We will roll back the change
b
rolled back and added a mention to the prior release notes. My guess is that the issue is in relying on
current
inside the kubernetes_decorator scope for populating the system annotations, given that apparently labels were still working, only annotations were not?
motivation for the changes were that we could use the kubernetes decorator as a source for setting the labels/annotations. Apparently during the init phase,
current
is not sufficiently populated though.. One option to consider is if we could populate the necessary properties for the current singleton, f.ex. during the
*_cli.py
entrypoints, but this needs some thought if there are any side-effects to setting project/user info too early.
@elegant-beach-10818 would you have time to look at a fix for this and possibly reintroducing the PR? I might also have some time this week to look into the issue with
current
, but for now the approach would be to see if the problematic system annotations can be inferred in another way inside the kubernetes decorator, and if not, we need to lift those out of the decorator back where they used to be.
e
This week is somewhat tight timewise for me. The earliest I can look at it will likely be next week
b
been extremely busy with other tasks as of late but managed to squeeze out a first-draft for reintroducing this feature. @elegant-beach-10818 if you got any time to spare, feel free to take it for a spin: https://github.com/Netflix/metaflow/pull/1568
also was unable to add you as a reviewer for some reason, but feel free to drop any notes in the PR 🙂
e
I feel you on the busy side of things I’ll definitely take a look. Thanks for working on it!