-
Notifications
You must be signed in to change notification settings - Fork 825
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
fix: enable async hooks manager in node tracer close #226 #232
Conversation
Codecov Report
@@ Coverage Diff @@
## master #232 +/- ##
==========================================
- Coverage 98.79% 98.74% -0.05%
==========================================
Files 55 55
Lines 2161 2155 -6
Branches 151 150 -1
==========================================
- Hits 2135 2128 -7
- Misses 26 27 +1
|
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.
LGTM
Yeah I got the same weird situation with the http-plugin, it's when you put test files in deeper folders... So if you put NodeTracer.test.ts inside instrumentation folder, it will run. It should also work if you put NodeTracer.test.ts inside a folder (not instrumentation only) |
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.
Fix NodeTracer.test.ts file. #233
Yes, right. One option is to remove folder hierarchy in tests and other is to allow multiple paths in test script ex: |
This is what I found: mochajs/mocha#3115 and looks to be working in our scenario. Will open PR to fix it. |
51b6936
to
e4b4fe9
Compare
@vmarchaud if you rebase (#233) you should see NodeTracer tests |
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.
LGTM
@vmarchaud Could you please fix the build? |
@mayurkale22 should be good now |
059ad39
to
5f83328
Compare
/** | ||
* NodeTracerConfig provides an interface for configuring a Node Tracer. | ||
*/ | ||
export interface NodeTracerConfig { |
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.
NodeTracerConfig
same as BasicTracerConfig
except one mandatory attribute. What's the motivation here? I proposed to keep ScopeManager
optional attribute in #194. If we do that then we don't need to create NodeTracerConfig
interface.
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.
The problem is i cant extend the BasicTracerConfig
to tell scopeManager
is optional so i'm forced to make a new interface.
I agree that it should be optional and the BasicTracer
should create a NoopScopeManager if none is used, if we agree we should open another PR
cc @OlivierAlbertini