-
Notifications
You must be signed in to change notification settings - Fork 107
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
Fix github commented
filter and wrong until
#363
base: main
Are you sure you want to change the base?
Conversation
Here's the difference for running --- /tmp/did-0.21.md 2024-03-26 23:20:08.714955329 +0100
+++ /tmp/did-felixoid.md 2024-03-26 23:19:54.871448943 +0100
@@ -11,7 +11,5 @@
-* Issues commented on github: 8
- * [woefe/git-prompt.zsh#44](https://github.com/woefe/git-prompt.zsh/issues/44) - [Feature] Status of the current process
+* Issues commented on github: 5
* [ClickHouse/ClickHouse#61541](https://github.com/ClickHouse/ClickHouse/issues/61541) - Improvements in CI jobs queue
* [psss/did#362](https://github.com/psss/did/issues/362) - Too recent GitHub pull requests included
- * [ClickHouse/ClickHouse#58979](https://github.com/ClickHouse/ClickHouse/issues/58979) - Logical error: 'Expected single dictionary argument for function.'. (Analyzer)
* [ClickHouse/ClickHouse#58497](https://github.com/ClickHouse/ClickHouse/issues/58497) - Why sending `SEGSEGV` does not terminate the clickhouse-server process
@@ -19,6 +17,4 @@
* [ClickHouse/ClickHouse#54767](https://github.com/ClickHouse/ClickHouse/issues/54767) - ClickHouse Keeper docker image and VOLUME directive
- * [ClickHouse/ClickHouse#39797](https://github.com/ClickHouse/ClickHouse/issues/39797) - Integration tests fail with timeout trying to pull `minio` image
-* Pull requests created on github: 12
- * [psss/did#363](https://github.com/psss/did/pull/363) - Fix GH commented filter and wrong `until`
+* Pull requests created on github: 11
* [ClickHouse/ClickHouse#61751](https://github.com/ClickHouse/ClickHouse/pull/61751) - Process removed files, decouple _check_mime
@@ -33,3 +29,3 @@
-* Pull requests commented on github: 25
+* Pull requests commented on github: 16
* [ClickHouse/ClickHouse#61715](https://github.com/ClickHouse/ClickHouse/pull/61715) - Test submodules-retries feature of ClickHouse/checkout
@@ -37,3 +33,2 @@
* [ClickHouse/ClickHouse#61662](https://github.com/ClickHouse/ClickHouse/pull/61662) - Fix logging of autoscaling lambda, add test for effective_capacity
- * [ClickHouse/ClickHouse#61658](https://github.com/ClickHouse/ClickHouse/pull/61658) - CI: integration tests: use runner as py module
* [ClickHouse/ClickHouse#61639](https://github.com/ClickHouse/ClickHouse/pull/61639) - [Experiment] Test the wrong duplicate
@@ -43,14 +38,6 @@
* [ClickHouse/ClickHouse#61592](https://github.com/ClickHouse/ClickHouse/pull/61592) - Improve build_download_helper
- * [ClickHouse/ClickHouse#61544](https://github.com/ClickHouse/ClickHouse/pull/61544) - Write `binary version -> commit hash` mapping to CI database (in private)
* [ClickHouse/ClickHouse#61530](https://github.com/ClickHouse/ClickHouse/pull/61530) - Fix client `-s` argument
- * [ClickHouse/ClickHouse#61197](https://github.com/ClickHouse/ClickHouse/pull/61197) - Merge commit style autofix
- * [ClickHouse/ClickHouse#61105](https://github.com/ClickHouse/ClickHouse/pull/61105) - Fix removing is_active node after re-creation
* [ClickHouse/ClickHouse#61089](https://github.com/ClickHouse/ClickHouse/pull/61089) - Analyzer: Fix 01244_optimize_distributed_group_by_sharding_key
- * [ClickHouse/ClickHouse#60656](https://github.com/ClickHouse/ClickHouse/pull/60656) - Add --now option to enable and start the service
* [python/mypy#16965](https://github.com/python/mypy/pull/16965) - Add a function to search for pyproject.toml in a project root
- * [ClickHouse/ClickHouse#59394](https://github.com/ClickHouse/ClickHouse/pull/59394) - Release pull request for branch 24.1
- * [ClickHouse/ClickHouse#58287](https://github.com/ClickHouse/ClickHouse/pull/58287) - Release pull request for branch 23.12
* [docker-library/official-images#15846](https://github.com/docker-library/official-images/pull/15846) - Initial commitment of clickhouse official image
- * [ClickHouse/ClickHouse#54187](https://github.com/ClickHouse/ClickHouse/pull/54187) - Release pull request for branch 23.8
- * [ClickHouse/ClickHouse#48280](https://github.com/ClickHouse/ClickHouse/pull/48280) - Release pull request for branch 23.3 |
b7983a0
to
38256ec
Compare
The tests fail with
It's expected. I am not sure how isolated the runners are now, but I feel that they are more or less static and used across the many jobs. As a quick solution, maybe it would help to replace |
Hello, dear @psss. I've spent some additional time researching whether it's possible to add an argument like For now, I've found that plugins' arguments are parsed automatically on the fly. I implemented something to add a hook for global StatsGroup arguments, but it would be good to discuss whether it fits the project or not. |
a015ee9
to
d585e98
Compare
Dear @psss, is there anything I can do to have a kick-start here? |
The last commit fixes the next issue
And makes it more friendly and descriptive:
|
@Felixoid, thanks a lot for looking into this! And sorry for the late response. The approach for fixing both issues looks good to me. Have two suggestions:
Could you please rebase on the latest |
until
commented
filter and wrong until
No problem, will do both! Glad you're back |
Should it be enabled or disabled by default? I'd disable it by default, but then smoking tests need the custom config |
Agreed, I'd also recommend to make the stats precise by default. Is the problem with the smoke test that it takes too long? We can adjust it if necessary. Also in recent commits a better support for handling github limits has been implemented, so even for larger reports it should now work nicely (although slowly) without interruption. |
The problem was the guaranteed out-of-requests issue. Maybe with a new approach it will be reliable |
GH search API unable to identify if the issues and PRs were updated by the user's comment. To make it reliable, one needs to search the comments for the entity after the `since` date, sort them by created_at field, and check if the comments in the given interval are created by the user.
The name of the method in different classes was the same, although each one did another thing. Renamed some of them to reflect the actual task.
I'll work on two things:
|
Hello. Here is a couple of fixes.
It fixes #362 by monkey-patching a wrong
until
value. GH search API requires exact values for bothsince
anduntil
It fixes #325 by additional filtering PRs and issues. For each entity, an additional request to GH API is done to check if the user has commented on it.