-
Notifications
You must be signed in to change notification settings - Fork 297
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
Support for YamlDotNet 16.0.0 #1573
Comments
let me take a look |
Based on the error message, one possible solution is to provide both forms of implementations of |
I recently upgraded one of my projects to YamlDotNet 16, its quite easy, IvanJosipovic/YamlDotNet.System.Text.Json@fa5963f I can do a PR for this if needed. Additionally, I don't see much value in making these converters backward compatible. |
thanks @IvanJosipovic, please. i was too busy recently |
Thanks to everyone. @tg123 Is it possible to trigger a release. Also https://github.com/buehler/dotnet-operator-sdk is broken if v16 of YamlDotNet is used. See also buehler/dotnet-operator-sdk#797 |
Any news regarding the release? I'm facing the issue, too. |
will kick a release for 1.31 soon |
Thank you! |
This was fixed in https://www.nuget.org/packages/KubernetesClient/14.0.9 |
@IvanJosipovic apparently not, it's the version I'm using and it throws NotImplementedExceptions at startup |
Check the references in nuget.org, you may have another dependency forcing the downgrade. |
@IvanJosipovic AFAIK I do not. All packages are up to latest version. If you want, you can easily repro the issue by starting Synapse's API server on the following branch: https://github.com/serverlessworkflow/synapse/tree/feat-k8s-container-platform/src/api/Synapse.Api.Server Removing the KubernetesClient package (and all related classes) from the solution "fixes" the issue. |
Just launched your branch, the error is:
Looks like you have your own converter |
@IvanJosipovic Sorry about that, in my dev setup I had manually updated the dependencies of the incriminated package. I'll properly update it, publish it and test it. I'll keep you posted! In the meanwhile, thanks for both your patience and attention 🙏 |
@IvanJosipovic I updated all packages and everything is working as expected!!! Many thanks ❤️ |
Describe the bug
Hi guys, I was wondering if there were plans to support YamlDotNet v 16.0.0? It looks like they have made some breaking changes in the latest release: https://github.com/aaubry/YamlDotNet/releases/tag/v16.0.0 specifically to ReadYaml and WriteYaml in IYamlTypeConverter.cs leaving any descendant in the KubernetesClient library broken (i.e., IntOrStringYamlConverter).
Let me know if you need any more information.
Dotnet Runtime Version
net8
To Reproduce
Expected behavior
Connection to succeed
Where do you run your app with Kubernetes SDK (please complete the following information):
The text was updated successfully, but these errors were encountered: