-
Notifications
You must be signed in to change notification settings - Fork 180
RUST-1509 SDAM Logging #918
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
98a112e
to
eede144
Compare
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.
Mostly LGTM! Just a few minor comments.
@@ -71,6 +71,12 @@ pub(crate) fn deserialize_spec_tests<T: DeserializeOwned>( | |||
continue; | |||
}; | |||
|
|||
if let Ok(unskipped_filename) = std::env::var("TEST_FILE") { |
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.
Was this intentionally left in?
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 add this when I'm debugging pretty often to make it easier to run single tests, but I can delete if you'd rather not have it checked in
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.
Nah, it seems fine to leave in as long as it's deliberate :)
src/sdam/topology.rs
Outdated
let tracing_emitter = | ||
TopologyTracingEventEmitter::new(options.tracing_max_document_length_bytes, id); | ||
let (tx, mut rx) = mpsc::unbounded_channel::<AcknowledgedMessage<SdamEvent>>(); | ||
// Spin up a task to handle events so that a user's event handling code can't block |
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.
This isn't from your changes, but I don't think this comment is accurate - if the user's event handler blocks, that'll block whatever thread this task happens to be scheduled on, which could include the worker.
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.
good catch, I'll just remove this comment.
No description provided.