-
Notifications
You must be signed in to change notification settings - Fork 532
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
1.0.0-rc3 Error "None of the given media types are supported" #1398
Comments
I think this is connected to #1341 and should be supported if we merge this and cut another RC. |
I wanted to publish a new release for kubernetes-client#1398 but it seems like the workflow is only available on the master branch thus it means it can not get executed in the release-1.x branch. Porting over the file and use latest node LTS in the setup-node action.
I wanted to publish a new release for kubernetes-client#1398 but it seems like the workflow is only available on the master branch thus it means it can not get executed in the release-1.x branch. Porting over the file and use latest node LTS in the setup-node action.
I wanted to publish a new release for kubernetes-client#1398 but it seems like the workflow is only available on the master branch thus it means it can not get executed in the release-1.x branch. Porting over the file and use latest node LTS in the setup-node action.
I wanted to cut another RC to potentially close * #1420 * #1398 * #1397 but the release is erroring at the test because of the memory limit so I decided to use c8 instead of nyc because when trying to remove nyc I concluded that the memory error comes from it and its last release was 4 years ago. It works as a drop-in replacement. https://www.npmjs.com/package/c8
@tugtugtug I've published a new release |
Verified fixed! |
Hi @mstruebing,
the passed One workaround found, that should be future compatible.
Let me know if you prefer a new issue tho. |
made a new issue #1499 |
Describe the bug
When any patch functions are called, such as patchNamespacedStatefulSet, the client throws "None of the given media types are supported"
** Client Version **
e.g.
1.0.0-rc3
** Server Version **
e.g.
1.25.1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The patch functions should work. And in addition to be working, I'm also not sure how the API will figure out which mediaType to prefer given the content of the body. The old api allows overriding the headers via the options, now this is no longer available.
** Example Code**
Environment (please complete the following information):
OS: [Ubuntu 22.04]
NodeJS Version [18]
Cloud runtime [NA]
Additional context
Is there a general status the testing coverage of the 1.0.0 branch?
Given the release candidate tag, I had higher expectation of the quality of the code, but it seems quite hard to move forward with all these bugs.
The text was updated successfully, but these errors were encountered: