I just tried upgrading to

flyteadmin:1.0.1

for the stow fix https://github.com/flyteorg/flyteadmin/pull/416 but now flyteconsole fails with a 500. "Request failed with status code 500 header key "userinfo" contains value with non-printable ASCII characters"

cc @Prafulla Mahindrakar

I have GCP deployment where i didn’t see this issue. May be its affecting only auth enabled admins. Let me try to enable auth on my setup and check too

@Prafulla Mahindrakar as soon as I load console when logged in. Does

userinfo

contain the full name perhaps coming from auth? Then it could be triggered because of the non-ascii ö in my name.

User info would be shared by openid connect provider . I was able to login using my name but yeah could be due to non ascii char in yours

yes

Ok . Let me check more

Yeah I think that's the issue indeed. I changed my name in Google Accounts removing the umlaut to test and now it works.

Awesome .

yes it's working with 1.0.0

Ok its due to update to GRPC which now doesn’t allow non-ascii chars in headers . Heres the issue https://github.com/grpc/grpc-go/issues/468 Which got fixed in this PR https://github.com/grpc/grpc-go/pull/4886 With the latest flyteadmin its pulling in the fix for this aswell and hence you are encountering this issue only with the latest admin version

Do you know where this is actually put into the header?

Thanks @Prafulla Mahindrakar!