[Job Launcher] feat: use shared logger - #3456
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 5 Skipped Deployments
|
dnechay
commented
Jul 10, 2025
dnechay
force-pushed
the
dnechay/jl-structured-log
branch
from
July 10, 2025 22:28
31ad4d4 to
15b8ade
Compare
flopez7
reviewed
Jul 11, 2025
flopez7
approved these changes
Jul 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue tracking
Follow up to #3387. Closes #3388
Context behind the change
Applied shared logger in order to use structured logging.
Changed scripts in root
package.jsonto rely on yarn workspace features in order:packages/libsyarn build:libscommand failure due to absence ofloggerworkspace in some docker imagesHow has this been tested?
Release plan
NODE_ENVon render for JL to correspond to actual environment (i.e.stagingorproduction, right now it'sdevelopmenton staging)Potential risks; What to monitor; Rollback plan
Should be none