-
Notifications
You must be signed in to change notification settings - Fork 162
🐛 [RUM-11848] Block Logs initialization on Node environments #3904
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
Conversation
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: 5c41345 | Docs | Was this helpful? Give us feedback! |
813d6f8
to
a1d3b6d
Compare
Bundles Sizes Evolution
🚀 CPU Performance
🧠 Memory Performance
|
test/apps/vanilla/app.ts
Outdated
@@ -1,3 +1,5 @@ | |||
/* eslint-disable */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 27 is reporting @typescript-eslint/no-unsafe-call
even when I disable the line 😕
9fb2483
to
3cce81d
Compare
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
Build pipeline has failing jobs for beac9bf: What to do next?
DetailsSince those jobs are not marked as being allowed to fail, the pipeline will most likely fail. |
7885467
to
5c41345
Compare
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
Motivation
The latest changes in Logs enable the SDK to function in Node environments. This side effect was unintended.
Changes
The PR introduces a condition that blocks SDK initialization in Node environments.
Test instructions
Compatibility test passed.
Checklist