Beside copyright bot /copypatrol /plagia bot - all jobs of the bot were moved to new toolforge-jobs .
I think we can close this ticket and mark it as complete?

Seems like the session expired. Should be solved now.

I think it is more proper from technical perspective to create a separate bot account than using EranBot for a bot dedicated for copyvio to help with separation of concerns.

@Rentier just added @MPGuy2824 . I'm marking this request as complete.

Thank you for your help keeping the tool working! I have sent a request to Rentier and asked him to add you as a co-maintainer for the original tool. If he is OK to add you as a co-maintiner this it seems to be the easiest way to do so.

Candidate fix https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cite/+/876285

I think it is already implemented in ext.cite.style. Here is a snippet to prove it.

Seems to be an issue with CXTextSelectionContextItem

Some people in hewiki report on exception in VE of HttpException from Rest: https://he.wikipedia.org/wiki/%D7%95%D7%99%D7%A7%D7%99%D7%A4%D7%93%D7%99%D7%94:%D7%93%D7%9C%D7%A4%D7%A7_%D7%99%D7%99%D7%A2%D7%95%D7%A5#%D7%AA%D7%A7%D7%9C%D7%94_%D7%A2%D7%9D_%D7%94%D7%AA%D7%A8%D7%90%D7%AA_%22%D7%A0%D7%AA%D7%A4%D7%A1_%D7%97%D7%A8%D7%99%D7%92%22

My current speculation:

• VE perspective:

'restbaseUrl' => $useRestbase ? $coreConfig->get( 'VisualEditorRestbaseURL' ) : false,
'fullRestbaseUrl' => $useRestbase ? $coreConfig->get( 'VisualEditorFullRestbaseURL' ) : false,

so I think useRestbase became from true to false resulting in false. (in VE code)

• Cite perspective: (modules/ve/ve.ui.CitoidInspector.js)

this.fullRestbaseUrl = mw.config.get( 'wgCitoidConfig' ).fullRestbaseUrl ||
	mw.config.get( 'wgVisualEditorConfig' ).fullRestbaseUrl;

I think we relay on the fallback of VE which is not valid. (e.g wgCitoidConfig seems to be invalid in both hewiki and enwiki).

Added a workaround now in https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%93%D7%99%D7%94_%D7%95%D7%99%D7%A7%D7%99:Common.js&diff=35257951&oldid=34496488

I restored the bot credentials for eranbot tool

I forgot to update that with help of Mark from Turnitin we got the account reactivate for another year. Thanks for Turnitin for quickly helping with this.

I tried to login to ithenticate , and confirmed the observation:

I'm in process of slowly migrating from cron jobs to tool forge jobs framework.

In T306888#7886158, @MusikAnimal wrote:

Another thing that just occurred to me is EranBot has several other tasks than just "plagiabot"! @eranroz, I'm happy to copy over the cron jobs (or k8s scheduled jobs equivalents, if we end up going that route) as they are written now, but I'm not sure what all of the hewiki and "report on rewrite articles" scripts are supposed to do. This begs the question... with such broad and multi-team interest in the plagiabot task, would it make sense to move it to the copypatrol Toolforge account? That way everything CopyPatrol-related would live under the same roof. Unless I'm missing anything, there's no technical reason to keep it under eranbot.

I restored the session for the bot user so it should not promote for a password now

I forgot about this. thanks for the reminder. Addressed good comment from matmarex in the review

This also applies to wikidata.

I think there is a risk for copyright violation to copy coordinates from google maps.
Suggesting to reject this ticket or consider the copyright side before going to implement that (there are probably other databases for which it is valid)

I am not able to reproduce this issue. Mohammed can you please specify specific gadget/script that required to get it reproduce?

I can't reproduce the issue anymore.
Seems like introduction of unicode-bidi: isolate or similar changes in other tasks fixed this issue already

I find the code of quick preview to be quite messy. The above patch just trying to do minor refactor to make the code cleaner before actually touching it and improving the diff part

Ref supports dir parameter since T15673 but we didn't expose it to VE

I'm asking for alignment. I think we already have direction support in VE - under language selection (my last screenshot).

• I believe yes - there is special RTL version for example in skins.minerva.content.styles.images but not in skins.minerva.icons.page.issues.uncolored as far as I see.
• I believe it is generally low priority.

This is discussed in hewiki village pump: https://he.wikipedia.org/w/index.php?title=%D7%95%D7%99%D7%A7%D7%99%D7%A4%D7%93%D7%99%D7%94:%D7%9E%D7%96%D7%A0%D7%95%D7%9F&oldid=31292360#%D7%94%D7%A2%D7%95%D7%A8%D7%9A_%D7%94%D7%97%D7%96%D7%95%D7%AA%D7%99_%D7%9C%D7%90_%D7%A2%D7%95%D7%91%D7%93_%D7%A2%D7%9D_{{%D7%94%D7%A2%D7%A8%D7%94%7C...}}

