Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 07:31
    bkhanale synchronize #2934
  • 06:23
    jayvdb commented #2954
  • 06:22
    jayvdb assigned #2954
  • 06:22
    jayvdb labeled #2954
  • 06:22
    jayvdb commented #2954
  • 05:57
    Naveenaidu commented #6066
  • 05:56
    jayvdb commented #2954
  • Aug 22 18:33
    Naveenaidu commented #6066
  • Aug 22 18:27
    Naveenaidu commented #6066
  • Aug 22 17:57
    Naveenaidu synchronize #6066
  • Aug 22 17:21
    bkhanale synchronize #2934
  • Aug 22 16:52
    abhishalya commented #2912
  • Aug 22 16:50
    Naveenaidu commented #6066
  • Aug 22 16:48
    Naveenaidu opened #6066
  • Aug 22 15:06
    jayvdb closed #2946
  • Aug 22 15:06
    jayvdb closed #644
  • Aug 22 15:06

    jayvdb on master

    IndentationBear: Ignore doc com… (compare)

  • Aug 22 14:47
    jayvdb labeled #2954
  • Aug 22 14:47
    jayvdb labeled #2954
  • Aug 22 14:47
    jayvdb opened #2954
薛晓桂 Xue Xiaogui
@xiaoguizi87
Hello World
corobo-abhishalya
@corobo-abhishalya

Welcome @xiaoguizi87! :tada:

To get started, please follow our newcomers guide. The guide might tell you that corobo's command will get you an invite, but it won't, I'm not corobo (he's my father and he's too tired to work atm).

The alternative is to request access to gitlab instead. A developer or maintainer will then soon invite you to the organization. But just to let you know, the invite might get delayed since most of our maintainers are busy.

Only after you've received and accepted the invitation, we can assign issues. Until that, feel free to explore coala.

薛晓桂 Xue Xiaogui
@xiaoguizi87
hi, i wan't to fix coala/coala#5944
Nitish Gupta
@imnitishng
Hi everyone! Starting my open source journey with coala.
薛晓桂 Xue Xiaogui
@xiaoguizi87
corobo assign coala/coala#5944
corobo help
Piyush
@knightowl2704
Hello World
corobo-abhishalya
@corobo-abhishalya

Welcome @knightowl2704! :tada:

To get started, please follow our newcomers guide. The guide might tell you that corobo's command will get you an invite, but it won't, I'm not corobo (he's my father and he's too tired to work atm).

The alternative is to request access to gitlab instead. A developer or maintainer will then soon invite you to the organization. But just to let you know, the invite might get delayed since most of our maintainers are busy.

Only after you've received and accepted the invitation, we can assign issues. Until that, feel free to explore coala.

Prashant Sharma
@gutsytechster

Hello all, I am trying to install requirements but getting these errors when installing lxml via pip.
https://paste.fedoraproject.org/paste/w6erirt6OiLBiM~7dyluJw

I have looked for solutions and re-checked the installation of libxml2 and libxml2-dev and these packages are properly installed on my system. Still I am getting these errors.
Kindly have a look and help :)

BTW, I am using python 3.7.1
I am using LMDE(Linux Mint Debian Edition) as my OS
Keshav Garg
@KVGarg
Can you try to build using python v3.6? As currently coala doesn't supports Python v3.7
Prashant Sharma
@gutsytechster
Oh! Yeah sure.
Prashant Sharma
@gutsytechster
Thanks @KVGarg, it worked. I guess python's version was the problem.
However, when installing test-requirements I got these errors
ERROR: moban 0.3.10 has requirement ruamel.yaml==0.15.87, but you'll have ruamel-yaml 0.15.100 which is incompatible.
ERROR: pytest-xdist 1.29.0 has requirement pytest>=4.4.0, but you'll have pytest 3.6.4 which is incompatible.
These requirements seems to conflict each other
Prashant Sharma
@gutsytechster
Hey anyone got anything on this :point_up:?
I am still not able to run tests until I explicitly install pytest>=4.4.0.
Though by doing so, I am getting errors like https://paste.fedoraproject.org/paste/1mv7DS0o7alMicg1q-Odqg
Utkarsh Sharma
@Utkarsh1308
That is a problem with travis. I'm getting the same error
Prashant Sharma
@gutsytechster
Hmm.
Is there any solution to it?
Utkarsh Sharma
@Utkarsh1308
the problem basically arises because travis doesn't recognize the executable cpd or run.sh

Is there any solution to it?

Try installing them manually

Prashant Sharma
@gutsytechster
Do you mean executing run.sh?
Utkarsh Sharma
@Utkarsh1308
Try installing them manually in .travis.yml
Prashant Sharma
@gutsytechster
But when running the tests locally, how does .travis.yml file gets triggered?
Utkarsh Sharma
@Utkarsh1308
If you're running the tests locally then just make sure the executables are in your PATH. The tests should pass then
Prashant Sharma
@gutsytechster
I am exactly not able to get which executable is it searching for and where should it be by default?
Ok, I get the second part
It should be in our system PATH
Prashant Sharma
@gutsytechster
Hey, I am getting this error https://ci.appveyor.com/project/coala/coala-bears/builds/26862272/job/81isokrqkuiupbf1#L1521.
Can someone tell me, exactly how does run_bear_from_section work? Because it seems to be the cause of failed tests.
Prashant Sharma
@gutsytechster
However, when installing test-requirements I got these errors
ERROR: moban 0.3.10 has requirement ruamel.yaml==0.15.87, but you'll have ruamel-yaml 0.15.100 which is incompatible.
ERROR: pytest-xdist 1.29.0 has requirement pytest>=4.4.0, but you'll have pytest 3.6.4 which is incompatible.
How can I correct these conflicting requirements on local?
I mean as I have discussed above, if I explicitly install packages, then they give unexpected errors and doesn't run tests.
Abhinav Kaushlya
@abhishalya
Is the CI broken? If not then check if you're on venv, pip, python version
Prashant Sharma
@gutsytechster
How do I check if CI is broken? I am using virtual environment, with pip version 9.0.3 and python version 3.6.8
Abhinav Kaushlya
@abhishalya
Are you installing test-requirements from your coala fork? Since that's not updated
Prashant Sharma
@gutsytechster
I am installing test-requirements from coala-bears repository fork
Abhinav Kaushlya
@abhishalya
Sorry couldn't replicate, best thing you could do is creating a new venv and try again
Prashant Sharma
@gutsytechster
After installing requirements and test-requirements, what is the version of pytest-xdist and pytest do you get?
Abhinav Kaushlya
@abhishalya
Afaik, pytest-xdist was removed from test-requirements.txt
Prashant Sharma
@gutsytechster
Oh! I am not sure, why it got installed.
Let me try creating a new virtual env and installing requirements again
Prashant Sharma
@gutsytechster
Well, pytest seems to work now without explicitly installing any other version. But these errors are still showing up https://paste.fedoraproject.org/paste/CZV1yx7V6sU~dcR2KK3AwQ
Abhinav Kaushlya
@abhishalya

If you're running the tests locally then just make sure the executables are in your PATH. The tests should pass then

:point_up:

Prashant Sharma
@gutsytechster
Which executable are we talking about here?
My $PATH variable holds /home/gutsytechster/miniconda3/envs/coala-env/bin:/home/gutsytechster/miniconda3/condabin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/sbin:/usr/sbin:/sbin
Abhinav Kaushlya
@abhishalya
I think cpd is the executable name and it comes under pmd. So check if you have pmd installed
Prashant Sharma
@gutsytechster
Ok
Prashant Sharma
@gutsytechster
Thanks @abhishalya
That worked. I didn't have pmd installed
Abhinav Kaushlya
@abhishalya
No problem @gutsytechster :smile: