-
Notifications
You must be signed in to change notification settings - Fork 581
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.
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
MarkdownBear doesn't work anymore #1235
Comments
my fault, wrong remark installed... we have to do something against this. |
Yea, the docker is broken for MarkdownBear : https://travis-ci.org/jayvdb/docker-coala-base/builds/188134615#L9730 . The cause is |
An easier workaround is to replace |
Install npm packages locally and add the local binaries to the PATH. Fixes coala/coala-bears#1235
Install npm packages locally and add the local binaries to the PATH. Fixes coala/coala-bears#1235
unfortunately this issue doesnt include a travis log to confirm which image was broken. I tested in 0.9 again, and it worked: https://travis-ci.org/jayvdb/sails-docs/builds/188711823 |
See also #926 |
CC @namanyadav12 we think your code may have broken this bear. |
So we may want to try reverting 57dbcc4 |
Oh sorry for the troubled caused. |
Will the problem solve if I change "remark-lint": ">=5.1.0" to "remark-lint": "~5.1.0" |
No. That was a problem with the docker. |
Ok |
@namanyadav12 , your last message here was 5 days ago. You have been working on #1277 instead, which is quite distressing. This bug is the most critical problem in the pre-release. Can you get this bear working correctly? promptly? |
Also added a better test to check the exact message of the result. Fixes coala#1235
https://travis-ci.org/jayvdb/discourse_docker/builds/208883544 is a build using the 0.10 docker image; the markdown files are wiped out. |
Another example, in our own backyard : https://gitlab.com/yuki_is_bored/cobot/builds/12258827 |
I've confirmed in many different ways that the problem is in remark, and maybe isolated to specific versions (of node stuff?) in the docker image. It can be reproduced by moving out of the |
remark-cli needs to find its plugins. When invoked in `/coala-bears` directory, Node automatically looks in `node_modules`. However if the docker image is used normally the working directory will not be `/coala-bears`. Setting NODE_PATH ensures that the plugins can be found. Related to coala/coala-bears#1235
remark-cli needs to find its plugins. When invoked in `/coala-bears` directory, Node automatically looks in `node_modules`. However if the docker image is used normally the working directory will not be `/coala-bears`. Setting NODE_PATH ensures that the plugins can be found. Related to coala/coala-bears#1235
remark-cli needs to find its plugins. When invoked in `/coala-bears` directory, Node automatically looks in `node_modules`. However if the docker image is used normally the working directory will not be `/coala-bears`. Setting NODE_PATH ensures that the plugins can be found. Related to coala/coala-bears#1235
remark-cli needs to find its plugins. When invoked in `/coala-bears` directory, Node automatically looks in `node_modules`. However if the docker image is used normally the working directory will not be `/coala-bears`. Setting NODE_PATH ensures that the plugins can be found. Related to coala/coala-bears#1235
remark-cli needs to find its plugins. When invoked in `/coala-bears` directory, Node automatically looks in `node_modules`. However if the docker image is used normally the working directory will not be `/coala-bears`. Setting NODE_PATH ensures that the plugins can be found. Related to coala/coala-bears#1235
So it is important to note that this can be fixed by the person who has installed the bear dependencies. Ideally we also raise a bug upstream, and/or try to workaround the problem in the bear, probably for 0.10.3. |
Worth noting ... the docker .travis.yml now has a test for this. And before we raise an upstream bug, using an old version of remark, we need to create a demo repo so it shows the problem clearly, and hopefully remark authors can easily see a fix. If we dont make it easy, they will close the bug and tell us to upgrade to the latest version of remark. |
remark-cli needs to find its plugins. When invoked in `/coala-bears` directory, Node automatically looks in `node_modules`. However if the docker image is used normally the working directory will not be `/coala-bears`. Setting NODE_PATH ensures that the plugins can be found. Related to coala/coala-bears#1235
We could anchor a release note on #1630 , if that is merged and backported to 10.2. |
We are having a new release soon, still backport needed? |
A better test for MarkdownBear to check the exact message of the result for a maximum line length error. Related to coala#1235
It always wants to empty all my files, something's horribly wrong here.
This issue was found by @nutella25 and I can reproduce it.
type bug importance critical needs backport
Opened via gitter by @sils
The text was updated successfully, but these errors were encountered: