Skip to content

Conversation

@lukebakken
Copy link
Contributor

Fixes #113

@meta-cla
Copy link

meta-cla bot commented Aug 21, 2025

Hi @lukebakken!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@meta-cla
Copy link

meta-cla bot commented Aug 22, 2025

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla bot added the cla signed label Aug 22, 2025
@robertoaloi
Copy link
Contributor

Thanks!

Out of curiosity, is there any reason why you want to disable this linter? Is it generating false positives?

@facebook-github-bot
Copy link
Contributor

@robertoaloi has imported this pull request. If you are a Meta employee, you can view this in D80779500.

@robertoaloi
Copy link
Contributor

@lukebakken There's a formatting issue on diagnostics.rs. Apart from that, it looks good.

@lukebakken
Copy link
Contributor Author

Out of curiosity, is there any reason why you want to disable this linter? Is it generating false positives?

Most of the RabbitMQ Common Test suites export everything, which generates a lot of false positives.

@lukebakken
Copy link
Contributor Author

@robertoaloi I've addressed the formatting issue, and made a note for future contributors to do the same.

@robertoaloi
Copy link
Contributor

@robertoaloi I've addressed the formatting issue, and made a note for future contributors to do the same.

Thanks! CI actually has that step, but:

  1. It needs approval to run on our side (you may need to enable actions on your fork to get earlier feedback)
  2. I think it's misconfigured to only work on push and not on pull requests (should be easy to solve)

@facebook-github-bot
Copy link
Contributor

@robertoaloi has imported this pull request. If you are a Meta employee, you can view this in D80779500.

@facebook-github-bot
Copy link
Contributor

@robertoaloi merged this pull request in 0809b9c.

@lukebakken lukebakken deleted the lukebakken/gh-113 branch August 25, 2025 18:55
facebook-github-bot pushed a commit that referenced this pull request Aug 26, 2025
Summary:
We currently run the main CI job on pushes only. This means we don't automatically run CI on pull requests from third-party users.
This is not ideal and can create delays for trivial issues such as bad formatting (see [example](#114)).

Reviewed By: TD5

Differential Revision: D80930880

fbshipit-source-id: d3f5a460fdf92a3e7a1842e07a0b97e098a7c197
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

W0008 diagnostic can't be disabled

3 participants