Fallback to Logger parameters incorrect

[lloydpick]

The logger fallback implementation seems to fail when using a non STDOUT or STDERR location in cold boot outside of the handler. I believe this is because the orig_initialize misses that the first 3 parameters are normal, but the remaining are named.

aws-lambda-ruby-runtime-interface-client/lib/aws_lambda_ric.rb

Lines 158 to 159 in e4939c2

	orig_initialize(logdev, shift_age, shift_size, level, progname,
	formatter, datetime_format, binmode, shift_period_suffix)

https://github.com/ruby/logger/blob/afe0da71087d721de7107f6bee7631b8b71a2471/lib/logger.rb#L380-L382

You end up with an error like the one described in this issue - airbrake/airbrake-ruby#630

Raising this here, as I know this occurs within the Lambda environment on Ruby 2.7.

[edhzsz]

Hi Lloyd, thank you so much for reporting this issue.

[lloydpick]

As I've just seen that there's a PR for this now 👍, once that is merged is there a rough timeframe to when the Lambda service itself will receive this fix? Obviously this repo will have it, and that can be used locally, or if I build an image and use that, but the straight lambda service. Would it be weeks, months?

[edhzsz]

Yes, the PR is still missing an approval, but I expect it to get it soon and release a new version of this library.
The update to the Lambda managed runtime will follow the normal deployment cadence of the Lambda Runtimes. I cannot give you an ETA for that, but I believe it is safe to measure it in weeks.