|
2018-04-11 00:49:00
|
<Dispenser>
|
Somebody should file a bug that phabricator should use <ins> and <del> instead of <span class="old/new"> for diffs
|
|
2018-04-11 03:51:33
|
<closedmouth>
|
yeah someone should
|
|
2018-04-11 14:02:38
|
<Nudin_WMDE>
|
<Nudin_WMDE> Technical Advice IRC meeting starting in 60 minutes in channel #wikimedia-tech, hosts: @addshore & @Pablo_WMDE - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
|
|
2018-04-11 14:59:22
|
<addshore>
|
o/
|
|
2018-04-11 15:01:32
|
<Nudin_WMDE>
|
o/ time for taim
|
|
2018-04-11 15:02:09
|
<addshore>
|
Welcome all to this weeks install of the Technical Advice IRC meetting!
|
|
2018-04-11 15:02:44
|
<addshore>
|
With Pablo_WMDE and myself!
|
|
2018-04-11 15:02:49
|
<Pablo_WMDE>
|
Hello!
|
|
2018-04-11 15:03:08
|
<andre__>
|
o/
|
|
2018-04-11 15:03:14
|
<addshore>
|
\o
|
|
2018-04-11 15:03:18
|
<Pablo_WMDE>
|
\o/
|
|
2018-04-11 15:05:22
|
<Lucas_WMDE>
|
~o~
|
|
2018-04-11 15:08:14
|
<addshore>
|
So, any questions?? :D
|
|
2018-04-11 15:08:45
|
<mainframe98>
|
I have one, I asked earlier, but got no reply (or got lost in connection failure)
|
|
2018-04-11 15:09:03
|
<addshore>
|
okay!
|
|
2018-04-11 15:09:10
|
<addshore>
|
fire away!
|
|
2018-04-11 15:09:11
|
<mainframe98>
|
So I've created a PHP version of the OOUI NumberInputWidget, but I can't get it to infuse properly
|
|
2018-04-11 15:09:18
|
<mainframe98>
|
Let me look up the error real quick
|
|
2018-04-11 15:09:35
|
<addshore>
|
ooooh, interesting
|
|
2018-04-11 15:10:10
|
<mainframe98>
|
So it says Unkown widget type; OO.ui.NumberInputWidget. Inspecting in the Browser tools shows that OO.ui does not contain NumberInputWidget.
|
|
2018-04-11 15:10:44
|
<mainframe98>
|
I recall that in MediaWiki you had to add a .widget resource loader module, but I'm not sure how I'd do such thing for OOUI, if that's even the solution
|
|
2018-04-11 15:11:16
|
<mainframe98>
|
The JavaScript version works fine on the JavaScript part of the demo.
|
|
2018-04-11 15:11:24
|
<addshore>
|
hmmm
|
|
2018-04-11 15:11:32
|
<Pablo_WMDE>
|
did you follow https://www.mediawiki.org/wiki/OOUI/PHP_examples ?
|
|
2018-04-11 15:12:24
|
<addshore>
|
It may have something to do with resourceloader modules and dependencies
|
|
2018-04-11 15:12:44
|
<mainframe98>
|
That should've been handled by the Demo, basically all I've done is add the fields to the demo.
|
|
2018-04-11 15:13:17
|
<mainframe98>
|
I forgot to mention that this is the OOUI standalone version, outside MediaWiki. So there's not MediaWiki running, just like here: https://doc.wikimedia.org/oojs-ui/master/demos/demos.php
|
|
2018-04-11 15:13:43
|
<Pablo_WMDE>
|
oh. is ee
|
|
2018-04-11 15:13:46
|
<Pablo_WMDE>
|
i see
|
|
2018-04-11 15:13:52
|
<addshore>
|
Ahhhh
|
|
2018-04-11 15:15:21
|
<addshore>
|
mainframe98: do you have a copy of code we can run locally?
|
|
2018-04-11 15:15:42
|
<mainframe98>
|
I'll see if I can create a gist.
|
|
2018-04-11 15:15:51
|
<addshore>
|
that would be great!
|
|
2018-04-11 15:18:36
|
<mainframe98>
|
Gist: https://gist.github.com/mainframe98/8370dc2b887c0b081ab16e131762a6e8
|
|
2018-04-11 15:19:01
|
<mainframe98>
|
Should just be applicable to https://phabricator.wikimedia.org/diffusion/GOJU/ by git apply
|
|
2018-04-11 15:21:57
|
<CFisch_WMDE>
|
mainframe98: Looking at the demo page above I just saw, that it does not include a NumberInputWidget ... so also in the JS code of that Demo page is no NumberInputWidget loaded / defined
|
|
2018-04-11 15:22:32
|
<CFisch_WMDE>
|
When you go to the JS tab on the demo page the widgit is included but not on the PHP tab
|
|
2018-04-11 15:23:29
|
<mainframe98>
|
Indeed, which is why I've (attempted to) create a PHP version, which should be infusable. The console then reports that on the PHP tab that it can't infuse the numberInputWidget because of an unknown widget type
|
|
2018-04-11 15:25:04
|
<CFisch_WMDE>
|
But still you would need to load the JS for that widget I guess
|
|
2018-04-11 15:25:37
|
<CFisch_WMDE>
|
at least if I am not totally mistaken here ^^'
|
|
2018-04-11 15:26:37
|
<mainframe98>
|
CFisch_WMDE: Well, on the PHP tab, the other widgets are loaded on infusion, except NumberInputWidget. It doesn't help that I can't find anywhere I'd need to add something that should load it.
|
|
2018-04-11 15:27:13
|
<mainframe98>
|
I've got nothing to compare it too. It almost seems the other widgets are loaded through magic, since I can't find an explicit loading mechanism
|
|
2018-04-11 15:27:32
|
<addshore>
|
So, https://doc.wikimedia.org/oojs-ui/master/demos/dist/oojs-ui-widgets.js contains NumberInputWidget
|
|
2018-04-11 15:28:13
|
<addshore>
|
Interestingly the PHP page loads <script src="classes/ButtonStyleShowcaseWidget.js"></script> explicitly, not sure why
|
|
2018-04-11 15:28:47
|
<mainframe98>
|
Bet that that is because the show case for the buttons is unique in the sense that it's for show, and not really for actual use.
|
|
2018-04-11 15:29:29
|
<CFisch_WMDE>
|
The PHP page only loads https://doc.wikimedia.org/oojs-ui/master/demos/dist/oojs-ui-core.js that does not contain the NumberWidget
|
|
2018-04-11 15:29:37
|
<CFisch_WMDE>
|
when the infusion code runs from https://doc.wikimedia.org/oojs-ui/master/demos/infusion.js
|
|
2018-04-11 15:29:44
|
<CFisch_WMDE>
|
he goes through all elements
|
|
2018-04-11 15:29:47
|
<Csisc>
|
Hello, I had a problem when installing Pywikibot in Python 3.5
|
|
2018-04-11 15:29:54
|
<CFisch_WMDE>
|
but can not identify the NumberWidget
|
|
2018-04-11 15:30:03
|
<CFisch_WMDE>
|
because the js for it is not present
|
|
2018-04-11 15:30:05
|
<addshore>
|
Hi Csisc! What's the problem?
|
|
2018-04-11 15:30:48
|
<CFisch_WMDE>
|
if you include the https://doc.wikimedia.org/oojs-ui/master/demos/dist/oojs-ui-widgets.js on the php demo page infusion should work for the number widget
|
|
2018-04-11 15:30:51
|
<CFisch_WMDE>
|
( I hope )
|
|
2018-04-11 15:31:30
|
<Csisc>
|
When I wrote Import Pywikibot in Python a text in red had appeared
|
|
2018-04-11 15:31:50
|
<mainframe98>
|
CFisch_WMDE: I'll try that, thanks
|
|
2018-04-11 15:32:07
|
<CFisch_WMDE>
|
:-)
|
|
2018-04-11 15:33:50
|
<mainframe98>
|
CFisch_WMDE: Currently it looks hideous, but it works, thank you!
|
|
2018-04-11 15:34:13
|
<mainframe98>
|
There's still some bugs to fix, but the infusion works at least
|
|
2018-04-11 15:34:31
|
<addshore>
|
Csisc: what did it say?
|
|
2018-04-11 15:37:43
|
<Csisc>
|
I made user-config py
|
|
2018-04-11 15:37:56
|
<Csisc>
|
After, I installed Pywikibot
|
|
2018-04-11 15:38:43
|
<Csisc>
|
When I runned an algorithm using Pywikibot, a text in red has appeared.
|
|
2018-04-11 15:41:38
|
<CFisch_WMDE>
|
mainframe98: You're welcome!
|
|
2018-04-11 15:45:55
|
<addshore>
|
Csisc: what did the text say? :)
|
|
2018-04-11 15:46:49
|
<Csisc>
|
Pywikibot does not work. I should verify user-config...
|
|
2018-04-11 15:47:14
|
<Csisc>
|
...or the connection
|
|
2018-04-11 15:47:33
|
<addshore>
|
hmmm
|
|
2018-04-11 15:47:50
|
<addshore>
|
What is in your user-config (without the sensitive bits)
|
|
2018-04-11 15:48:45
|
<Csisc>
|
Wikidata.wikidata Csisc and my password
|
|
2018-04-11 15:49:45
|
<Csisc>
|
Csisc is my username
|
|
2018-04-11 15:50:49
|
<addshore>
|
What are you calling when you get the error?
|
|
2018-04-11 15:50:52
|
<addshore>
|
can you paste your code?
|
|
2018-04-11 15:51:23
|
<Csisc>
|
Import Pywikibot
|
|
2018-04-11 15:51:38
|
<Csisc>
|
Just that.
|
|
2018-04-11 15:51:39
|
<addshore>
|
Well, so that should probably be "import pywikibot"
|
|
2018-04-11 15:51:50
|
<addshore>
|
have you followed https://www.mediawiki.org/wiki/Manual:Pywikibot/Wikidata /
|
|
2018-04-11 15:51:51
|
<addshore>
|
?
|
|
2018-04-11 15:52:29
|
<addshore>
|
Did you set your username in the user-config.py as a unicode string?
|
|
2018-04-11 15:52:39
|
<addshore>
|
(the u before the string in) usernames['wikidata']['wikidata'] = u'YourBot'
|
|
2018-04-11 15:53:41
|
<Csisc>
|
Yes
|
|
2018-04-11 15:58:51
|
<addshore>
|
Can I see a copy of the script that you are trying to run?
|
|
2018-04-11 15:58:53
|
<Csisc>
|
I think that I should contact you by email as the meeting is closing now
|
|
2018-04-11 15:59:07
|
<addshore>
|
indeed, however I might not be the best person for pywikibot issues
|
|
2018-04-11 15:59:15
|
<addshore>
|
perhaps you should join #pywikibot and ask in there :)
|
|
2018-04-11 15:59:21
|
<addshore>
|
Otherwise there is also a pywikibot mailing list
|
|
2018-04-11 15:59:44
|
<Csisc>
|
I will do that. Thank you.
|
|
2018-04-11 15:59:54
|
<Csisc>
|
Good Bye.
|
|
2018-04-11 15:59:56
|
<addshore>
|
o/
|
|
2018-04-11 16:00:07
|
<addshore>
|
And that concludes this weeks IRC technical advice meeting session office hour!
|
|
2018-04-11 16:00:16
|
<addshore>
|
Thanks for coming all [=
|
|
2018-04-11 21:43:46
|
<mooeypoo>
|
bd808: meh, vagrant provision failed again -- same way it failed initially a few weeks ago, it just froze in the middle. The initial set up was finally done, at home, with my internet running properly, and then it went through provisioning, and then died at some point... I thought I was hallucinating, so I tried vagrant ssh -- but that timed out, so the machine is clearly dead.
|
|
2018-04-11 21:43:54
|
<mooeypoo>
|
bd808: help me oh vagrant whisperer
|
|
2018-04-11 22:30:35
|
<bd808>
|
mooeypoo: :( -- why does Vagrant fight you so badly?
|
|
2018-04-11 22:31:11
|
<HunterH>
|
Is this the channel for code review during open office hours?
|
|
2018-04-11 22:31:57
|
<mooeypoo>
|
bd808: no idea, but I removed 'visualeditor' role and am retrying provisioning now
|
|
2018-04-11 22:32:19
|
<mooeypoo>
|
I've crossed fingers and toes, and am awaiting Vagrant judgment
|
|
2018-04-11 22:32:59
|
<mooeypoo>
|
bd808: I also ssh'ed in, and am watching 'top' just to see if things crap out
|
|
2018-04-11 22:33:10
|
<HunterH>
|
have you tried `vagrant git-update`
|
|
2018-04-11 22:33:26
|
<bd808>
|
mooeypoo: setting the PUPPET_DEBUG=1 environment variable can help spot why it suddenly gets stuck sometimes. Usually its a git clone or an apt-get install.
|
|
2018-04-11 22:33:52
|
<mooeypoo>
|
HunterH: the initial bare-bones 'just cloned mw-vagrant' failed, so I don't think vagrant git-update would help here? Doesn't that just re-pull vagrant itself + all extension repos?
|
|
2018-04-11 22:33:53
|
<bd808>
|
something like `PUPPET_DEBUG=1 vagrant provision`
|
|
2018-04-11 22:34:01
|
<mooeypoo>
|
I don't have extensions yet, I removed them all
|
|
2018-04-11 22:34:23
|
<bd808>
|
there was some instability with gerrit access yesterday too
|
|
2018-04-11 22:34:31
|
<mooeypoo>
|
bd808: I have, prepared, this command in case it fails again: VAGRANT_LOG=debug PUPPET_DEBUG=1 vagrant provision 2>&1 | tee provision-4-11-2018.log
|
|
2018-04-11 22:34:35
|
<mooeypoo>
|
That should do it
|
|
2018-04-11 22:34:41
|
<HunterH>
|
mooeypoo: I see. I was having some issues with VisualEditor and the update fixed it.
|
|
2018-04-11 22:34:47
|
<mooeypoo>
|
I tweaked your command bd808 :P
|
|
2018-04-11 22:35:00
|
<bd808>
|
mooeypoo: nice. that should give us something to look at for sure
|
|
2018-04-11 22:36:00
|
<bd808>
|
HunterH: to your code review question, I'm not sure if twentyafterfour and other folks are still holding the office hour for that or not.
|
|
2018-04-11 22:36:09
|
<mooeypoo>
|
aaaand it is hanging
|
|
2018-04-11 22:36:12
|
<mooeypoo>
|
ok, time for the big guns
|
|
2018-04-11 22:36:57
|
<bd808>
|
HunterH: But this is generally a good channel to ask for help in. Not always quick for answers, but generally somebody will take a shot at helping at some point
|
|
2018-04-11 22:37:48
|
<HunterH>
|
bd808: I think the next office hour is tomorrow at 20:00 UTC. I haven't sat in for one yet and was just checking out the #wikimedia-codereview channel to make sure i was in the right place.
|
|
2018-04-11 22:40:48
|
<bawolff>
|
Are we doing those again?
|
|
2018-04-11 22:42:07
|
<bd808>
|
volunteers bawolff to review all the codez
|
|
2018-04-11 22:42:34
|
<bawolff>
|
[Oprah voice] Everyone gets a +2
|
|
2018-04-11 22:47:16
|
<mooeypoo>
|
https://www.irccloud.com/pastebin/uPhiAYZs/
|
|
2018-04-11 22:47:26
|
<mooeypoo>
|
... that was stupid, irccloud
|
|
2018-04-11 22:47:40
|
<mooeypoo>
|
bd808: vagrant seemed to die again. The top thread i see in "top" in vagrant ssh is
|
|
2018-04-11 22:47:40
|
<mooeypoo>
|
/usr/bin/node /vagrant/srv/changeprop/node_modules/service-runner/service-runner.js -c /vagrant/srv/changeprop/config.vagrant.yaml
|
|
2018-04-11 22:47:42
|
<mooeypoo>
|
vagrant provision is continuing to send ssh keep-alive, but "top" in vagrant ssh isn't moving, and 'vagrant ssh' in another tab craps out with 'connection reset by peer'. I assume it's dead.
|
|
2018-04-11 22:47:53
|
<mooeypoo>
|
I do have a log file...
|
|
2018-04-11 22:49:04
|
<bd808>
|
changeprop running would be "normal" once it is provisioned. that shouldn't be blocking things however.
|
|
2018-04-11 22:49:31
|
<bd808>
|
dig in the log file for the last thing that Puppet was trying to do
|
|
2018-04-11 22:50:20
|
<bd808>
|
that might be easier without the `VAGRANT_LOG=debug` bits. That is mostly useful for debugging early failures in getting the VM created
|
|
2018-04-11 22:51:53
|
<mooeypoo>
|
bd808: last few lines (before a barrage of ssh 'keep alive') from that log:
|
|
2018-04-11 22:51:56
|
<mooeypoo>
|
https://www.irccloud.com/pastebin/LL5m3gBv/
|
|
2018-04-11 22:52:12
|
<mooeypoo>
|
so, it seems like git clone?
|
|
2018-04-11 22:52:18
|
<bd808>
|
looks like it
|
|
2018-04-11 22:52:23
|
<mooeypoo>
|
is it an internet problem again!?
|
|
2018-04-11 22:52:33
|
<mooeypoo>
|
OMG I'M GOING HOME
|
|
2018-04-11 22:52:39
|
<mooeypoo>
|
Where I have actual internet!
|
|
2018-04-11 22:53:03
|
<bd808>
|
clones practically instantly from my house :)
|
|
2018-04-11 22:53:11
|
<mooeypoo>
|
But why would vagrant *freeze*
|
|
2018-04-11 22:53:20
|
<mooeypoo>
|
the machine froze completely
|
|
2018-04-11 22:53:25
|
<mooeypoo>
|
it can't be just the connection
|
|
2018-04-11 22:53:31
|
<bd808>
|
that sounds more dire
|
|
2018-04-11 22:53:53
|
<bd808>
|
like kernel instability or a problem with VirtualBox
|
|
2018-04-11 22:53:59
|
<mutante>
|
do you have 2 VMs running at the same time by any chance?
|
|
2018-04-11 22:54:00
|
<mooeypoo>
|
:\
|
|
2018-04-11 22:54:11
|
<mooeypoo>
|
I don't right now. I had once before, but not now
|
|
2018-04-11 22:54:14
|
<bd808>
|
mooeypoo: just for giggles, have you tried running with the LXC driver?
|
|
2018-04-11 22:54:15
|
<mutante>
|
i see that as a response to somebody talking about vagrant freezing and ssh
|
|
2018-04-11 22:54:19
|
<mutante>
|
that's why i asked
|
|
2018-04-11 22:54:27
|
<mooeypoo>
|
I have another vagrant box for another thing but it's not up
|
|
2018-04-11 22:54:34
|
<mooeypoo>
|
Should I remove it completely? :\
|
|
2018-04-11 22:54:59
|
<mooeypoo>
|
I either run this vagrant or the other, never at the same time, especially during provisioning
|
|
2018-04-11 22:55:04
|
<mutante>
|
You can check if you have 2 machines running with vagrant global-status. That causes terminal when in ssh to freeze.
|
|
2018-04-11 22:55:06
|
<bd808>
|
for what it's worth I run 3-4 VirtualBox VMs on my mac at the same time. Only problem is when all my cpu cores get busy
|
|
2018-04-11 22:55:44
|
<mooeypoo>
|
I have a couple there that are no longer in existence, but they're all "poweroff" except for the mediawiki vagrant
|
|
2018-04-11 22:56:31
|
<mooeypoo>
|
Should I reinstall virtualbox?
|
|
2018-04-11 22:56:39
|
<mooeypoo>
|
You know this whole started when I upgraded the guest OS :\
|
|
2018-04-11 22:57:10
|
<mooeypoo>
|
But since then, I multiple times deleted everything, and re-cloned mw-vagrant to start from scratch
|
|
2018-04-11 22:57:15
|
<bd808>
|
you had lots of the lockup problems with the older Jessie base image too though right?
|
|
2018-04-11 22:57:27
|
<bd808>
|
the bug where it would hang mid boot
|
|
2018-04-11 22:57:32
|
<mooeypoo>
|
I just had intermittent ssh issue there
|
|
2018-04-11 22:57:43
|
<mooeypoo>
|
For the most part, it works decently
|
|
2018-04-11 22:58:04
|
<mooeypoo>
|
I upgraded because we were working on a kartotherian puppet role and it wouldn't run with the old OS
|
|
2018-04-11 22:58:31
|
<mooeypoo>
|
And then it started crapping out every 10 minutes, dying randomly, and not provisioning
|
|
2018-04-11 22:58:44
|
<bd808>
|
I think it might be worth trying to run as an LXC container. The basic instructions are in support/README-lxc.md
|
|
2018-04-11 22:58:46
|
<mutante>
|
why not try the reinstall. i dont know why but askubuntu.com also has that "Re-install virtualbox-dkms package first"
|
|
2018-04-11 22:59:01
|
<mooeypoo>
|
The "crapping out every 10 minutes" was a problem with parsoid not finding crap in its node_modules folder; an 'npm install' solved it
|
|
2018-04-11 22:59:10
|
<mooeypoo>
|
ok, i shall try
|
|
2018-04-11 22:59:15
|
<bd808>
|
If I was on a linux host I would personally use LXC over VirtualBox
|
|
2018-04-11 22:59:15
|
<mooeypoo>
|
At this point, I'll try anything
|
|
2018-04-11 22:59:51
|
<mooeypoo>
|
who-ta-whatta?
|
|
2018-04-11 22:59:54
|
<bd808>
|
node.js is the root of much evil. maybe not as much at RoR, but close ;)
|
|
2018-04-11 23:01:49
|
<mooeypoo>
|
ok I have virtualbox 5.2 installed
|
|
2018-04-11 23:01:53
|
<mooeypoo>
|
should I remove and reinstall it? :\
|
|
2018-04-11 23:03:41
|
<bd808>
|
mooeypoo: if you are going to blow another evening on this, try getting the LXC setup to work instead. If you get it running correctly it will perform better than virtualbox
|
|
2018-04-11 23:04:32
|
<mooeypoo>
|
I would rather not blow any evenings on this, but I can't work without this running :\
|
|
2018-04-11 23:04:34
|
<bd808>
|
the ubuntu instructions we have are for old Trusty boxes, but you should be able to google up "vagrant lxc" setup instructions for your newer version
|
|
2018-04-11 23:05:18
|
<bd808>
|
the LXC runtime is what we use for the MediaWiki-Vagrant role on Cloud VPS hosts
|
|
2018-04-11 23:05:48
|
<mooeypoo>
|
do you have a link to instructions on how to install that?
|
|
2018-04-11 23:05:52
|
<bd808>
|
basic instructions are in support/README-lxc.md of the mediawiki-vagrant repo
|
|
2018-04-11 23:06:01
|
<mooeypoo>
|
ooh
|
|
2018-04-11 23:06:20
|
<bd808>
|
you might find more help at https://github.com/fgrehm/vagrant-lxc too
|
|
2018-04-11 23:06:50
|
<mooeypoo>
|
I don't need to uninstall virtualbox do I?
|
|
2018-04-11 23:06:55
|
<bd808>
|
nope
|
|
2018-04-11 23:07:00
|
<mooeypoo>
|
just checking
|
|
2018-04-11 23:07:19
|
<mooeypoo>
|
at this point, seriously, I'm considering dancing around my computer with incense and chanting binary
|
|
2018-04-11 23:07:33
|
<bd808>
|
000111
|
|
2018-04-11 23:08:31
|
<bd808>
|
mooeypoo: I'm going to wander away from my laptop for a while. ping me if you get stuck
|
|
2018-04-11 23:27:33
|
<mooeypoo>
|
bd808: ok, I installed lxc and ran 'vagrant up' and I get this:
|
|
2018-04-11 23:27:43
|
<mooeypoo>
|
https://www.irccloud.com/pastebin/qrOxpAG7/
|
|
2018-04-11 23:27:57
|
<mooeypoo>
|
There's nothing using port 8080 in my machine... why is it saying it's taken :\
|
|
2018-04-11 23:29:11
|
<paladox>
|
I always do netstat -tuln | grep ":8080"
|
|
2018-04-11 23:29:14
|
<paladox>
|
mooeypoo ^^
|
|
2018-04-11 23:31:17
|
<mooeypoo>
|
paladox: no result
|
|
2018-04-11 23:31:22
|
<paladox>
|
oh
|
|
2018-04-11 23:31:25
|
<mutante>
|
if you add 'p' to that it also tells you which program is running it
|
|
2018-04-11 23:31:34
|
<mooeypoo>
|
sure, but nothing is using 8080
|
|
2018-04-11 23:32:13
|
<paladox>
|
https://stackoverflow.com/questions/10953070/how-to-debug-vagrant-cannot-forward-the-specified-ports-on-this-vm-message
|
|
2018-04-11 23:32:17
|
<paladox>
|
mooeypoo ^^
|
|
2018-04-11 23:32:30
|
<mutante>
|
on the host machine, not the guest machine, right
|
|
2018-04-11 23:32:41
|
<mooeypoo>
|
You know, guys
|
|
2018-04-11 23:33:02
|
<mutante>
|
oh, wait, it's not 8080
|
|
2018-04-11 23:33:04
|
<mooeypoo>
|
if this is what volunteers run into when they're trying to set up our dev environment, we are screwed even before retention
|
|
2018-04-11 23:33:09
|
<mutante>
|
it's "The forwarded port TO 8080"
|
|
2018-04-11 23:33:19
|
<mutante>
|
To fix this, modify your current project's Vagrantfile to use another
|
|
2018-04-11 23:33:20
|
<mutante>
|
port. Example, where '1234' would be replaced by a unique host port:
|
|
2018-04-11 23:33:20
|
<mutante>
|
config.vm.network :forwarded_port, guest: 8080, host: 1234
|
|
2018-04-11 23:33:22
|
<mooeypoo>
|
huh? so what's the forwarded port?
|
|
2018-04-11 23:33:26
|
<mutante>
|
so it's the 1234 part in that example above
|
|
2018-04-11 23:33:32
|
<mooeypoo>
|
yeah but -- oh
|
|
2018-04-11 23:33:41
|
<mutante>
|
8080 on guest to 1234 on host
|
|
2018-04-11 23:33:45
|
<mutante>
|
and 1234 on host already used
|
|
2018-04-11 23:33:45
|
<mooeypoo>
|
... doesn't that do that automatically? :\
|
|
2018-04-11 23:33:45
|
<mutante>
|
afaict
|
|
2018-04-11 23:33:55
|
<mutante>
|
"Sometimes, Vagrant will attempt to auto-correct this for you. In this
|
|
2018-04-11 23:33:56
|
<mutante>
|
case, Vagrant was unable to."
|
|
2018-04-11 23:34:09
|
<Sveta_>
|
i'd be excited if #mediawiki-vagrant actually existed
|
|
2018-04-11 23:34:19
|
<paladox>
|
lol
|
|
2018-04-11 23:34:41
|
<paladox>
|
You have to set a config for vagrant to do it automatically
|
|
2018-04-11 23:34:54
|
<mutante>
|
This is usually because the guest machine
|
|
2018-04-11 23:34:54
|
<mutante>
|
is in a state which doesn't allow modifying port forwarding. You could
|
|
2018-04-11 23:34:54
|
<mutante>
|
try 'vagrant reload' (equivalent of running a halt followed by an up)
|
|
2018-04-11 23:34:54
|
<mutante>
|
so vagrant can attempt to auto-correct this upon booting. Be warned
|
|
2018-04-11 23:35:03
|
<mutante>
|
that any unsaved work might be lost.
|
|
2018-04-11 23:35:10
|
<mooeypoo>
|
grr
|
|
2018-04-11 23:35:38
|
<mooeypoo>
|
config.vm.network :forwarded_port, guest: 8080, host: 1234 <-- this should be in the Vagrantfile, right?
|
|
2018-04-11 23:35:47
|
<paladox>
|
yep
|
|
2018-04-11 23:35:58
|
<paladox>
|
mooeypoo search the file for port 8080
|
|
2018-04-11 23:36:05
|
<paladox>
|
it should find the correct line
|
|
2018-04-11 23:37:20
|
<mooeypoo>
|
I put it under the override for lxc
|
|
2018-04-11 23:38:27
|
<mooeypoo>
|
GUYS. HOLD YOUR BREATH -- it's working
|
|
2018-04-11 23:38:37
|
<mooeypoo>
|
It's loading facts!
|
|
2018-04-11 23:38:44
|
<mooeypoo>
|
IT IS PROVISIONING
|
|
2018-04-11 23:39:00
|
<mooeypoo>
|
please don't get stuck please don't get stuck please don't get stuck
|
|
2018-04-11 23:39:08
|
<mooeypoo>
|
is going to let it run
|
|
2018-04-11 23:39:09
|
<paladox>
|
lol
|
|
2018-04-11 23:39:52
|
<mooeypoo>
|
OK I'll take this time to take a coffee break
|
|
2018-04-11 23:40:01
|
<mooeypoo>
|
... wish me luck as I leave vagrant to its own devices
|
|
2018-04-11 23:45:21
|
<mutante>
|
hehe, nice. good luck
|
|
2018-04-11 23:57:01
|
<mooeypoo>
|
omg it finished without errors
|
|
2018-04-11 23:57:14
|
<mooeypoo>
|
I'm going to cry
|
|
2018-04-11 23:57:23
|
<mooeypoo>
|
It's running... fast!
|
|
2018-04-11 23:57:37
|
<mooeypoo>
|
ok. so. now.... roles.
|
|
2018-04-11 23:57:41
|
<mooeypoo>
|
<ominous music>
|