Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Missing pants/backend/experimental/tools/yamllint/__init__.py file #19820

Closed
kaos opened this issue Sep 12, 2023 · 4 comments · Fixed by #19899
Closed

Missing pants/backend/experimental/tools/yamllint/__init__.py file #19820

kaos opened this issue Sep 12, 2023 · 4 comments · Fixed by #19899
Labels
bug category:internal CI, fixes for not-yet-released features, etc.

Comments

@kaos
Copy link
Member

kaos commented Sep 12, 2023 

Can not check requirements for backend: 'pants.backend.experimental.tools.yamllint'. A __init__.py file is probably missing.

Tagging as internal as I don't believe it has a practical impact.
@kaos kaos added bug category:internal CI, fixes for not-yet-released features, etc. labels Sep 12, 2023
kaos added a commit that referenced this issue Sep 21, 2023
@kaos
Add missing __init__.py file for the yamllint backend.
7aeb542 
Closes #19820.
@kaos kaos mentioned this issue Sep 21, 2023
Merged
kaos added a commit that referenced this issue Sep 22, 2023
@kaos
Add missing __init__.py file for the yamllint backend. (#19899)
c7ecbc5 
Closes #19820.
WorkerPants pushed a commit that referenced this issue Sep 22, 2023
@kaos @WorkerPants
Add missing __init__.py file for the yamllint backend. (#19899)
598c7f5 
Closes #19820.
WorkerPants pushed a commit that referenced this issue Sep 22, 2023
@kaos @WorkerPants
Add missing __init__.py file for the yamllint backend. (#19899)
4bb057e 
Closes #19820.
This was referenced Sep 22, 2023
Merged
Merged
WorkerPants pushed a commit that referenced this issue Sep 22, 2023
@kaos @WorkerPants
Add missing __init__.py file for the yamllint backend. (#19899)
8b27f29 
Closes #19820.
@WorkerPants WorkerPants mentioned this issue Sep 22, 2023
Merged
kaos added a commit that referenced this issue Sep 22, 2023
@WorkerPants @kaos @huonw
Add missing __init__.py file for the yamllint backend. (Cherry-pi…
d58a817 
…ck of #19899) (#19908)

Closes #19820.

Co-authored-by: Andreas Stenius <andreas.stenius@imanage.com>
Co-authored-by: Huon Wilson <huon@exoflare.io>
kaos added a commit that referenced this issue Sep 22, 2023
@WorkerPants @kaos @huonw
Add missing __init__.py file for the yamllint backend. (Cherry-pi…
c3a6aa4 
…ck of #19899) (#19906)

Closes #19820.

Co-authored-by: Andreas Stenius <andreas.stenius@imanage.com>
Co-authored-by: Huon Wilson <huon@exoflare.io>
kaos added a commit that referenced this issue Sep 22, 2023
@WorkerPants @kaos @huonw
Add missing __init__.py file for the yamllint backend. (Cherry-pi…
95e1c59 
…ck of #19899) (#19907)

Closes #19820.

Co-authored-by: Andreas Stenius <andreas.stenius@imanage.com>
Co-authored-by: Huon Wilson <huon@exoflare.io>
@ryaminal
Copy link
Contributor

@kaos i'm seeing this warning now and it seems new. if i understand correct, there is no problem and i can safely ignore this message?

@kaos
Copy link
Member Author

kaos commented Nov 30, 2023

@kaos i'm seeing this warning now and it seems new. if i understand correct, there is no problem and i can safely ignore this message?

Yes, I believe it is harmless, but if you have issues with yamllint, upgrading to a version where this was fixed could resolve it in that case.

@ryaminal
Copy link
Contributor

ryaminal commented Dec 1, 2023 •
edited
Loading

oh, my error isn't specific to yamllint, but to a backend i have defined named dag... apparently i named a custom backend the same as a python resolve... and that was causing me all sorts of confusion. just added an __init__.py to my backend and it went away... sorry to waste time.

@kaos
Copy link
Member Author

kaos commented Dec 4, 2023

oh, my error isn't specific to yamllint, but to a backend i have defined named dag... apparently i named a custom backend the same as a python resolve... and that was causing me all sorts of confusion. just added an __init__.py to my backend and it went away... sorry to waste time.

Good find, and no time wasted on my part so don't worry about it ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug category:internal CI, fixes for not-yet-released features, etc.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add missing __init__.py file for the yamllint backend. pantsbuild/pants
2 participants
@kaos @ryaminal