These are chat archives for coala/coala-bears

15th
Apr 2018
John Vandenberg
@jayvdb
Apr 15 2018 00:01
we merged without that change, due to human resource constraints
but lets recreate a sample code to show that problem and work out the upstream bug
John Vandenberg
@jayvdb
Apr 15 2018 01:52
coala/coala-bears#2134 ready for final reviews
Boxuan Li
@li-boxuan
Apr 15 2018 05:35
@jayvdb I have left a comment regarding mocked tests for non-free linter bears. https://gitlab.com/coala/non-free-linter-bears/issues/3#note_68461880
Anyone interested in linter bear may take a look at that repo :wink: It lacks basic infrastructure.
Dopamine Gamer
@DopamineGamer_twitter
Apr 15 2018 06:36
@jayvdb Hi. You mentioned earlier about a bug in coala around bear names if they don’t end with ‘Bear’. Could you point it to me?
Ankit Joshi
@MacBox7
Apr 15 2018 07:02
@jayvdb shoud I add deprecated setting for coala/coala-bears#2334
John Vandenberg
@jayvdb
Apr 15 2018 09:17
@DopamineGamer_twitter coala/coala#5134
@yukiisbored coala/coala-bears#2134
Sangam Kumar
@sangamcse
Apr 15 2018 15:46
@jayvdb, I am getting difficulty in understanding this.
John Vandenberg
@jayvdb
Apr 15 2018 15:50
that is me wondering out loud whether my existing choice is the best
when we release, the dependency should be ==0.x (last release number)
and that should be in all repos
keeping it global (in gitlab's coala/mobans) will mean that all repos need to be updated, and any failures are identified and fixed
Sangam Kumar
@sangamcse
Apr 15 2018 15:54
Have you tried ==0.xthere? If not, try once. :stuck_out_tongue:
John Vandenberg
@jayvdb
Apr 15 2018 15:55
hmm .. iirc we used to use >=0.x.0 to allow for patches
anyway that isnt the concern. im only wondering whether each repo should have a local setting. bears usually needs a local setting
John Vandenberg
@jayvdb
Apr 15 2018 16:12
snore
Sangam Kumar
@sangamcse
Apr 15 2018 16:16

:laughing: I just opened one more issue to coala/coala repo and now reviewing your PR :smiley:

snore

Dopamine Gamer
@DopamineGamer_twitter
Apr 15 2018 23:58
Sometimes flush-cache is not taken from .coafile. The run seems to still use the cache. If specified via CLI after that it seems fine. Any known issue? I couldn’t find any.