Skip to content

Conversation

@nevans
Copy link
Collaborator

@nevans nevans commented Apr 21, 2025

Backports #444 to v0.3-stable

nevans added 3 commits April 20, 2025 20:50
_Please note:_ this only limits the size per response.  It does _not_
limit how many unhandled responses may be stored on the responses hash.
Note that this cherry-picked commit is missing key paits that are
incompatible with net-imap before 0.4.  I'm keeping the conflict
resolution here, and the updates for net-imap 0.3 in the next commit.

------

Though it would be useful to also have limits based on response type and
what commands are currently running, that's out of scope for now.

_Please note:_ this only limits the size per response.  It does _not_
limit how many unhandled responses may be stored on the responses hash.
@nevans nevans added enhancement New feature or request backport This issue or PR is for a stable release branch labels Apr 21, 2025
For the net-imap v0.3 backport, two major changes were needed:
* the tests needed to be almost completely rewritten because FakeServer
  was added for v0.4.
* `max_response_size` needed to be on Net::IMAP directly, because Config
  was added for v0.4.
@nevans nevans force-pushed the backport/v0.3-max_response_size branch from fce830d to e005925 Compare April 21, 2025 10:53
@nevans nevans merged commit 2aadab9 into v0.3-stable Apr 21, 2025
34 checks passed
@nevans nevans deleted the backport/v0.3-max_response_size branch April 21, 2025 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This issue or PR is for a stable release branch enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants