-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1601550 - Enforce disk quota on pending pings directory #1110
Bug 1601550 - Enforce disk quota on pending pings directory #1110
Conversation
I redirected this to @badboy as I won't be able to get to it today and won't be around tomorrow. |
f7d1dab
to
240257b
Compare
74cdd92
to
5e55a0b
Compare
980b308
to
50482c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still some open questions and some suggestions.
This is on a good way though.
This definitely needs some documentation, e.g. user-facing here: https://mozilla.github.io/glean/book/user/pings/index.html?highlight=rate#limitations
636c82a
to
f57b4e1
Compare
7a12c62
to
1c90936
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now, I think we can (nearly) land this.
Some inline questions, but nothing totally blocking.
Good work!
glean-core/android/src/test/java/mozilla/telemetry/glean/pings/DeletionPingTest.kt
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That doesn't look much more complicated.
It's unfortunate that we do the double-reverse, but assuming we're never should have thousands of those I also don't want to over-optimize this just yet.
The test was not checking if pings were actually loadedfrom disk
Co-authored-by: Jan-Erik Rediger <badboy@archlinux.us>
The problem was that the test was trying to get a request sent by a worker, but that worker received a PingUploadTask::Wait before getting a PingUploadTask::Upload and the test was trying to check the request before it had actually arrived. This is potentially an issue with more tests, but it only manifested in this test for now. I opened Bug 1657589 for more in depth investigation on this.
Co-authored-by: Jan-Erik Rediger <badboy@archlinux.us>
26f2a1f
to
0979629
Compare
I am opening this as a draft because I would like to get some opinions on the approach.
Please refer to comments I'll leave in the code to see what I mean.