Fix large imap_content event warning by truncating the email text body to 2 KiB #92066
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.
Breaking change
The use of
imap_content
event could break for users that want to parse data from larger email messages from the part that is truncated. Only the first 2048 bytes of the message body (2 KiB) will be available.Proposed change
Limits the size of the email text body that will be available in the event data or an
imap_content
event.We should avoid large text bodies to be passed as event. The size of body
text
will be truncated to 2 KiB.Large messages will lead to event data becoming to large, causing events not to be processed and warnings in the log about the size. A PR to update the documentation is added.
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: