|
2018-11-07 20:45:29
|
<Raymond_>
|
I am getting a fatal error " „UnexpectedValueException“ for https://commons.wikimedia.org/w/index.php?title=Category:Argenta_(company)&action=edit
|
|
2018-11-07 21:59:02
|
<Wim_b>
|
"[W@Nf1wpAIC0AABZ2NAYAAABI] 2018-11-07 21:57:43: Errore irreversibile di tipo "UnexpectedValueException" " <- where and how should I report an error like this?
|
|
2018-11-07 22:00:40
|
<wm-bot>
|
Technical Advice IRC meeting starting in 60 minutes in channel #wikimedia-tech, hosts: @tgr & @nuria - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
|
|
2018-11-07 22:04:38
|
<Wim_b>
|
because in it.wikt I conflict my self and this error appears every time I try to see the preview of a new page
|
|
2018-11-07 22:05:41
|
<Wim_b>
|
the conflict of edit appears also in preview (?) not when i save the page�
|
|
2018-11-07 22:08:17
|
<tgr>
|
Wim_b: https://phabricator.wikimedia.org/
|
|
2018-11-07 22:08:48
|
<tgr>
|
although since you already reported it here I can look into it
|
|
2018-11-07 22:10:16
|
<Wim_b>
|
tgr: do you want me to save this anyway on phab?
|
|
2018-11-07 22:10:19
|
<tgr>
|
Wim_b: how do you conflict yourself over a non-existing page?
|
|
2018-11-07 22:10:52
|
<Wim_b>
|
I conflict my self when I click "preview" :p
|
|
2018-11-07 22:11:07
|
<Wim_b>
|
when I save is all ok� :)
|
|
2018-11-07 22:11:17
|
<tgr>
|
nah, seems to be T205942
|
|
2018-11-07 22:11:18
|
<stashbot>
|
T205942: Some edit submits get fatal InvalidArgumentException "The title does not refer to an existing page" from TwoColConflict extension - https://phabricator.wikimedia.org/T205942
|
|
2018-11-07 22:12:27
|
<tgr>
|
I still don't get why TwoColConflict is involved in a preview, but they seem to have a patch merged
|
|
2018-11-07 22:12:32
|
<tgr>
|
just not deployed yet
|
|
2018-11-07 22:12:33
|
<Wim_b>
|
when i. click "preview" in a new page, appears the error "[W@Nf1wpAIC0AABZ2NAYAAABI] ... "UnexpectedValueException" "
|
|
2018-11-07 22:13:10
|
<tgr>
|
yeah but why is TwoColConflict even invoked there, it's supposed to run on edit conflicts
|
|
2018-11-07 22:13:30
|
<tgr>
|
anyway, looks like the relevant team is on it
|
|
2018-11-07 22:15:56
|
<Wim_b>
|
for now, I have disabled TwoColConflict to be able to use the preview and the error is gone
|
|
2018-11-07 22:16:51
|
<stwalkerster>
|
Relatedly, I clicked an edit section link on [[meta:Meta talk:Adminstrators]], and immediately get thrown into an edit conflict resolution - I've neither made a change, nor even seen the normal edit box yet
|
|
2018-11-07 22:22:00
|
<tgr>
|
there's a deployment scheduled to 12h UTC tomorrow to fix this
|
|
2018-11-07 22:22:11
|
<tgr>
|
until then, probably disabling the beta feature is best
|
|
2018-11-07 22:26:05
|
<Wim_b>
|
sure� TY :)
|
|
2018-11-07 22:50:13
|
<wm-bot>
|
Technical Advice IRC meeting starting in 10 minutes in channel #wikimedia-tech, hosts: @tgr & @nuria - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
|
|
2018-11-07 23:00:21
|
<nuria>
|
is tgr here/
|
|
2018-11-07 23:00:28
|
<nuria>
|
hola!
|
|
2018-11-07 23:00:36
|
<tgr>
|
Hi everyone!
|
|
2018-11-07 23:00:48
|
<tgr>
|
welcome to the Tech Advice meeting
|
|
2018-11-07 23:01:32
|
<tgr>
|
feel free to ask nuria and me about any topic
|
|
2018-11-07 23:01:56
|
<tgr>
|
this time, you can also ask in Spanish or Hungarian
|
|
2018-11-07 23:02:19
|
<bd808>
|
lurks
|
|
2018-11-07 23:02:44
|
<tgr>
|
a mai műszaki tanácsadáson magyarul is tudtok kérdezni
|
|
2018-11-07 23:06:18
|
<bd808>
|
I keep wondering if we are failing to advertise this once per month session well enough or if it is just at a bad time for folks with questions :/
|
|
2018-11-07 23:06:39
|
<paladox>
|
Hi, im wondering how do i debug a mw import xml file?
|
|
2018-11-07 23:06:40
|
<nuria>
|
bd808: it is very west coasty time
|
|
2018-11-07 23:06:44
|
<paladox>
|
im getting this error: https://phabricator.wikimedia.org/P7774
|
|
2018-11-07 23:06:45
|
<zchrykng>
|
This might be a stupid idea, but I was thinking about it earlier and I'm here. How much work would be required to allow users to give other users permission to edit a specific user page? Thinking for situations like working on large scripts. Alternatively, would it be possible to create a "scripts" namespace to allow collaboration on scripts. This would be nice for when users leave, are banned, or just stop maintaining their scripts. It could
|
|
2018-11-07 23:06:45
|
<zchrykng>
|
either be locked behind a new group or under template protection.
|
|
2018-11-07 23:06:48
|
<paladox>
|
(the file is 19gb)
|
|
2018-11-07 23:07:52
|
<zchrykng>
|
Sorry for the wall-o-text.
|
|
2018-11-07 23:08:25
|
<nuria>
|
zchrykng: seems that your question is about how to collaborate better with scripts?
|
|
2018-11-07 23:08:52
|
<nuria>
|
zchrykng: it is not tied per se to user pages right?
|
|
2018-11-07 23:09:05
|
<zchrykng>
|
nuria: Yeah, that is the thrust of the question. :)
|
|
2018-11-07 23:09:16
|
<bd808>
|
paladox: that "page line 65535" is suspicious. 2**N - 1 numbers always make me think of overflow/truncation problems
|
|
2018-11-07 23:09:26
|
<paladox>
|
oh ah
|
|
2018-11-07 23:09:51
|
<paladox>
|
maybe a bug in https://github.com/WikiTeam/wikiteam
|
|
2018-11-07 23:09:53
|
<nuria>
|
zchrykng: is gerrit not a good tool? that is the tool most commonly used is used for "code" collaborations
|
|
2018-11-07 23:11:02
|
<zchrykng>
|
nuria: honestly, I wasn't aware of gerrit until now. Will check it out later and get back to you.
|
|
2018-11-07 23:11:58
|
<tgr>
|
paladox: did you use XML_PARSE_BIG_LINES ?
|
|
2018-11-07 23:12:03
|
<tgr>
|
see e.g. http://php.net/manual/en/domnode.getlineno.php#113529
|
|
2018-11-07 23:12:14
|
<paladox>
|
nope
|
|
2018-11-07 23:12:26
|
<paladox>
|
does mw use that?
|
|
2018-11-07 23:12:45
|
<nuria>
|
zchrykng: ok, you need a user and password that will be different from your wiki user: https://gerrit.wikimedia.org
|
|
2018-11-07 23:13:08
|
<tgr>
|
zchrykng: in general MediaWiki tries to be pretty light on permission control
|
|
2018-11-07 23:13:14
|
<nuria>
|
zchrykng: if you are thinking of collaborating on code that the wikimedia foundation does not need to deploy github is also an option
|
|
2018-11-07 23:13:18
|
<tgr>
|
no ACLs and such
|
|
2018-11-07 23:14:07
|
<tgr>
|
so regardless of how hard it would be technically (probably not super hard) it's not likely to happen
|
|
2018-11-07 23:14:18
|
<bd808>
|
zchrykng: gerrit is the code review and git repository hosting system that Wikimedia technical contributors use for our free and open source projects. If you decide you want to try using it, there is more information at https://www.mediawiki.org/wiki/Gerrit
|
|
2018-11-07 23:15:09
|
<tgr>
|
user-owned scripts are a problem, but the solution is more likely to be 1) transitioning to community ownership or 2) moving to a system that's better suited for individual ownership and control than MediaWiki
|
|
2018-11-07 23:15:38
|
<zchrykng>
|
Yeah, totally understand. I was mainly thinking of user scripts. Is there a deployment pipeline for GitHub -> User script page? Or is it a build your own situation?
|
|
2018-11-07 23:16:18
|
<bd808>
|
I think tgr was working on something like that as a side project :)
|
|
2018-11-07 23:16:49
|
<zchrykng>
|
I was hoping for some kind of solution that would allow new editors to pick up discarded scripts without having to get everyone currently using it to notice and switch over when maintainers change.
|
|
2018-11-07 23:16:57
|
<tgr>
|
1) is part of the plan for Gadgets, except no one is actually working on Gadgets :(
|
|
2018-11-07 23:17:00
|
<tgr>
|
see https://www.mediawiki.org/wiki/Gadgets_3.0
|
|
2018-11-07 23:17:32
|
<tgr>
|
2) is a side project of mine, yeah. https://phabricator.wikimedia.org/T187749
|
|
2018-11-07 23:18:36
|
<zchrykng>
|
Okay will check those out, thanks!
|
|
2018-11-07 23:18:59
|
<tgr>
|
there is definitely interest in this, both from the security side (scripts loaded from user namespace have probably been the main vector for Wikimedia projects getting hacked) and the power contributor support side
|
|
2018-11-07 23:19:35
|
<tgr>
|
e.g. there was a bunch of discussion at the Wikimedia Technical Conference a few weeks ago
|
|
2018-11-07 23:20:01
|
<tgr>
|
but no concrete plans at this point
|
|
2018-11-07 23:20:03
|
<zchrykng>
|
Didn't figure I was the only person who thought there was problem.
|
|
2018-11-07 23:20:46
|
<tgr>
|
if you are looking for something right now, I think frwiki has a github -> MediaWiki namespace sync bot
|
|
2018-11-07 23:21:13
|
<zchrykng>
|
Any place I can sign up to hear about developments? I'm sure I can't help on the dev side, but would like to hear about discussions.
|
|
2018-11-07 23:21:52
|
<zchrykng>
|
Not doing anything complex at this point was more asking for potential future stuff.
|
|
2018-11-07 23:21:54
|
<tgr>
|
also, you can still add suggestions to the Community Wishlist until end of this week :)
|
|
2018-11-07 23:22:11
|
<zchrykng>
|
Ah, yeah. Will do that.
|
|
2018-11-07 23:22:24
|
<tgr>
|
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019
|
|
2018-11-07 23:22:39
|
<zchrykng>
|
enterprisey will vote for it at least. XD
|
|
2018-11-07 23:23:18
|
<tgr>
|
you can subscribe to the phab task, not sure what other place there is for updates
|
|
2018-11-07 23:23:57
|
<tgr>
|
T36958 is the Gadgets task
|
|
2018-11-07 23:23:58
|
<stashbot>
|
T36958: Gadgets 3.0: Implement ability to create wiki-modules at a user level - https://phabricator.wikimedia.org/T36958
|
|
2018-11-07 23:24:31
|
<tgr>
|
T187749 is the git sync task
|
|
2018-11-07 23:24:32
|
<stashbot>
|
T187749: Make it possible to use code from an external repository for editor-controlled Javascript/CSS - https://phabricator.wikimedia.org/T187749
|
|
2018-11-07 23:26:18
|
<zchrykng>
|
Thanks!
|
|
2018-11-07 23:29:05
|
<tgr>
|
paladox: https://codesearch.wmflabs.org/search/?q=XML_PARSE_BIG_LINES&i=nope&files=&repos=
|
|
2018-11-07 23:29:09
|
<tgr>
|
apparently not
|
|
2018-11-07 23:29:22
|
<paladox>
|
hmm
|
|
2018-11-07 23:29:23
|
<paladox>
|
ok
|
|
2018-11-07 23:29:30
|
<paladox>
|
i've commited a hack in our fork
|
|
2018-11-07 23:29:36
|
<paladox>
|
to increase the lines
|
|
2018-11-07 23:29:37
|
<paladox>
|
:)
|
|
2018-11-07 23:31:34
|
<enterprisey>
|
Is this the channel for the technical advice IRC meeting?
|
|
2018-11-07 23:31:40
|
<paladox>
|
yup
|
|
2018-11-07 23:32:04
|
<enterprisey>
|
Cool
|
|
2018-11-07 23:32:48
|
<enterprisey>
|
I was wondering, is there a JS function that goes from HTML elements to wikitext ranges?
|
|
2018-11-07 23:33:06
|
<nuria>
|
enterprisey: yes yes
|
|
2018-11-07 23:33:14
|
<enterprisey>
|
Whoa really
|
|
2018-11-07 23:33:21
|
<enterprisey>
|
That would be useful
|
|
2018-11-07 23:33:27
|
<nuria>
|
enterprisey: yes to "is this teh place to ASK questions"
|
|
2018-11-07 23:33:30
|
<nuria>
|
*the
|
|
2018-11-07 23:33:34
|
<enterprisey>
|
Ah I see
|
|
2018-11-07 23:33:50
|
<enterprisey>
|
I was going to write the function myself but wanted to maybe save myself a little work
|
|
2018-11-07 23:33:59
|
<nuria>
|
enterprisey: what do you mean with " wikitext ranges"
|
|
2018-11-07 23:34:10
|
<enterprisey>
|
Start and end indices
|
|
2018-11-07 23:34:40
|
<nuria>
|
enterprisey: I see, start and end indices of markup?
|
|
2018-11-07 23:34:49
|
<enterprisey>
|
E.g. if a page contains "Hi" in a div, and I call this function and pass in the div, I should get [0, 2]
|
|
2018-11-07 23:34:51
|
<enterprisey>
|
Yeah
|
|
2018-11-07 23:35:16
|
<tgr>
|
enterprisey: you mean in an editor window?
|
|
2018-11-07 23:35:17
|
<enterprisey>
|
Sorry that's wrong, just the text "Hi" without a div
|
|
2018-11-07 23:35:34
|
<enterprisey>
|
tgr: from a user script, in regular "view" mode
|
|
2018-11-07 23:36:20
|
<enterprisey>
|
I can approximate this with a Parsoid round-trip but it's inefficient
|
|
2018-11-07 23:36:26
|
<tgr>
|
so in *regular* view mode that's highly unlikely
|
|
2018-11-07 23:36:47
|
<tgr>
|
the Parsoid view contains wikitext annotations and you can probably use those to get a position
|
|
2018-11-07 23:36:56
|
<enterprisey>
|
It comes up very frequently writing a certain sort of user script
|
|
2018-11-07 23:37:01
|
<tgr>
|
...the Parsoid HTML...
|
|
2018-11-07 23:37:06
|
<enterprisey>
|
Yeah I was looking through the Parsoid docs
|
|
2018-11-07 23:37:37
|
<tgr>
|
but that HTML is not used except in a few fringe cases (e.g. when you save a VisualEditor edit but don't reload the page)
|
|
2018-11-07 23:37:41
|
<enterprisey>
|
It would be nice to be able to do this without multiple API calls, though
|
|
2018-11-07 23:38:10
|
<tgr>
|
you could replace the page content with the one from Parsoid, I guess
|
|
2018-11-07 23:38:25
|
<enterprisey>
|
Yeah, the trivial way is use Parsoid to get the annotated HTML, add "flag" elements around the target element, send it back to wikitext, and diff to find the "flags"
|
|
2018-11-07 23:40:07
|
<enterprisey>
|
And I haven't tried this in practice, but it might be tricky to recover the flags in all cases - but that's just because there are many difficult cases for this function
|
|
2018-11-07 23:41:22
|
<enterprisey_>
|
My bad
|
|
2018-11-07 23:42:15
|
<tgr>
|
Parsoid has element IDs which are probably easy to convert into positions on the server side: https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec/Element_IDs
|
|
2018-11-07 23:42:44
|
<tgr>
|
so if this use case is common enough, it should be easy to build a nicer API than adding flag elements
|
|
2018-11-07 23:42:56
|
<tgr>
|
but you'd still have to start with the Parsoid HTML
|
|
2018-11-07 23:43:07
|
<enterprisey_>
|
Yeah, agreed
|
|
2018-11-07 23:43:25
|
<enterprisey_>
|
The Element IDs look very cool, I'll look into those more
|
|
2018-11-07 23:43:25
|
<tgr>
|
I very much doubt you can do anything useful with the PHP parser output in this regard
|
|
2018-11-07 23:45:30
|
<enterprisey_>
|
Yeah, I can try working on the "nicer API", I was just wondering if it already existed
|
|
2018-11-07 23:45:36
|
<enterprisey_>
|
Thanks for the help!
|
|
2018-11-07 23:46:26
|
<tgr>
|
by nicer API I mean an endpoint which gives you a map of element ID to wikitext position or range
|
|
2018-11-07 23:46:58
|
<tgr>
|
I don't know much about the Parsoid internals but I imagine that would be trivial to create as a parsing byproduct
|
|
2018-11-07 23:47:44
|
<tgr>
|
and they are already working on splitting up the result of a parse into separate API endpoints (page HTML + page metadata) so it shouldn't be conceptually hard to add another one
|
|
2018-11-07 23:48:27
|
<tgr>
|
of course #mediawiki-parsoid is a better place for these questions
|