Jason Parraga
### Describe the bug My custom Flyte plugin has a depenency that pulls in a more recent version of viper v1.11.0 -> v1.18.2 and this appears to break config loading...
# Description I was unable to use a more recent version of `grpc-io` due to this library's upper restriction on the version of protobuf. Protobuf 5 was released in March...
… builds Fixes # #### Special notes for your reviewer:
Armada scheduler is in a crash loop. There appears to be a zero'd out job run UUID getting created or deserialized somewhere. I haven't looked into the source code yet...
I'm actually just looking for Python bindings for the new job query API but if the job service is being deprecated it seems that the Armada operator should at least...
### Problem Statement This may be a broader problem but metrics don't seem to be recorded when the context passed with the request times out. It appears that this results...
## Why are the changes needed? These changes aren't strictly needed but they simplify configuration based on the changes introduced in https://github.com/flyteorg/flyte/pull/5460 ## What changes were proposed in this pull...
## Tracking issue Related to https://github.com/flyteorg/flyte/issues/5189 Related to https://github.com/flyteorg/flyte/issues/4622
## Tracking issue While working on an RFC I noticed that there is a duplicate recovery interceptor installed inside the Flyte Admin server. We ideally want to use the custom...