These are chat archives for coala/coala-bears

29th
May 2017
John Vandenberg
@jayvdb
May 29 2017 01:33
Kuniwak/vint#215 no traction
Muhammad Kaisar Arkhan
@yukiisbored
May 29 2017 03:49
cobot new issue Bear Proposal: PerlTidy
http://perltidy.sourceforge.net/
coala-bot
@coala-bot
May 29 2017 03:49
Here you go : undefined
Muhammad Kaisar Arkhan
@yukiisbored
May 29 2017 03:49
what?
cobot help
coala-bot
@coala-bot
May 29 2017 03:50
Hello World - Get invited to the coala organization.
cobot (invite|inv) <username> [to [team]] - Allows maintainers to invite users to the coala organization.
cobot (new|file) issue <repository> <title><newline>[description] - Creates a GitHub issue given the repo name, title and description. Write description in new line.
cobot <nevermind|nm> - Doesn't mind.
cobot <wa|wolfram> <question> - Searches Wolfram Alpha for the answer to the question.
cobot assign <issue_link> - Assigns issue <issue_link> to user
cobot explain [topic] [to <explainee>] - Returns the info we have on your topic. Use explainee tag only if you want to mention it to anyone.
cobot ghetto <text> - Real talk yo
cobot help - Displays all of the help commands that Hubot knows about.
cobot help <query> - Displays all help commands that match <query>.
cobot lmgtfy <term> - Searches google for you!
cobot mark (wip|pending) <pull URL> - Marks the given pull request as work in progress/pending review.
cobot the rules - Make sure hubot still knows the rules.
cobot unassign <issue_link> - Unassign the user from the issue <issue_link>
ship it - Display a motivation squirrel
John Vandenberg
@jayvdb
May 29 2017 03:50
missing repo name
Muhammad Kaisar Arkhan
@yukiisbored
May 29 2017 03:50
cobot new issue coala-bears Bear Proposal: PerlTidy
http://perltidy.sourceforge.net/
John Vandenberg
@jayvdb
May 29 2017 03:50
can you do help in the test channel or private channel :P
coala-bot
@coala-bot
May 29 2017 03:50
Here you go : coala/coala-bears#1786
Muhammad Kaisar Arkhan
@yukiisbored
May 29 2017 03:50
euhm, what kind?
the cobot-test channel?
John Vandenberg
@jayvdb
May 29 2017 03:51
ya
Muhammad Kaisar Arkhan
@yukiisbored
May 29 2017 04:00
cobot help
John Vandenberg
@jayvdb
May 29 2017 05:21
3 days and all users of coala are screwed
(if they use CI, or upgrade to the latest requests)
Meet Mangukiya
@meetmangukiya
May 29 2017 05:28
Please pin requests and back port for gods sake(as a temp solution)
At least we'll have one version working
Fwiw docker images would still be working if they weren't rebuilt after the breakage
John Vandenberg
@jayvdb
May 29 2017 05:30
that would require releases of coala and coala-bears
if we only deactivate vim-vint, we only need to release coala-bears
IMO deactivating vim-vint is the better option, as I doubt anyone is using it, and if they are, they can put pressure on the maintainer
anyway ... coala/coala-bears#1785 is unassigned .. someone needs to take it up and do something
im at work
Arjun Singh Yadav
@arjunsinghy96
May 29 2017 06:44
tests are failing on windows. I am investigating it currently.
John Vandenberg
@jayvdb
May 29 2017 06:44
strange - @yukiisbored just fixed it
Arjun Singh Yadav
@arjunsinghy96
May 29 2017 06:46
AppVeyor is failing on pip install --pre coala-bears
IMO its some dependency stuff
it uninstalls 0.5.0.dev and installs 0.4.0
yuki's tests are OK :+1:
Arjun Singh Yadav
@arjunsinghy96
May 29 2017 07:08
So version in coala/requirements.txtneed changing or something else ??
https://ci.appveyor.com/project/ArjunSinghYadav/package-manager/build/1.0.220/job/7dh5013br0697ih0
John Vandenberg
@jayvdb
May 29 2017 07:45
Ah, which coala is being installed. You need pre release
just disable your appveyor and repush
Or, and coala>=... to requirements.txt in your commit
Arjun Singh Yadav
@arjunsinghy96
May 29 2017 09:33
In appveyor.yml we have pip install --pre coala-bears.
requirements.txt of coala-bears have development version of coala.
coala have dependency_management~=0.4.0 removes previous installation of dependency_management 0.5.0.dev on appveyor and we get FileNotFoundError.
disabling appveyor will simply make master branch red when merged.
Arjun Singh Yadav
@arjunsinghy96
May 29 2017 09:43
coala/coala#4277. The same error is also present. The PR was green earlier on appveyor. So, requests may be the reason. So I will disable appveyor.
Naman Maheshwari
@naman1901
May 29 2017 18:08
Can someone direct me towards docs on setting inheritance?
I've looked in bear, bearlib and settings. Haven't been able to find the solution.
Basically, I want to check if a setting was set for that block or was it inherited.
Links to any similar issue would be great help too
Lasse Schuirmann
@sils
May 29 2017 18:12
in a bear?
I think for the __iter__ there's a defaults=True which you can invoke with false to iterate over all settings which are directly specce in that section
there might be more, check Setting.py
Naman Maheshwari
@naman1901
May 29 2017 18:23
The signature is def __iter__(self, remove_backslashes=True), but there are other methods like __path__. I guess I can use that to identify where the setting came from and compare it to my current path. Is that correct?
Lasse Schuirmann
@sils
May 29 2017 18:29
the origin is where it came from, that'll be the coafile not the section
what do you want it for?
Naman Maheshwari
@naman1901
May 29 2017 18:33
coala/coala-bears#1778
This issue that I am working on. I need to be able to determine if use_spaces was inherited or set in the current block.
Lasse Schuirmann
@sils
May 29 2017 18:35
I don't understand the reasoning yet why it's important if it's inherited
Naman Maheshwari
@naman1901
May 29 2017 18:37
So the Bear uses a linter that uses tabbed indentation. So I was tasked with raising an error if someone tried to use it with use_spaces = True, because the linter doesn't support it.
I'm being asked now to raise the error only if that param was set in the current block and was not inherited. I guess I need to just print out a warning if that's the case.
If its inherited, that is
Lasse Schuirmann
@sils
May 29 2017 18:40
ok then I disagree
I'll post my reason on the PR
Naman Maheshwari
@naman1901
May 29 2017 18:40
Sure. Thanks :)
I personally think the error should be thrown irrespective of when the param was set, because the linter doesn't support it. But I'm new here and I still haven't got a proper idea of how everything works.
Lasse Schuirmann
@sils
May 29 2017 18:44
please do express your thoughts
the worst thing you can have is a contributor who turns off thinkin on his own ^^
if you don't understand something it's good to dig into it and eventually also ask for more info!
Naman Maheshwari
@naman1901
May 29 2017 18:46
Will do from now on. coala is my first foray into open source, so I'm a bit intimidated :P
Lasse Schuirmann
@sils
May 29 2017 18:47
no worries :) you can also do code review, your opinion is much appreciated!
Naman Maheshwari
@naman1901
May 29 2017 18:49
Do I not have to wait for my first PR to be accepted? Its the newcomer issue I solved at coala/coala-bears#1767. If you're free, can you take a quick look? It has passed all its builds and checks.
Lasse Schuirmann
@sils
May 29 2017 19:53
yeah check coala.io/review there's a long queue
this is a bit of a problem