👋 I was testing out

flytectl

with

DeviceFlow

auth. It seems like it doesn't properly record the expiration so it requires a re-auth on every request. Has anyone else ran into this issue?

Error: failed to refresh token using cached token. Error: oauth2: token expired and refresh token is not set

This issue may also be related? https://github.com/flyteorg/flyte/issues/3288

Yeah, seems to be issue related to that PR I referenced. Is there a process to help get this more attention from the maintainers of the repository? Seems like it would be a good fix to get included in an upcoming release.

Ah yeah just realized that the PR is referring to the same issue. 🙂

@Nick Tate can you give the Issue a 👍🏽 ? we're trying to establish a lightweight mechanism for the community to signal their priorities and this is one of them. I just also gave it a label that will help continue the discussion with the maintainers

Thank you 🙇

will merge the change once tests pass

Thanks for getting this merged in 🙇 One question I had was around the release process. I see that

flytectl

is now bundled in the

flyte

monorepo but we still have the separate repository for

flytectl

as well that looks active (and possibly what the new releases are based off of).

I'm working on a change to allow us to release flytectl from the monorepo. I hope to get it out by EOW. Once that is merged I'm going to port the remaining changes from the flytectl repo and archive it to decrease the confusion.