These are chat archives for coala/coala-bears

19th
May 2018
Nalin Bhardwaj
@nalinbhardwaj
May 19 2018 08:48 UTC
@jayvdb : created coala/coala-bears#2490
John Vandenberg
@jayvdb
May 19 2018 09:51 UTC
thx
Vaibhav Rai
@RaiVaibhav
May 19 2018 10:02 UTC
Hey @jayvdb this issue still exists coala/coala#3182
same error and causing all the Clang bear to fail
John Vandenberg
@jayvdb
May 19 2018 10:41 UTC
yup
should I assign you to it?
John Vandenberg
@jayvdb
May 19 2018 10:52 UTC
nobody is working on the coala-bears breakage ?
Vaibhav Rai
@RaiVaibhav
May 19 2018 10:55 UTC
Sorry srsly no time already on debugger initial commit, I am already late, hoping you will understand
Thats why I asked about that bear as I want to check how my debbuger will perform on those bear who is not even returning anything
Viresh Gupta
@virresh
May 19 2018 12:04 UTC

nobody is working on the coala-bears breakage ?

For the breakage I can work on it, although not sure if we need to do mobanisation of .appveyor as a part of this issue or just change the yml for now ?

John Vandenberg
@jayvdb
May 19 2018 13:41 UTC
Problem exists in lots of repos
Moban is quicker
Viresh Gupta
@virresh
May 19 2018 14:12 UTC
Alright, I could see coala, coala-bears, PyPrint and coala-quickstart.
Any others that need to be kept in mind in case we mobanise appveyor configs ?
John Vandenberg
@jayvdb
May 19 2018 14:59 UTC
that should be enough to get the algorithm correct
Viresh Gupta
@virresh
May 19 2018 15:02 UTC
Okay, I will make an MR in the moban repo by tomorrow :)
Sanjeeth
@sanjeethboddi
May 19 2018 15:22 UTC
need help
coala/coala-bears#2306
as the regex is already able to find the endif or endfor without corresponding start tags. What am i supposed to do Imgur
Sanjeeth
@sanjeethboddi
May 19 2018 15:29 UTC
@kriti21
I would suggest you to read all the comments in this PR to better understand the issue.
Kriti Rohilla
@kriti21
May 19 2018 16:40 UTC
Based on https://github.com/coala/coala-bears/issues/1037#issuecomment-262212048 @jayvdb Is it that only one of the parent commits will be unmerged ?
Viresh Gupta
@virresh
May 19 2018 17:53 UTC

@jayvdb
I was looking at the appveyor configs
Seems like mobanising them might lead us to lose some useful comments
Or we might end up having a not very readable yaml full of comment strings in place of dictionary entries in order to supply values to the config file

Do you feel generating a yaml from a yaml would be worth it ?
(And we will definitely need syncing PRs for both coala and coala-bears as well, because of minor case differences in both the config files, like set and SET)

John Vandenberg
@jayvdb
May 19 2018 18:33 UTC
moving comments to mobans repo is fine
the comments are boilerplate stuff
Viresh Gupta
@virresh
May 19 2018 18:52 UTC
Okay cool
Kriti Rohilla
@kriti21
May 19 2018 19:52 UTC
Regarding coala/coala-bears#1037 . I have made some changes in GitCommitBear locally https://pastebin.com/tZRTQ3GN
How to add tests for this change since these merge commits are automatically created by github?
Viresh Gupta
@virresh
May 19 2018 22:54 UTC
@jayvdb
https://gitlab.com/coala/mobans/merge_requests/13/
Review needed
(currently doesn't require any changes in coala, only a syncing pr for coala-bears along with a newcomer issue to add appveyor in coala's .moban.yaml should suffice)