Closed desb42 closed 4 years ago
Turns out, I was off by one The line in question is the following line
cfg.siteID = mw.wikibase.getGlobalSiteId()
getGlobalSiteId
does not exist in xowa (sort of)
It's a very recent addition to mw.wikibase.lua (or at least rearrangement)
Confusingly getGlobalSiteId
exists in mw.wikibase.entity.lua - and is probably why this works for xowa-gui
but when running hdump (on enwiki 2019-11-01) a few more lines in mw.wikibase.lua seems to do the trick The lines are:
function wikibase.getGlobalSiteId()
return php.getGlobalSiteId()
end
with another change to Scrib_lib_wikibase.java to expose the getGlobalSiteId() function
Thanks for the breakdown as well as the pointers.
I synchronized mw.wikibase.entity.lua
and added support for the underlying functions. Tested against the latest 2019-11 en.w Alabama
Let me know if anything else. Thanks!
In the change that I made - calling php.getGlobalSiteId() directly instead of calling php.getSetting( 'siteGlobalID' )
getGlobalSiteId within xowa calls core.Wiki().Domain_abrv() which for this wiki I believe is enwiki
As far as I can tell using php.getSetting( 'siteGlobalID' ), this will always return wikidatawiki
Nice catch! I incorrectly assumed that the getSettings
call was the same for all wikis.
Fixed in the commit above. Reference urls below.
Thanks!
getSettings
call which uses wgWBRepoSettings
: https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/lib/includes/WikibaseSettings.phpwgWBReposSettings
: https://noc.wikimedia.org/conf/highlight.php?file=Wikibase.php
I am building a few wikis from the 2019-11-01 dumps This error occurs when I try to build (hdump) enwiki - the full trace is
I am using a build of xowa from commit 8653e665cc83e936c4152446e6763d8b5f0aadc1
If I run xowa-gui or xowa-http the page
Alabama
appears (with no error) My suspicion is that there is a subtly different startup for the hdump process For this exercise I am only using one worker (so as not to get into any multithread issues)Line 162 of Module:Wd reads
however, I cannot see why this is an issue