-
-
Notifications
You must be signed in to change notification settings - Fork 125
feat: add request layer lifecycle TracingChannels #196
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
Open
logaretm
wants to merge
24
commits into
pillarjs:master
Choose a base branch
from
logaretm:tracing-channel
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,169
−25
Open
Changes from 22 commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
95e23ba
feat: add TracingChannel support for express:request
logaretm 858399c
refactor: reduce duplication in invokeWithTrace
logaretm 9f1aea7
fix: guard against missing dc.tracingChannel on older Node versions
logaretm dea81ae
ref: use node: prefix
logaretm 1f6bc25
fix: use the top-level hasSubscribers flag
logaretm 1ad1b9c
test: pin down error event semantics for next(err) flows
logaretm 28b3213
fix: always publish error events before calling next
logaretm 90ed7e2
fix: refine error handling for control-flow sentinels in invokeWithTrace
logaretm 758030e
test: added case for router control flow error
logaretm 9c9b4a7
test: assert handled flag on error events in both-layers error tests
logaretm 67c3851
refactor: rename tracing channel to pillarjs.router.request
logaretm 6aa0575
docs: document pillarjs.router.request tracing channel
logaretm 5e80078
refactor: rename tracing channel to express.router.request
logaretm da0da14
fix: detect tracing subscribers on Node versions without TracingChann…
logaretm 8fd857f
refactor: gate tracing on subscribers in callers and pass ctx directly
logaretm 337e212
fix: report each request error once, at its origin layer
logaretm 232143b
fix: don't report thrown 'route'/'router' signals as errors
logaretm 10a47bc
docs: clarify error semantics on the request tracing channel
logaretm cc5deb7
fix: report value-less rejections as the forwarded error on the channel
logaretm 9aa666a
test: extract channel-name constant and shared byLayer helper
logaretm 04b2f72
fix: route traced outcomes through next so tracing never changes routing
logaretm 97da6d8
test: hoist repeated setup and predicates into shared helpers
logaretm 583c8c4
refactor: rename the error-handler context flag to errorHandler
logaretm d0d8f7e
perf: publish lifecycle via start.runStores instead of tracePromise
logaretm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
I think we should rename it to something like
errorHandler, maybe?Uh oh!
There was an error while loading. Please reload this page.
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.
That's fair, the clearer the better I suppose. Maybe
isErrorHandlerorerrorHandleractually? since it doesn't mean that the error is handled, just that the handler is an error handler.