These are chat archives for coala/coala-bears

3rd
Aug 2017
John Vandenberg
@jayvdb
Aug 03 2017 11:45
docker broken again, this time by a rubygem coala/docker-coala-base#234
John Vandenberg
@jayvdb
Aug 03 2017 17:35
docker broken again, by @yash-nisar 's new bear
John Vandenberg
@jayvdb
Aug 03 2017 18:38
coala/docker-coala-base#238 @Makman2 @yash-nisar urgent review to unbreak the docker
John Vandenberg
@jayvdb
Aug 03 2017 18:57
@NiklasMM , and one for you ... coala/docker-coala-base#236 / coala/coala-bears#1975 ;-)
and now I need @makman2's voodoo instance variable REQUIREMENTS
Mischa Krüger
@Makman2
Aug 03 2017 19:15
@jayvdb the docker cloud build failed, and can't access the logs :/
And what do you need the instance-bound requirements for? :D
I think I have a commit ready with it (adapted to next gen core though)
Makman2/...
Uhm lemme see again :3
Mischa Krüger
@Makman2
Aug 03 2017 19:21
Makman2/runtime-deps
John Vandenberg
@jayvdb
Aug 03 2017 19:21
docker cloud (and travis ci) regularly fail due to coala/docker-coala-base#224
Mischa Krüger
@Makman2
Aug 03 2017 19:22
The commit is wip it seems, however it works basically the same as the commit before with bear.BEAR_DEPs
John Vandenberg
@jayvdb
Aug 03 2017 19:22
which is a serious problem in coala, somewhere, recently added
Mischa Krüger
@Makman2
Aug 03 2017 19:26
Oh :/
Not sure is docker cloud required for merge?
John Vandenberg
@jayvdb
Aug 03 2017 19:26
nope
either build is good enough
Mischa Krüger
@Makman2
Aug 03 2017 19:27
Yeah commit looks fine with me
We also need to make the docker cloud builds publicly accessible
John Vandenberg
@jayvdb
Aug 03 2017 19:27
ill go look
Mischa Krüger
@Makman2
Aug 03 2017 19:27
Being required to login is a bit annoying :/
John Vandenberg
@jayvdb
Aug 03 2017 19:29
I cant see any setting for making them public
Mischa Krüger
@Makman2
Aug 03 2017 19:30
@jayvdb acked your commit
And that's bad :/
That's uncool from docker :/
John Vandenberg
@jayvdb
Aug 03 2017 19:35
I've created a maintainers team and added you
Mischa Krüger
@Makman2
Aug 03 2017 19:35
Cool thx :)
John Vandenberg
@jayvdb
Aug 03 2017 19:36
but .. no place to add permissions for public
would love a review of coala/docker-coala-base#149 ; makes it much easier to see where all the packages were fetched from
Mischa Krüger
@Makman2
Aug 03 2017 19:45
Hm.
<progress id=...>
Doesn't read so we'll :sweat_smile:
Well*
John Vandenberg
@jayvdb
Aug 03 2017 19:46
openSUSE/zypper#122
If it fails, too much info is good. currently when zypper is completed, the output doesnt show where the packages were fetched from
John Vandenberg
@jayvdb
Aug 03 2017 19:52
I could use zypper -vv (redirected to file) and on success parse it with sed to only show the URLs ; then on error, show the -vv output, which is more readable than the xml, but has so much whitespace.
John Vandenberg
@jayvdb
Aug 03 2017 20:08
The full URLs in the -vv output can be seen at https://travis-ci.org/jayvdb/docker-coala-base/builds/260087371#L2849 , and include done markers on the stdout. I wonder if the output is simplified if sent to a file
Mischa Krüger
@Makman2
Aug 03 2017 20:20
A bit tired now, will review more thoroughly tomorrow
Slept quite bad ^^
John Vandenberg
@jayvdb
Aug 03 2017 20:42
no probs; ive switched to using -vv