pin multi_json to 1.19.1 since 1.20.0 has java variant with newer concurrent-ruby pin

[jsvd]

multi_json 1.20.0 is a very big release with drop of support for 9.4, multiple changes to its adapters and the first version that publishes java and ruby platform gems separately.

The java version introduces a concurrent-ruby pin we're not yet ready to respect, leading bundler to pick the ruby version since it doesn't have C extensions, but also doesn't carry jruby specific parts like jrjackson backend and use of java concurrency primitives.

So we pin the dependency for now at ~> 1.19.x.

Not pinning causes the ruby version to be installed, and then the orphan cleanup task removes the dependency by mistake, leading to failures in tests and potentially in runtime too.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

[mergify]

This pull request does not have a backport label. Could you fix it @jsvd? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• If no backport is necessary, please add the backport-skip label

[jsvd]

run exhaustive tests

[kaisecheng]

qa/integration/Gemfile also need to pin gem "multi_json", "~> 1.19.1" ? Unit test is passed but IT still fail

[jsvd]

run exhaustive tests

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 30ea229

Failed CI Steps

• 🥼 x-pack integration
• 🥼 x-pack integration

History

• 💔 Build #4646 failed 9c76d9b

[jsvd]

@Mergifyio backport 9.4

[mergify]

backport 9.4

✅ Backports have been created

Details

• #18979 [9.4] (backport #18977) pin multi_json to 1.19.1 since 1.20.0 has java variant with newer concurrent-ruby pin has been created for branch 9.4

Git reported the following error:

To https://github.com/elastic/logstash
 ! [rejected]            mergify/bp/9.4/pr-18977 -> mergify/bp/9.4/pr-18977 (non-fast-forward)
error: failed to push some refs to 'https://github.com/elastic/logstash'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.