Skip to content

Don't Ignore Custom Formatters + Version Bump to 3.1.2 #49

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

Merged
merged 8 commits into from
Jun 6, 2025

Conversation

M-Elsaeed
Copy link
Contributor

@M-Elsaeed M-Elsaeed commented Jun 5, 2025

Description of changes:

We have 2 PRs modifying the logging behavior
#32
#47

Following the first PR, in case the logdevice was stdout or stderr, lambda's custom formatter which we used to assign to @default_formatter was ignored since we were calling the constructor which restored the @default_formatter to ruby's built in default formatter; HOWEVER, if you passed in a formatter, that will be used.

Following the second PR, in case the logdevice was stdout or stderr, the formatter is always set to be lambda's custom formatter.

This PR allows custom formatters.

Target (OCI, Managed Runtime, both): Both

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@M-Elsaeed M-Elsaeed changed the title Don't Ignore Custom Formatters. + Version Bump Don't Ignore Custom Formatters + Version Bump to 3.1.2 Jun 5, 2025
@M-Elsaeed M-Elsaeed merged commit c5cf4de into main Jun 6, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants