Yannis Zarkadas
Yannis Zarkadas
@alaypatel07 Ahh makes much more sense now! That's great, please do share your findings! :smile: Did you encounter any major roadblocks?
Hi @chlunde and sorry for the late reply! I don't have any merging capabilities unfortunately. The current approvers are @varshaprasad96 @koba1t @knverey
@dragoscalinescu the obvious workaround is to send a 40x error, which should go through, and include extra information in the response body. Otherwise, I think getting involved in the PRs...
@mortent I also encountered this issue when trying to vendor a third-party Helm chart. In my case, I actually want to vendor the Helm chart, not ignore it, in order...
@andreyvelich this sounds like a good solution. Another way would be to pre-download the dataset in the image. The problem is how to make a new image for the example....
/reopen /lifecycle frozen Hi @reem! The contributor UI is not a very well-maintained component. Its backend (KFAM) is following a road to deprecation. So I have 2 suggestions: First, did...
@ericchiang thanks for taking the time such a detailed reply. My thought was that the library could specifically enrich request-related errors with extra information, which would enable library users to...
Pinging maintainer: @rithujohn191 @JoelSpeed @srenatus @bonifaido @sagikazarmark Would you be open to a PR adding this functionality? I see this implementation as having 2 stages: 1. Add the `id_token_hint` support...