Skip to content

Remove old limiter algo comparison - #591

Merged
neSpecc merged 1 commit into
masterfrom
limiter-remove-counter-comparison
Sep 17, 2026
Merged

neSpecc merged 1 commit into
masterfrom
limiter-remove-counter-comparison

Conversation

@Kuchizu

@Kuchizu Kuchizu commented Sep 17, 2026

Copy link
Copy Markdown
Member

Remove old limiter algo comparison

@neSpecc
neSpecc merged commit a6b1757 into master Sep 17, 2026
5 checks passed
@neSpecc
neSpecc deleted the limiter-remove-counter-comparison branch September 17, 2026 19:26
@Kuchizu Kuchizu mentioned this pull request Sep 17, 2026
Kuchizu added a commit that referenced this pull request Sep 26, 2026
* fix(grouper): fix some ts errors (#581)

* Use dailyEvents counter for all workspaces in limiter (#584)

* Stop limiter from opening every events collection each hour (#587)

* Stop limiter from opening every events collection each hour

* Comment limiter dailyEvents aggregation sections

* Report sampled limiter counter validation to Telegram

* Compare old and new limiter algo for listed workspaces instead of sampling

* Use the previous dailyEvents query for old algo comparison

* Remove old limiter algo comparison (#591)

* Exit runner when a worker fails to start (#594)

---------

Co-authored-by: Peter <[email protected]>
Co-authored-by: Kuchizu <[email protected]>
alisawavezen12 added a commit that referenced this pull request Oct 14, 2026
* fix(grouper): fix some ts errors (#581)

* Use dailyEvents counter for all workspaces in limiter (#584)

* Stop limiter from opening every events collection each hour (#587)

* Stop limiter from opening every events collection each hour

* Comment limiter dailyEvents aggregation sections

* Report sampled limiter counter validation to Telegram

* Compare old and new limiter algo for listed workspaces instead of sampling

* Use the previous dailyEvents query for old algo comparison

* Remove old limiter algo comparison (#591)

* Exit runner when a worker fails to start (#594)

* Add release validator and regression tracking (#590)

* Add release validator worker

* Track event regressions by release

* chore

* Support repeated resolution and regression cycles

* validate Events Batch

* Add release validator to Docker Compose

* chore

* chore

* chore

* chore

* Align release validation with retention policy

Use MAX_DAYS_NUMBER to define the candidate release window and fall
back to event timestamps when original release records are archived.

* Isolate release validation failures by project

* Clear regression when resolving event again

* Track latest event occurrence before validation

* tests fix

* chore

* chore

---------

Co-authored-by: Peter <[email protected]>
Co-authored-by: Kuchizu <[email protected]>
Co-authored-by: alisawavezen12 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants