Skip to content
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

Use updated logging macro. #4

Merged
merged 1 commit into from
Oct 30, 2024

Conversation

vorporeal
Copy link
Collaborator

Some time between 8.15 and 8.36, Sentry changed their logging macros, so we need to update our debug log line added in our subprocess patch.

@vorporeal vorporeal requested a review from alokedesai October 29, 2024 22:06
Copy link

Fails
🚫 Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Use updated logging macro ([#4](https://github.com/warpdotdev/sentry-cocoa/pull/4))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against 25595d4

@@ -321,10 +321,12 @@ handleExceptions(void *const userData)
break;
}

SentryCrashLOG_DEBUG("Received exception from subprocess. Ignoring message and waiting for another.");
SENTRY_ASYNC_SAFE_LOG_DEBUG(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming this is the only actual change?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I don't know how that other commit got in here. Lemme see if I can clean that up real quick.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh interesting looks like Sentry has a bot that automatically adds a commit to PRs that fixes formatting issues? I'm going to revert that commit and force-push and then merge; don't want to potentially have problems with merge conflicts in the future.

@vorporeal vorporeal force-pushed the david/fix-logging-macro branch from 3f9e323 to 25595d4 Compare October 30, 2024 17:44
@vorporeal vorporeal merged commit 56fd585 into 8.36.0-with-subprocess-fix Oct 30, 2024
90 of 100 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants