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.
Explanation
Fix #3949
This increases the event log to 50k total events (from 5k). This results in a 10x change in total event storage, but for an estimated 3.33MB total space now being needed this seems reasonable long-term. We specifically want this for the upcoming alpha MR4 study to ensure that events can be collected for potentially weeks without internet syncing, but that also matches longer-term goals of the app.
Note that no testing changes occur since this is just a configuration knob, and we don't currently have any module tests. They could be trivially added in the future, but this is simple enough to inspect directly so a test doesn't seem urgently needed for this PR.
Essential Checklist
For UI-specific PRs only
N/A -- configuration-only change with no UI implications*.
* Technically, this may result in 50k event logs being viewable from the developer menu, but this realistically will never happen. If, in the event it does, the recycler view that's being used for event logs should be suitable to handle the load.