[17.0][IMP] attachment_azure: add stack_info on ResourceExistsError #524
Merged
Conversation
vvrossem
changed the title
vvrossem
changed the title
gurneyalex
approved these changes
Apr 14, 2026
The blob already exists, so the exception traceback (inside upload_blob) is not useful on its own. Adding stack_info=True to _logger.exception() also logs the call stack, revealing who triggered the duplicate write.
vvrossem
force-pushed
the
azure_attachment-traceback
branch
from
552d575 to
d0fcf01
Compare
vvrossem
changed the title
jcoux
approved these changes
Apr 17, 2026
Author
|
Hello @vrenaville, @florentx, could you please merge this PR ? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The blob already exists, so the exception traceback (inside upload_blob)
is not useful on its own. Adding stack_info=True to _logger.exception()
also logs the call stack, revealing who triggered the duplicate write.