I have minor concern about different libraries bheavior (MySQLdb vs oursql) and what exact version is used in the server and I wanted to run it experimentally/test it before actually merging. Please go ahead and give it a try - if we see it works well we can merge it. and thanks for helping to improve the tool!

@JJMC89 good catch - thank you for the pull request - I've merged that and we shall see how this affects the bot stability.

it seems like I missed important setting that is required to fail here: "Show previews without reloading the page"

In T256501#6585457, @MusikAnimal wrote:

My next idea is to automatically restart the bot after every N hours. Very cheap, and this would cause brief periods of downtime from when the bot dies and starts back up, but it still seems better than the status-quo.

Turnitin helped me to get the bot back to work and it should start to work now

In T256501#6513207, @MusikAnimal wrote:

In T256501#6511243, @eranroz wrote:

Following a recent change all users where forced to logout - https://lists.wikimedia.org/pipermail/wikitech-l/2020-October/093922.html
I had to relogin to set the session again - it should start to work soon

That needed to be done too, for sure, but as Dianna says it appears we are still having issues with iThenticate. The error message suggests it's the same issue as T205917. Did you get an email from Turnitin?

Following a recent change all users where forced to logout - https://lists.wikimedia.org/pipermail/wikitech-l/2020-October/093922.html
I had to relogin to set the session again - it should start to work soon

it runs monthly with cronjob from toolserver - probably the session expired. Lunching now manually the default gadgets,

For {{formatnum:1,234}} it gives warning tracking category, so to preserve the old behavior editors would need to start with reverse format, followed by formatting e,: {{formatnum::{{{x}}|}} -> {{formatnum:{{formatnum:{{{x}}|R}}}} ?

It is desirable when there are trolls using ISPs which use CGN (maybe other cases) - I think this is quite rare case - but when it is required it's important to have that.

I can modify the bot to give some indication on the last titles/edits requests to turnin, or the last turnin response.
Just let me know what would be easiest to monitor

Similar to Amir, I have no much experience with Django, but css janus works pretty good in many cases.
Just as a good practice, it is good to keep in mind to avoid using inline styles that are LTR/RTL specific (such as style="text-align:left;") but to prefer id/class to make it easier to define it in clean CSS than can be adapted to RTL friendly

Thanks - I already stole the fix from VE into the gadget.

it's disappointing that JS API that was just exposing the PHP API (part of it) and that is used used by Wikibase itself, isn't available anymore for other consumers :-(
Anyway it seems like JS consumers of wikibase should not relay on that anymore and should use re-implement it themselves or directly access using MW API for now.

@Ladsgroup @daniel I would like to understand what is the approach we would like to go for the long run:

• Do we want to have JS api for other extensions (the current and future use cases I can think of are Content translation such as T249458 and Client_editing_input) and for gadgets?
• Do we want to have bare light API without JS wrapping? in which case, when do Wikibase plan to adapt to this approach? (rm RepoApi and change all the uses)

In T259211#6347466, @Ladsgroup wrote:

but in the mean time you can still mark jquery.wikibase.linkitem as the dependency instead and use the global variable but I don't recommend it.

• Wikidata (wikidata client only) and communities (frwiki, hewiki, ruwiki) code is misaligned by removing JS API interface to wikidata that is used by gadgets -> functionality broken -> regression. to get it resolved we need to re-align them
  • communities code can adapt to new API-less wikidata (develop their own wrappers to API)
  • wikidata code can return removed code
  • (or anything in between)

I don't find RepoApi as bad module - it get in the constructor the repository - repository could be Wikidata, or Commons or other Wikibase site.

Probably regression following T256054
Doesn't it appear in error logs of RM in the server side?

restarted the session, should work now.

i reinitialize the credentials - should solve that

There is a fix in the frontend, but this bug still exists in the backend.

(yet another example)
I want to fix https://he.wikipedia.org/wiki/Module:Infobox_gene to use getEntity instead of getEntityObject which is legacy alias, it is cloned from https://en.wikipedia.org/wiki/Module:Infobox_gene which is protected.
What is the best way to achieve it?

1. Ask sysop permissions /templateeditor permissions in enwiki, fix it there, port it back to hewiki, hope that 20 other wikis will update their forks as well?
2. Update hewiki and let enwiki pull back the changes, ope that 20 other wikis will update their forks as well?
3. Split the module to logic that is common to all wikis, put it in shared repo, and fix it there

@Krinkle @hoo - digging further in wikibase source - the module registeration in Wikibase uses packageFiles and callback which I'm not that familiar with.
Anyhow the callback function getSiteConfiguration in ClientHooks.php of wikibase uses cache... Do you have any suggestion what could explain it?

I suggest we adopt approach similar to Lua modules - for example: https://en.wikipedia.org/wiki/Module:Message_box is Lua page, and https://en.wikipedia.org/wiki/Module:Message_box/doc is a wikitext page describing it or allowing users to nominate it for deletion.
Each dataset will have (optionally) a description page allowing to add categorization, additional information in non machine readable-wikitext format.