-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing malformed data to apimachinery causes panic #737
Comments
In the near term we certainly shouldn't panic. I'll fix that. @lukehoban @pgavlin what are your thoughts on supporting this longer term? Worth doing? And if so, how do you envision this working? |
What did you do to hit this? |
@lukehoban sorry—you pass any Also—why did we remove the P1? It seems like we should commit to fixing this ASAP. |
Alright, after careful thought, I think the only time we would encounter an error like this is when we pass an To recap:
Hence, merging this PR should ameliorate of of this issue in the short term. Questions/thoughts:
cc @lukehoban @pgavlin @lblackstone for visibility. We're going to merge the PR that we think addresses this issue tonight, but I will keep this open for another day or two just so it has time to get visibility, percolate, etc. |
Talking a bit to @ellismg I believe the above is correct modulo the secrets—which he is handling. |
Let's close this out if there's no known work remaining here. If we find new issues, we can open new issues to track. |
This is relatively unlikely for TS users (because types), but could in theory accidentally be done by Python and TS users. The panic looks like:
The text was updated successfully, but these errors were encountered: