Ruby 3.3.3 default logger 1.6.0 is failing on lambda

[choosen]

I've added a solution PR, but maybe issue is needed to be picked up by reviewers?

#32

Problem is made by changes in logger and lambda ruby is changing logger initializer too much
(there is some logic in logger.rb in initializer, which is not best practice maybe :P and it is not backward compatible for initializer function overwrites :D)

[cgaube]

This is also happening on Ruby 3.2

[kminevskiy]

We hit the same issue. As mentioned above, it is present for both 3.2 and 3.3 runtimes.

[choosen]

workaround is to downgrade explicitly the logger gem to ~> 1.5.0 🤔

UPDATE or to logger 1.6.1

[HistoireDeBabar]

The most recent version of logger (v1.6.1) has resolved this for us where they now guarantee level_override exists

[mullermp]

Is a fix for this still necessary or desired with the latest logger change?

[choosen]

@mullermp
It not so much needed as 1.6.1 logger is compatible again.

But I think my solution is more safe for the future as it calls super in all code branches in overwritten patch.

You can also close it if you would like

[mullermp]

It makes sense to call super as you've done. I'll look this week.

[maxday]

Closing this at #32 has been merged