-
-
Notifications
You must be signed in to change notification settings - Fork 166
fix: Improve transport synchronization and consume response #260
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
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.
Err(err) => { sentry_debug!("Failed to read sentry response: {}", err); }, | ||
Ok(text) => { sentry_debug!("Get response: `{}`", text); }, |
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.
Err(err) => { sentry_debug!("Failed to read sentry response: {}", err); }, | |
Ok(text) => { sentry_debug!("Get response: `{}`", text); }, | |
Err(err) => sentry_debug!("Failed to read sentry response: {}", err), | |
Ok(text) => sentry_debug!("Get response: `{}`", text), |
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'm wondering how this does not fail rustfmt.
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.
its inside the macro, so none of that stuff is rustfmt-ed, also, I needed to wrap this in a block because of the way the sentry_debug
macro is built :-(
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 see, thanks. At least the comment after the }
should go usually.
The synchronization fixes have been proposed in #172 originally