coala command: use --limit-files#18
Conversation
|
Comment on 0fd5944, file test/resources/language/pep8.py, line 1. The code does not comply to PEP8. PEP8Bear, severity NORMAL, section The issue can be fixed by applying the following patch: --- a/test/resources/language/pep8.py
+++ b/test/resources/language/pep8.py
@@ -1 +1 @@
-a = 1 + 1 # <- not PEP8 compliant
+a = 1 + 1 # <- not PEP8 compliant |
|
@sils So this is the separate PR mentioned in #17. This is really how The issue now is that the PEP8 test file causes |
|
|
||
| [python] | ||
| bears = PEP8Bear | ||
| files = **.py |
There was a problem hiding this comment.
as per gitmate result #18 (comment) maybe put the test files into an ignore?
There was a problem hiding this comment.
see 875adbc which ignores the test file from root and includes it in the test subfolder (so that cask exec ert-runner picks it up). Test works, a local coala run from the root ignores the test file, but gitmate is still complaining. What am I missing? Is there a separate gitmate config?
|
Comment on 0fd5944, file test/resources/language/pep8.py, line 1. The code does not comply to PEP8. Origin: PEP8Bear, Section: The issue can be fixed by applying the following patch: --- a/test/resources/language/pep8.py
+++ b/test/resources/language/pep8.py
@@ -1 +1 @@
-a = 1 + 1 # <- not PEP8 compliant
+a = 1 + 1 # <- not PEP8 compliant |
|
Anyone working on this repo now? I guess 'Default' is deprecated now. |
|
ping @fleimgruber |
|
Not currently working on it. Will have a look in the next days. |
|
@Grox-Ni the last commit already contains that deprecation. |
|
FYI, I am using this on a daily basis and just tried with the most recent PyPI dev version and that works as well. AFAICS, the remaining problem is that gitmate-bot does not honour the "ignore" directive, see also #18 (comment). |
|
@fleimgruber you are right, I have an idea to solve gitmate's problem, please see #20, do you think I should reopen it? |
|
@Grox-Ni No. What @jayvdb said in #20 (comment) and following. |
|
@fleimgruber Are you still on this? Or should I close this? :) |
|
@nemaniarjun this is still waiting for feedback on CI failures because of gitmate-bot, see #18 (comment). |
|
@fleimgruber @Makman2 I am confused here, which config does gitmate bot use, the one in the PR or the one on master? Also can't we just override the CI so that we can get this merged? (I mean if gitmate uses the coafile from master then we should just merge this) |
|
I believe it takes it from the PR, otherwise you can't fix issues once they are on master. |
|
However I don't see a problem adding the test files to the |
|
Ah sorry haven't read it properly. Let's try to rebase and see if it works. If not, we have to investigate. |
|
@gitmate-bot rebase |
|
Once more, gitmate was disabled. |
|
@gitmate-bot rebase |
|
Hey! I'm GitMate.io! This pull request is being rebased automatically. Please DO NOT push while rebase is in progress or your changes would be lost permanently |
|
Automated rebase with GitMate.io was successful! 🎉 |
|
Hm seems the commits are already up-to-date, could you regenerate the commit hash @fleimgruber and repush? --> |
875adbc to
afe77d7
Compare
|
Comment on 0fd5944, file test/resources/language/pep8.py, line 1. The code does not comply to PEP8. Origin: PEP8Bear, Section: The issue can be fixed by applying the following patch: --- a/tmp/tmpan329k2u/test/resources/language/pep8.py
+++ b/tmp/tmpan329k2u/test/resources/language/pep8.py
@@ -1 +1 @@
-a = 1 + 1 # <- not PEP8 compliant
+a = 1 + 1 # <- not PEP8 compliant |
|
Done. gitmate still complains. |
|
Sorry for responding that late, I've become a bit busy and haven't worked through my notification queue^^ And I know the cause: I've actually missed your very first commit in this PR, because it was at the very top of this page. You have to squash the commits, gitmate will do its analysis on each commit and uses the repository state of it. So your commit that added the new filenames in .coafile does not ignore the test file yet and flags a problem. |
afe77d7 to
7f60105
Compare
|
@Makman2 well, how obvious it is in hindsight... done and gitmate does not complain anymore. |
| :error-patterns ((error (or "None" line) ":" (or "None" column) ":MAJOR:" (message)) | ||
| (warning (or "None" line) ":" (or "None" column) ":NORMAL:" (message)) | ||
| (info (or "None" line) ":" (or "None" column) ":INFO:" (message))) | ||
| :command ("coala" "--format" "{line}:{column}:{severity_str}:{message}" "--find-config" "--limit-files" source-original) |
There was a problem hiding this comment.
But won't limit-files filter out given files? Wouldn't this render the plugin completely useless?
| :command ("coala" "--format" "{line}:{column}:{severity_str}:{message}" "--find-config" "--limit-files" source-original) | ||
| :error-patterns ((error line-start (or "None" line) ":" (or "None" column) ":MAJOR:" (message) line-end) | ||
| (warning line-start (or "None" line) ":" (or "None" column) ":NORMAL:" (message) line-end) | ||
| (info line-start (or "None" line) ":" (or "None" column) ":INFO:" (message) line-end)) |
There was a problem hiding this comment.
Don't you have to adapt the coala --format to also emit line-starts and line-ends?
There was a problem hiding this comment.
See :error-patterns documentation and example in http://www.flycheck.org/en/latest/developer/developing.html#writing-the-checker. The line-start and line-end are rx pattern elements and do not map to checker command results.
|
7f60105 to
c3f56b7
Compare
|
Thanks for review. I addressed your comments, changed the commit message (typos) and reverted the regexp pattern change. With your consent I would squash. |
|
Alright you can squash ;) Please rectify your final commit message so things like |
Uses `--limit-files` instead of `--files`. coafile: Ignore for gitmate CI and include for ert.
c3f56b7 to
118576d
Compare
|
@Makman2 Squashed. |
Uses
--limit-filesinstead of--files. Also, additional line-startand line-end regexp patterns.