Limit event fetches to prevent stack size from growing too large

[devonh]

Pull Request Checklist

• Pull request is based on the develop branch
• Pull request includes a changelog file. The entry should:
  • Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
  • Use markdown where necessary, mostly for code blocks.
  • End with either a period (.) or an exclamation mark (!).
  • Start with a capital letter.
  • Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
• Code style is correct
  (run the linters)

[devonh]

We might want to lower the upper range even further.
The stack size depends on the path and can easily have some variation in it between systems/python versions.

With the full list of events (~20) the full stack message of the exception on my laptop was 73839 bytes whereas the maximum allowed size is 65535 bytes.
Fetching only 10 should reduce the size to around 36k bytes which is much below the max. But this will differ by environment.

[erikjohnston]

Ok: so I guess the change is that in Python 3.12 and latest Twisted something has changed with the stack traces for twisted failures? I tried with older py3.12 and twisted and couldn't reproduce even if I increased the number of events we sent. I think Twisted does try and do stuff to correctly keep track of stack traces, so could believe that something has gone wibbly there. What does confuse me though is that the stack traces you shared didn't seem to be one long stack trace but multiple copies of the same thing.