-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Wrong number of arguments for i18n after upgrade to Version 8.10.3 #15407
Comments
Same in 8.10.2, 8.10.1, 8.10.0 |
Same on elk 8.10.4 (on-prem). [2023-10-23T23:12:12,257][FATAL][logstash.runner ] An unexpected error occurred! {:error=>#<ArgumentError: wrong number of arguments (given 2, expected 0..1)>, :backtrace=>["/usr/s |
Anyone know if we downgrade to 8.9.X, will help fix this? |
It's a bug in the usage of hash arguments in method
where it invokes I18n.t("something", {"key" => "value"}) but it has been deprecated in Ruby 2.7 and removed in 3.0, as reported in the method comment it's a missed leftover from the original migration PR #14861 |
Logstash information:
Plugins installed: no additional ones
JVM (e.g.
java -version
): the one provided in docker container from https://www.docker.elastic.co/OS version (
uname -a
if on a Unix-like system): docker containerDescription of the problem including expected versus actual behavior:
After we upgraded from 8.8.x to 8.10.3 the connection between logstash and elasticsearch stopped working. After investigating the only error we were able to find is located in logstash logs after startup:
The warnings in the full log provide the impression of some connection issues, but if we connect to container and run for example a curl command to elasticsearch it works fine. Only error we can find is this i18n ruby issue in logstash.
I assume that this is something related to the Ruby version upgrade? Has anyone idea how to fix this at least temporarily?
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: