Try bumping recursive-open-struct #640
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
recursive-open-struct recently had a 2.0 release which included an ABI breaking change. I'm not sure if the change affects kubeclient or not. If not, it would be nice to be able to use the newer release.
smoser
added a commit
to smoser/wolfi-os
that referenced
this pull request
Oct 25, 2024
ruby3.2-kubeclient is currently not passing a test. That means it can't get any new version should one be created. I hit this when trying to create ruby 3.3 versions of it. If this does not work, then we will need to create a ruby3.2-recursive-open-struct-1.3 package and depend on it. I proposed upstream ManageIQ/kubeclient#640. Fixes: wolfi-dev#31938
smoser
added a commit
to smoser/wolfi-os
that referenced
this pull request
Oct 25, 2024
ruby3.2-kubeclient is currently not passing a test. That means it can't get any new version should one be created. I hit this when trying to create ruby 3.3 versions of it. If this does not work, then we will need to create a ruby3.2-recursive-open-struct-1.3 package and depend on it. I proposed upstream ManageIQ/kubeclient#640. Fixes: wolfi-dev#31938
smoser
added a commit
to smoser/wolfi-os
that referenced
this pull request
Oct 25, 2024
ruby3.2-kubeclient is currently not passing a test. That means it can't get any new version should one be created. I hit this when trying to create ruby 3.3 versions of it. If this does not work, then we will need to create a ruby3.2-recursive-open-struct-1.3 package and depend on it. I proposed upstream ManageIQ/kubeclient#640. Fixes: wolfi-dev#31938
|
@smoser I see workflows awaiting to run. Maybe you can turn on actions in your fork, modify workflow file and manually trigger them there? Not sure if any of them are possible to run in forks without secrets. |
We'll see how it does: https://github.com/smoser/kubeclient/actions/runs/11525469999 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
recursive-open-struct recently had a 2.0 release which included an ABI breaking change. I'm not sure if the change affects kubeclient or not. If not, it would be nice to be able to use the newer release.
I have only tried import test, I was hoping that c-i would give a better sniff.
wolfi-dev/os#31938