Refs #34089 - Work around Kafo type parsing bug #1013
Merged
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
evgeni
approved these changes
Jan 4, 2022
ehelms
approved these changes
Jan 4, 2022
Due to a bug in Kafo[1], the Stdlib::IP::Address data type can't be used. This broke the nightly build[2]. By reducing the type to simple String[1] and asserting in the body the same guarantee is given, but with a worse UX if it does fail. [1]: https://projects.theforeman.org/issues/21398 [2]: https://community.theforeman.org/t/foreman-installer-develop-package-release-1015-failed/26627/3
ekohl
force-pushed
the
34089-workaround-kafo
branch
from
44a73e1 to
2f60b88
Compare
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.
Due to a bug in Kafo, the Stdlib::IP::Address data type can't be used. This broke the nightly build.
By reducing the type to simple
String[1]and asserting in the body the same guarantee is given, but with a worse UX if it does fail.Currently our pipelines are broken due to Psych 4 being pulled in by rdoc 6.4 which is incompatible with Puppet.