Drop multi_json support#293
Merged
bastelfreak merged 1 commit intoOpenVoxProject:mainfrom Jan 5, 2026
Merged
Conversation
These days the built in JSON is fast enough and supporting other implementations can only complicate matters. We can also rely on JRuby to have a correct implementation since the same json gem is also built for Java and included in JRuby.
bastelfreak
reviewed
Dec 28, 2025
| end | ||
|
|
||
| begin | ||
| require 'multi_json' |
Contributor
There was a problem hiding this comment.
mental note: we probably can/have to adjust puppet-runtime or openvox-server to not include multi_json in the packages
bastelfreak
approved these changes
Dec 28, 2025
jay7x
approved these changes
Dec 29, 2025
Member
|
Haha, I just found this PR while trying to find what cause a regression when updating OpenVox on FreeBSD (I had some time today to dig in the issue). It happens that with these packages: root@puppet:~ # pkg info | grep openv
openvox-agent8-8.24.2 Configuration management framework written in Ruby
openvox-server8-8.12.0 Puppet Server running in the JVM
openvoxdb-terminus8-8.11.0 PuppetDB storeconfigs backend terminus module
rubygem-openvoxserver-ca-3.0.0 Ruby CLI tool to interact with the OpenVox Server Certificate AuthorityApplying a catalog fails with a bunch of errors: The root caused is not directly visible (exception catched by Puppet), but digging the rabbit hole we land here in After applying the patch, the issue vanished 😁 root@puppet:~ # puppet agent -t
Info: Refreshing CA certificate
Info: CA certificate is unmodified, using existing CA certificate
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Notice: Requesting catalog from puppet:8140 (10.0.0.10)
Notice: Catalog compiled by puppet
Info: Caching catalog for puppet.lan
Info: Applying configuration version 'production-a9c260d'
Notice: Applied catalog in 5.04 secondsThank you for fixing issues before I find them 😍 |
Contributor
Author
|
I saw those exact same failures in CI, which prompted me to drop it. Glad it helps you too |
This file contains hidden or 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
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.
These days the built in JSON is fast enough and supporting other implementations can only complicate matters. We can also rely on JRuby to have a correct implementation since the same json gem is also built for Java and included in JRuby.
Note I made an assumption about JRuby because https://rubygems.org/gems/json also lists a Java build.
I was triggered to drop this because tests started to fail for me.