Skip to content

Conversation

@yadij
Copy link
Contributor

@yadij yadij commented Dec 10, 2025

  • trivial whitespace cleanup
  • reposition for alphabetical naming order
  • move SQUID_DEFINE_BOOL inside the check macro

@yadij
Copy link
Contributor Author

yadij commented Dec 10, 2025

FTR; these changes have already passed review in PR #1157.

@yadij yadij added M-cleared-for-merge https://github.com/measurement-factory/anubis#pull-request-labels S-could-use-an-approval An approval may speed this PR merger (but is not required) backport-to-v7 maintainer has approved these changes for v7 backporting labels Dec 10, 2025
@yadij
Copy link
Contributor Author

yadij commented Dec 21, 2025

These changes have reached 10+ days without any negative feedback. The merge bot should have committed them already.

@rousskov
Copy link
Contributor

rousskov commented Dec 21, 2025

These changes have reached 10+ days without any negative feedback.

Correct.

The merge bot should have committed them already.

Incorrect: The merge bot is correctly waiting for a required status check called "Review" to complete. GtHub clearly shows that some required checks have not been completed:

Some checks haven't completed yet
1 expected, 11 successful checks
1 pending check
Review  Expected — Waiting for status to be reported    Required

I have not checked why this GitHub-managed(?) "Review" status check was added to the set of the required PR checks. GtHub review counting has always been incompatible with how we count votes and should not be enabled. We have discussed that before.

I have not checked, but it is likely that the same recently introduced GitHub configuration(?) problem applies to other recent PRs, including #2316 and #2315.

FWIW, I do not recommend changing GitHub configuration without discussing those changes first.

@rousskov rousskov removed M-cleared-for-merge https://github.com/measurement-factory/anubis#pull-request-labels S-could-use-an-approval An approval may speed this PR merger (but is not required) labels Dec 21, 2025
@rousskov
Copy link
Contributor

The merge bot is correctly waiting for a required status check called "Review" to complete. GtHub clearly shows that some required checks have not been completed:

Some checks haven't completed yet
1 expected, 11 successful checks
1 pending check
Review  Expected — Waiting for status to be reported    Required

I have not checked why this GitHub-managed(?) "Review" status check was added to the set of the required PR checks. GtHub review counting has always been incompatible with how we count votes and should not be enabled. We have discussed that before.

I have now removed that "Review" check from the set of the required PR checks in our master branch configuration on GitHub. I have not investigated when/why it was added. This removal should allow eligible PRs to merge again.

@yadij yadij requested a review from rousskov December 23, 2025 22:09
@yadij yadij added the S-waiting-for-reviewer ready for review: Set this when requesting a (re)review using GitHub PR Reviewers box label Dec 23, 2025
kinkie
kinkie previously approved these changes Dec 25, 2025
@yadij
Copy link
Contributor Author

yadij commented Dec 30, 2025

Blocked for 3 weeks by @rousskov because lines of text unrelated to this PR exist in the Squid code.

@yadij yadij requested a review from kinkie December 30, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-to-v7 maintainer has approved these changes for v7 backporting S-waiting-for-reviewer ready for review: Set this when requesting a (re)review using GitHub PR Reviewers box

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants