These are chat archives for coala/coala-bears

28th
Nov 2017
Mamat Rahmat
@mamat-rahmat
Nov 28 2017 01:00
my hypothesis is, model is not updated for a while
https://gitlab.com/coala/landing/blob/master/backend/bears/cron.py
John Vandenberg
@jayvdb
Nov 28 2017 01:11
Correct
Sushil khanchi
@khanchi97
Nov 28 2017 11:30
What value we have to pass to --files argument while running a GlobalBear?
John Vandenberg
@jayvdb
Nov 28 2017 11:53
I do --files .coafile ;-)
Sushil khanchi
@khanchi97
Nov 28 2017 11:58

I do --files .coafile

you do it just for passing an argument and fill that void space?

John Vandenberg
@jayvdb
Nov 28 2017 11:59
yup; a workaround
Adhityaa
@adtac
Nov 28 2017 12:02
hmm, is there an issue related to this?
maybe --files /dev/null would work too :P
Sushil khanchi
@khanchi97
Nov 28 2017 12:03

hmm, is there an issue related to this?

No.I'm just writing a GlobalBear and this question comes in my mind.

Adhityaa
@adtac
Nov 28 2017 12:04
corobo new issue coala-bears Don't require a --files flag if we're running only global bears
corobo
@co-robo
Nov 28 2017 12:04
Here you go: coala/coala-bears#2144
Adhityaa
@adtac
Nov 28 2017 12:04
doesn't hurt to create an issue :)
Sushil khanchi
@khanchi97
Nov 28 2017 12:06
I want to ask one more thing when we use a GlobalBear so ideally does it ask for directory where it should analyse or in current directory?
Adhityaa
@adtac
Nov 28 2017 12:07
it's usually the directory in which your coafile lives
if you don't have any in any ancestor directory, it's the current directory
not sure if we have support for providing a custom directory
John Vandenberg
@jayvdb
Nov 28 2017 12:08

maybe --files /dev/null would work too :P

haha

Sushil khanchi
@khanchi97
Nov 28 2017 12:10

it's usually the directory in which your coafile lives

So when writing GlobalBear, should I have to implement this thing also i.e first search for a .coafile if it exists then analyse that dir otherwise current dir

Adhityaa
@adtac
Nov 28 2017 12:10
no, that's taken care in coalib
Sushil khanchi
@khanchi97
Nov 28 2017 12:19
@adtac while using this --files /dev/null
No files matching /dev/null were found.
Adhityaa
@adtac
Nov 28 2017 12:20
lol
Sushil khanchi
@khanchi97
Nov 28 2017 12:20
:smile:
Adhityaa
@adtac
Nov 28 2017 12:20
coala is trying to glob that wrt to the current directory
Sushil khanchi
@khanchi97
Nov 28 2017 12:20
yeah
Adhityaa
@adtac
Nov 28 2017 12:20
corobo new issue coala Support --files /dev/null
corobo
@co-robo
Nov 28 2017 12:20
Here you go: coala/coala#4916
Sushil khanchi
@khanchi97
Nov 28 2017 12:37

@adtac As you said that's taken care in coalib

no, that's taken care in coalib

Can you take a look at IMG1 which is not showing any result except executing section cppcheck...
executing section cli...

and now take a look at last line of IMG2 I just add os.getcwd() and it worked fine.

Adhityaa
@adtac
Nov 28 2017 12:41
The difference is that you're passing an argument to cppcheck
coalib won't automatically add that argument for you
what I meant by "that's taken care in coalib" is that coalib will find the root directory to work from
it's up to you to pass that information to external linters
(at least that's what I think; my knowledge of bears is limited)
Sushil khanchi
@khanchi97
Nov 28 2017 12:55

not sure if we have support for providing a custom directory

It supports I just check it :smiley: