Fork me on GitHub

Wikimedia IRC logs browser - #wikimedia-tech

Filter:
Start date
End date

Displaying 211 items:

2019-06-26 12:43:38 <kwj2772_> server connections too slow nowadays :( what's the matter?
2019-06-26 12:46:29 <Reedy> you'll have to give more information than that....
2019-06-26 12:46:30 <Reedy> https://wikitech.wikimedia.org/wiki/Reporting_a_connectivity_issue
2019-06-26 14:00:27 <wm-bot> Technical Advice IRC meeting starting in 60 minutes in channel #wikimedia-tech, hosts: @chiborg & @milimetric - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
2019-06-26 14:50:11 <wm-bot> Technical Advice IRC meeting starting in 10 minutes in channel #wikimedia-tech, hosts: @chiborg & @milimetric - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
2019-06-26 15:00:14 <milimetric> hi everyone
2019-06-26 15:00:17 <milimetric> welcome to tech advice
2019-06-26 15:00:27 <simnalamburt> Hi
2019-06-26 15:00:31 <chiborg> Welcome to the Technical Advice IRC meeting! I'm here for your questions.
2019-06-26 15:00:35 <milimetric> I'm Dan, feel free to ask anything and we'll try to help
2019-06-26 15:00:37 <gwiyomisaranghae> hi~
2019-06-26 15:01:10 <simnalamburt> Hi, I'm simnalamburt. Me and lens0021_ and gwiyomisaranghae are the sysadmins of https://femiwiki.com/. We have monetary issues with maintaining our wiki regarding Cassandra, which is required by RESTBase and VisualEditor extension.
2019-06-26 15:01:11 <simnalamburt> Is there any plan or ongoing work to make VisualEditor plugin to be able to function without any backend servers like RESTBase or Parsoid? Since Parsoid is completely stateless and RESTBase is nothing more than a cache layer for Parsoid, if someone manages to port Parsoid's Node.js codes into web browser compatible one, VisualEditor plugin will be able to function without any servers just like TinyMCE
2019-06-26 15:01:13 <simnalamburt> extension.
2019-06-26 15:01:15 <simnalamburt> From the point of view of an ordinary programmer who has no knowledge of the history of the MediaWiki engine, it seems possible but it'd be better if we can learn something from previous works. If there were previous failed attempt to make Parsoid serverless, we want to listen about it. Or if there's any good reason which prevents Parsoid from becoming serverless, we also want to listen about it.
2019-06-26 15:01:51 <simnalamburt> :)
2019-06-26 15:02:49 <milimetric> simnalamburt: there's a lot there but I'll try to explain what's going on
2019-06-26 15:03:00 <milimetric> so there's a big effort to move Parsoid to PHP
2019-06-26 15:03:31 <simnalamburt> Yeah I found that there's pair of same codes one in js and another one in PHP
2019-06-26 15:03:42 <milimetric> the JS one is being ported to PHP, yeah
2019-06-26 15:03:57 <milimetric> I'm not sure exactly what will happen to the RESTBase part of that architecture
2019-06-26 15:04:18 <milimetric> but you can ask the parsing team (subbu is the head of that)
2019-06-26 15:04:56 <milimetric> but I do know that you can probably swap out Cassandra for another storage solution behind RESTBase
2019-06-26 15:05:26 <milimetric> for example, we (Analytics) use Druid behind hyperswitch (a piece of RESTBase)
2019-06-26 15:05:36 <simnalamburt> We once tried to use SQLite3 instead of Cassandra, but in that case we weren't able to autoscale RESTBase servers
2019-06-26 15:05:38 <simnalamburt> Druid
2019-06-26 15:05:53 <milimetric> we do this in a separate repository to support the pageview API: https://github.com/wikimedia/analytics-aqs
2019-06-26 15:05:53 <simnalamburt> Never heard of it thanks
2019-06-26 15:06:26 <milimetric> Druid is probably not that much easier to configure than Cassandra and most likely not the right store for you. What I'm saying is that it's very easy to use different stores behind hyperswitch
2019-06-26 15:06:40 <subbu> simnalamburt, wikitext by its nature requires access to a mediawiki server (templates, config, media metadata, etc). but, in any case, we are curently porting Parsoid to PHP and once that is avaialble in a mediawiki release, you won't need to run node services.
2019-06-26 15:06:45 <milimetric> now, are you having trouble hosting nodejs services (like the routing part) or Cassandra?
2019-06-26 15:07:04 <subbu> and as milimetric said, you can use sqlite backend for restbase instead of cassandra till then.
2019-06-26 15:07:34 <simnalamburt> We have no trouble with hosting Node.js servers. But we do have trouble with hosting Cassandra because of it's relatively large minimum requirement of RAM
2019-06-26 15:07:42 <subbu> if you want to go that route, i can point you to folks who can give you more info.
2019-06-26 15:07:42 <chiborg> I have not looked at the Parsoid code, but I guess it would be much slower in the browser, when lots of links and templates are involved, since the API needs to be queried for each template and link, to expand the templates and mark links as red/blue.
2019-06-26 15:07:50 <milimetric> sqlite, mysql, anything you want really
2019-06-26 15:07:56 <milimetric> (I recommend postgres :))
2019-06-26 15:08:30 <simnalamburt> Wow is it able to replace Cassandra with MySQL?
2019-06-26 15:08:32 <subbu> looks like marko or petr aren't on this channel
2019-06-26 15:08:42 <simnalamburt> If that's possible I think that's probabily the best option for us
2019-06-26 15:08:45 <subbu> simnalamburt, i know they have sqlite as an option.
2019-06-26 15:09:03 <milimetric> simnalamburt: it's not supported out of the box, but like you can see in our example with Druid, it's very simple to implement
2019-06-26 15:09:38 <subbu> chiborg, that is correct reg. perf.
2019-06-26 15:11:14 <simnalamburt> OK maybe replacing Cassandra with MySQL might be much easier than rewriting every feature of parsoid into browser compatible js codes
2019-06-26 15:11:17 <milimetric> simnalamburt: I'll paste you some code to look at to see. So the sys/pageviews.js module uses Cassandra, and this module uses Druid: https://github.com/wikimedia/analytics-aqs/blob/master/sys/mediawiki-history-metrics.js#L19
2019-06-26 15:11:46 <milimetric> and if you look at druidUtil, it's almost all just building the queries: https://github.com/wikimedia/analytics-aqs/blob/master/lib/druidUtil.js
2019-06-26 15:12:06 <simnalamburt> Sounds promising
2019-06-26 15:12:42 <milimetric> simnalamburt: and then see, the actual interaction with druid is just a simple post: https://github.com/wikimedia/analytics-aqs/blob/master/sys/mediawiki-history-metrics.js#L502-L507
2019-06-26 15:13:06 <milimetric> you could import any datastore client code npm library, like mysql or postgres, and call out to it
2019-06-26 15:13:51 <simnalamburt> As far as I know hyperswitch is simple HTTP server framework which supports Swagger out of the box, right?
2019-06-26 15:14:01 <milimetric> yep
2019-06-26 15:14:41 <simnalamburt> Looks not that hard
2019-06-26 15:14:55 <simnalamburt> Thanks it was very helpful and precise advise for us
2019-06-26 15:15:33 <milimetric> again, I'm not sure about the Parsoid service, but yeah, seems pretty simple to me to support a different back-end. Now, that may not be worth it at all, if the port to PHP will trigger a re-architecture of the RESTBase part
2019-06-26 15:15:50 <tassu> hey, how would a sysadmin get started contributing to WMF projects?
2019-06-26 15:15:56 <simnalamburt> Haha
2019-06-26 15:16:02 <simnalamburt> To reduce server expenses
2019-06-26 15:16:13 <milimetric> simnalamburt: if I were you, I'd keep in close contact with the product teams here, to avoid duplicating effort
2019-06-26 15:16:32 <milimetric> tassu: in what way? Coding?
2019-06-26 15:17:18 <simnalamburt> milimetric: Thanks. Time is extremely limited resource for our team, we'll be sure to do that
2019-06-26 15:17:39 <tassu> Coding, configuring stuff, anything
2019-06-26 15:17:41 <subbu> simnalamburt, https://www.mediawiki.org/wiki/RESTBase/Installation says sqlite is the default
2019-06-26 15:17:58 <milimetric> simnalamburt: yeah, definitely try sqlite to start, see where that break
2019-06-26 15:18:02 <tassu> The thing is that I get my motivation seeing stuff live/actually helping someone
2019-06-26 15:18:18 <milimetric> tassu: gotcha, well, that's pretty broad :)
2019-06-26 15:18:29 <milimetric> we have dozens of projects going on
2019-06-26 15:18:42 <simnalamburt> Yes we once used sqlite as a backend, and we found that it become strange if we set up multiple instances of RESTBase behind load balancer.
2019-06-26 15:18:50 <subbu> simnalamburt, also you don't really need restbase for visualeditor .. you only need it for two scenarios (a) avoiding dirty diffs to wikitext (b) to switch between wikitext and html editing in the same editing session.
2019-06-26 15:18:57 <mszabo-wikia> subbu: actually that makes me wonder, would the PHP port of Parsoid eliminate the need to run RESTBase to enable lossless switching between visual and source editing, or would RESTBase still be required for that?
2019-06-26 15:19:34 <simnalamburt> subbu: Yeah we know that. the "to switch between wikitext and html editing in the same editing session" was kinda huge for our users including me
2019-06-26 15:19:40 <tassu> I've been running a private MW instance in my school for some time now and I'd like to use the knownledge and my general sysadmin/dev skills to help
2019-06-26 15:19:53 <subbu> mszabo-wikia, restbase will still be required for that. but eventually some of that functionality might be integrated in core but not immediately
2019-06-26 15:20:05 <subbu> simnalamburt, ah ok. :)
2019-06-26 15:20:13 <milimetric> tassu: ok, gotcha, that helps narrow it down
2019-06-26 15:20:28 <simnalamburt> Great to hear that part of parsoid and RESTBase will be integrated into core in the future
2019-06-26 15:20:29 <milimetric> tassu: so is it fair to assume you'd be less interested in like front-end JS UIs?
2019-06-26 15:21:07 <mszabo-wikia> ouch
2019-06-26 15:21:17 <tassu> I'm most interested in backend / server admin / other behind the scenes stuff
2019-06-26 15:21:41 <milimetric> ok, cool, then basically I think to help you'd mostly need to learn puppet
2019-06-26 15:21:44 <milimetric> do you know puppet already?
2019-06-26 15:22:10 <mszabo-wikia> and question two, until the PHP port is ready, what Parsoid should be used in tandem with VisualEditor? I see there is a "v0.10.0" tag in the repo from December, but there is also a "deploy-2019-06-10" branch with some extra js code changes. Is v0.10.0 expected to work with VisualEditor until the PHP port is done?
2019-06-26 15:23:47 <tassu> Not yet, however that is something I'm planning to learn in the near future
2019-06-26 15:25:16 <apergos> another area that might be of interest is the installer or mediawiki configuration
2019-06-26 15:26:43 <subbu> mszabo-wikia, we usually have releasing parsoid deb / npm packages every 6 months .. we'll probably release one more closer to the end of the port.
2019-06-26 15:27:08 <mszabo-wikia> great, thanks!
2019-06-26 15:27:40 <subbu> deploy-2019-06-10 is just a git tag for our local deployments ... if you are using git master, then you can pick whatever version has been deployed to production most recently ( https://www.mediawiki.org/wiki/Parsoid/Deployments )
2019-06-26 15:28:22 <subbu> but, barring any unforeseen circumstances, that next deb / npm release is likely going to be last release of the Parsoid/JS version.
2019-06-26 15:28:24 <milimetric> tassu: ok, so most of our server configuration and system definition is written in puppet, and kept in https://github.com/wikimedia/puppet
2019-06-26 15:29:02 <milimetric> apergos is a distinguished member of the SRE team, the one that maintains the vast majority of that repository
2019-06-26 15:29:14 <apergos> or at least a run-of-the-mill member :-D
2019-06-26 15:29:35 <tassu> millimetric: so you keep all config in Git? I definitely need that for my own servers
2019-06-26 15:29:44 <milimetric> I'm not sure what the installer is, but mediawiki configuration is how all the wikis are configured, what extensions are where, etc, and that's in this repo: https://github.com/wikimedia/operations-mediawiki-config
2019-06-26 15:29:56 <apergos> another thing being discussed is providing a replacement eventually for desktop development of mediawiki, which is currently done by a specialized setup of vagrant. the idea is to replace it by a docker image
2019-06-26 15:30:25 <milimetric> notice, for example, the files with -labs, those are settings that apply to the wikis on the beta cluster: https://github.com/wikimedia/operations-mediawiki-config/tree/master/wmf-config
2019-06-26 15:30:41 <apergos> I guess that there might be multiple images (pods w/ kubernetes) to allow setup of all the underlying services too
2019-06-26 15:31:06 <tassu> millimetric: do you have any concrete place/direction to start? I'm definitely willing to learn some new tools in the process
2019-06-26 15:31:07 <apergos> any of these might be interesting for someone of your experience as a mediawiki sysadmin
2019-06-26 15:32:05 <milimetric> tassu: I think apergos's suggestions are good, you can look at those places, I'm a lot further from that part of the tech as I work mostly on analytics infrastructure. But I definitely think learning puppet and reading through the puppet code would be a great place to start
2019-06-26 15:32:34 <tassu> Thanks! I'll have to disappear for an hour or two now
2019-06-26 15:32:36 <apergos> out of curiosity what languages are you used to working with?
2019-06-26 15:32:36 <milimetric> apergos: does SRE have tasks that are marked like "beginner friendly" or anything like that?
2019-06-26 15:32:49 <apergos> probably not, to be honest
2019-06-26 15:32:52 <milimetric> tassu: there's a tag for tasks on phabricator, our task tracker, I think it's like newcomer or something like that
2019-06-26 15:33:02 <milimetric> feel free to ping here if you're looking for work, someone will give you something
2019-06-26 15:33:12 <tassu> PHP, js, python, ruby, some others too
2019-06-26 15:33:14 <milimetric> HEY EVERYONE: we got someone who wants TO DO WORK! :)
2019-06-26 15:33:29 <tassu> But I'll be back in an hour or two
2019-06-26 15:33:30 <chiborg> https://phabricator.wikimedia.org/project/view/169/
2019-06-26 15:33:32 <milimetric> :)
2019-06-26 15:33:51 <milimetric> ah thanks chiborg, yeah tassu look at that tag, "good-first-bug"
2019-06-26 15:34:21 <milimetric> and our docs on puppet: https://wikitech.wikimedia.org/wiki/Puppet
2019-06-26 15:35:58 <apergos> great!
2019-06-26 15:39:33 <chiborg> tassu: If you want to get involved in the docker/k8s side of things, this repository might be interesting: https://gerrit.wikimedia.org/r/plugins/gitiles/releng/local-charts/
2019-06-26 16:00:50 <chiborg> Thank you for attending the Technical Advice IRC meeting!
2019-06-26 16:58:40 <tassu> chiborg, millimetric: hey, i'm back! also, is there anything like good-first-bug for mediawiki-config or puppet?
2019-06-26 17:04:24 <apergos> that good-first-bug tag is on the mediawiki-config project, well on one task but I think someone took it already
2019-06-26 17:04:44 <apergos> so we need to find someone who sort of knows what's going on in that area and can wave you towards a few things
2019-06-26 17:05:31 <tassu> do you know who that person would be?
2019-06-26 17:15:17 <tgr> mediawiki-config is backend development, not sysadmin stuff
2019-06-26 17:15:29 <tgr> if by sysadin you mean operations
2019-06-26 17:15:55 <tassu> i mean ops and configuration
2019-06-26 17:16:40 <tgr> yeah but I think apergos was talking about https://phabricator.wikimedia.org/tag/mediawiki-configuration/
2019-06-26 17:16:57 <tgr> which is the configuration management layer in MediaWiki, not actual configuration
2019-06-26 17:17:02 <apergos> yeah I meant that workboard
2019-06-26 17:17:24 <apergos> because we're talking about someone who has set up and maintained a mediawiki install so presumably has some familiarity with the config
2019-06-26 17:17:32 <apergos> plus writes php among other things
2019-06-26 17:18:48 <tgr> actual configuration changes are in https://phabricator.wikimedia.org/tag/wikimedia-site-requests/ mostly
2019-06-26 17:20:36 <tgr> I think that queue is mainly handled by Urbanecm, maybe he has ideas
2019-06-26 17:20:39 <tassu> no good-first-bugs there :/
2019-06-26 17:21:28 <Urbanecm> almost all site requests are good-first-bugs
2019-06-26 17:21:59 <hauskatze> except for the part of "SWAT" :)
2019-06-26 17:22:22 <tassu> or "Wikimedia-maintenance-script-run"?
2019-06-26 17:22:51 <Urbanecm> tassu, scripts are easy too, but just need permissions
2019-06-26 17:24:19 <Urbanecm> tassu, maybe you can review tasks that are blocked on community consensus, and if you find some change that's agreed by the community, you can make a patch for it?
2019-06-26 17:25:11 <tassu> Urbanecm, that sounds something that I could try
2019-06-26 17:25:17 <Urbanecm> cool!
2019-06-26 17:25:32 <Urbanecm> feel free to ping me here if you have any questions!
2019-06-26 17:26:56 <Urbanecm> tassu, also, T193639 seems to be ready, just noticed the answer
2019-06-26 17:26:57 <stashbot> T193639: Please add <http://data.collectienederland.nl>; to $wgCopyUploadsDomains - https://phabricator.wikimedia.org/T193639
2019-06-26 17:27:43 <tassu> I can try that one
2019-06-26 17:28:30 <Urbanecm> cool!
2019-06-26 17:29:58 <tassu> Urbanecm: my nickname on Phabricator and other wmf stuff is "Majavah", btw
2019-06-26 17:30:05 <Urbanecm> ok
2019-06-26 17:37:38 <Krenair> <Urbanecm> tassu, scripts are easy too, but just need permissions
2019-06-26 17:37:44 <Krenair> 'just' :)
2019-06-26 17:37:50 <Krenair> those need restricted/deployment level permissions
2019-06-26 17:37:58 <Urbanecm> yeah :)
2019-06-26 17:38:04 <Krenair> so are not good for new volunteers
2019-06-26 17:38:09 <Urbanecm> certainly
2019-06-26 17:38:22 <Krenair> very few volunteers get that kind of access these days - those that do have been around for a long time and are well known
2019-06-26 17:40:33 <Krenair> I agree writing the patch is something that can be done by complete newbies
2019-06-26 17:41:48 <Krenair> dealing with the SWAT process may be something best done by people with a little more experience though there's nothing to stop a brand new person from trying. could totally watch the operations channel while it happens
2019-06-26 17:42:21 <Krenair> doing actual deployments and maint script runs are restricted for pretty good reasons unfortunately
2019-06-26 17:43:00 <hauskatze> Breaking the wiki is surprisingly easy. Recovering from the break requires more than a 'git revert' sometimes :)
2019-06-26 17:44:57 <Urbanecm> Krenair, in gci 2018, i've included "choose a siterequest, upload a patch and schedule for SWAT deployment" as a task
2019-06-26 17:44:59 <Urbanecm> it worked pretty well
2019-06-26 17:46:26 <tassu> Urbanecm: that site in T193639 serves images from multiple different hosts
2019-06-26 17:46:26 <stashbot> T193639: Please add <http://data.collectienederland.nl>; to $wgCopyUploadsDomains - https://phabricator.wikimedia.org/T193639
2019-06-26 17:46:41 <tassu> for example, https://www.collectienederland.nl/search/?q=delving_spec%3A"zuiderzeemuseum"&page=1&rows=100 serves from http://images.memorix.nl
2019-06-26 17:47:12 <tassu> and https://data.collectienederland.nl/search/?q=&qf=edm_dataProvider%3ACODA+Museum&qf=edm_dataProvider%3ACODA serves from http://igem.adlibsoft.com/
2019-06-26 17:47:47 <Urbanecm> tassu, seems completing this task would require knowing which PD images they want to mass upload. Maybe ask there
2019-06-26 17:51:25 <Urbanecm> tassu, btw, i guess https://gerrit.wikimedia.org/r/c/wikimedia-cz/tracker/+/519044 is your patch, isn't it? I don't think it's a good way to just add empty td's to fix the problem. colspan attribute would be a prettier solution IMO, see https://www.w3schools.com/tags/att_td_colspan.asp.
2019-06-26 17:53:12 <Urbanecm> hauskatze, can you please have a look at https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CirrusSearch/+/518392 please?
2019-06-26 17:53:27 <hauskatze> mira
2019-06-26 17:53:43 <tassu> Urbanecmm, it is my patch. I know about the colspan but empty td's are used in multiple places across the project (for example in the line before my change), and I just went with what was used on the project to not create inconsistency. I can modify that to use colspan if you want
2019-06-26 17:54:44 <hauskatze> Urbanecm: aha, I spotted it a couple of days ago but I wasn't sure why Cindy kept -1ing the patch. I see it votes +1 now and the patch looks sane so I'll +2
2019-06-26 17:57:11 <Urbanecm> hauskatze, it voted -1 because the patch wasn't depending on the IS.php part
2019-06-26 17:59:22 <Urbanecm> tassu, I think colspan will be better. You can also modify the previous lines to use colspan, that'll be appreciated
2019-06-26 17:59:35 <tassu> yeah, I'll do that
2019-06-26 17:59:57 <Urbanecm> thank you tassu
2019-06-26 17:59:59 <hauskatze> Urbanecm: yes, I mean "Cindy-the-browser-test-bot"
2019-06-26 18:00:12 <Urbanecm> hauskatze, i know, i meant it too :)
2019-06-26 18:00:15 <hauskatze> some browser tests failed before but they're okay now
2019-06-26 18:00:26 <hauskatze> it's on the gate-and-submit queue now
2019-06-26 18:00:34 <hauskatze> lots of CI tests but it's going
2019-06-26 18:00:42 <Urbanecm> thanks hauskatze
2019-06-26 18:00:48 <hauskatze> :)
2019-06-26 18:03:14 <tassu> Urbanecm: this might be the reason the column wasn't just extended: https://i.imgur.com/F772WaJ.png
2019-06-26 18:03:49 <Urbanecm> tassu, it should be possible to extend the second column, not the first, shouldn't it?
2019-06-26 18:04:01 <tassu> yep, was just typing about suggesting that
2019-06-26 18:04:21 <Urbanecm> :)
2019-06-26 18:05:31 <tassu> Urbanecm: I still haven't figured out how can I mark expeditures as accepted or paid
2019-06-26 18:05:49 <Urbanecm> tassu, i assume you're logged in as a superuser
2019-06-26 18:05:53 <tassu> yes
2019-06-26 18:06:02 <Urbanecm> in that case, here are the steps:
2019-06-26 18:06:08 <Urbanecm> 1) open the ticket in administration
2019-06-26 18:06:18 <Urbanecm> 2) in the expeditures sections, there are "paid" checkboxes
2019-06-26 18:06:41 <Urbanecm> that's for the paid part. Regarding accepted, it's a little bit more difficult
2019-06-26 18:06:50 <Urbanecm> expeditures are marked as approved when a ticket is approved
2019-06-26 18:07:45 <Urbanecm> you can approve a ticket by opening the ticket in administration, click "add ack" in the admin interface and then add "accepted"
2019-06-26 18:08:06 <Urbanecm> if you don't want to approve 100% of expeditures, you can adjust rating percentage
2019-06-26 18:08:22 <Urbanecm> if it's 80, only 80 % of expenses will be marked as approved
2019-06-26 18:08:29 <Urbanecm> tassu, does that answer to your question?
2019-06-26 18:08:44 <tassu> it does, managed to get it working. thanks!
2019-06-26 18:08:51 <Urbanecm> happpy to help
2019-06-26 18:11:24 <tassu> Urbanecm: updated the patch!
2019-06-26 18:11:29 <Urbanecm> thank you tassu
2019-06-26 18:14:18 <Urbanecm> tassu, I've approved your patch. Thank you!
2019-06-26 18:14:38 <tassu> Happy to help!
2019-06-26 18:16:21 <Urbanecm> tassu, if you want to help Tracker more, T213173 might be an interesting choice ;)
2019-06-26 18:16:22 <stashbot> T213173: add_to_mediawiki/remove_from_mediawiki errors on files with no first section - https://phabricator.wikimedia.org/T213173
2019-06-26 18:18:56 <tassu> Urbanecm, I'll take a look!
2019-06-26 18:19:08 <Urbanecm> thanks! ping me if you have any questions!
2019-06-26 18:21:40 <Stryn> tassu: https://phabricator.wikimedia.org/T193639 is not me (Stryn), but SIryn. Yeah, I also sometimes see first it's me...
2019-06-26 18:21:50 <Stryn> actually SIryn*
2019-06-26 18:22:43 <tassu> Stryn: sorry! totally not confusing at all...
2019-06-26 18:31:56 <tassu> Urbanecm: I'm leaving for today, however I'll continue T213173 when I'll have time.
2019-06-26 18:31:56 <stashbot> T213173: add_to_mediawiki/remove_from_mediawiki errors on files with no first section - https://phabricator.wikimedia.org/T213173
2019-06-26 18:33:37 <Urbanecm> tassu|away, sure!
2019-06-26 20:23:59 <techguru_paul> I am a new volunteer for SRE tasks ... ready, willing and able to do some heavy lifting for architecture/requirements/design/refactor/observability/etc -- in the past year I have created a production k8s/docker/helm umbrella style deployment with full CI (now deployed to several Fortune 10 companies) — supporting IaaS/PaaS and SaaS components.
2019-06-26 20:26:02 <techguru_paul> > Looking for some global scale, high frequency, big data challenges

This page is generated from SQL logs, you can also download static txt files from here