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

[3.11] bpo-46755: Don't log stack info twice in QueueHandler (GH-31355) (GH-94564) #94564

Merged
merged 1 commit into from
Jul 5, 2022

Conversation

miss-islington
Copy link
Contributor

(cherry picked from commit c60f125)

Co-authored-by: Erik Montnemery erik@montnemery.com

(cherry picked from commit c60f125)

Co-authored-by: Erik Montnemery <erik@montnemery.com>
@miss-islington miss-islington requested a review from vsajip as a code owner July 5, 2022 14:24
@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@vsajip vsajip self-assigned this Jul 5, 2022
@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@vsajip vsajip changed the title [3.11] bpo-46755: Don't log stack info twice in QueueHandler (GH-31355) [3.11] bpo-46755: Don't log stack info twice in QueueHandler (GH-31355) (GH-94564) Jul 5, 2022
@vsajip vsajip merged commit d49159b into python:3.11 Jul 5, 2022
@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@miss-islington miss-islington deleted the backport-c60f125-3.11 branch July 5, 2022 14:49
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.

4 participants