Legacy container-based Wikibase
See:
Legacy container-based Wikibase
See:
I have also confirmed, by creating a docker-compose.override.yml that overrides the WIKIBASE_HOST variable and re-creating both wdqs-based containers, then deleting the override and re-creating them again, that the VocabularyVersioningException only occurs while the override file is in place and sets an environment variable that is different from the initial one. As I mentioned above, this has also worked out on production in the past.
I would like to revisit this topic since we got the very same exception trace in one of our instances.
I was able to solve the error EntityId is not an interface, see https://www.mediawiki.org/wiki/Topic:X2qyoagj0mx24oey
I'm getting the same
I am getting new errors along these lines, when trying to upgrade to Mediawiki 1.38:
Thought this might be the best thread to ask on.
@Argahsuknesib I got frustrated and abandoned the platform for about a year sadly;
In T186161#6928737, @Superraptor123 wrote:@Addshore I'm confused by your link (https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_options.html#conceptBaseUri); so if I want to change the URIs from the default http://wikibase.svc/entity/Q39 to localhost:8181/entity/Q39, I do this by adding something to LocalSettings.php?
The conceptBaseUri says it is constructed from $wgServer by default, the value this has upon initialization is $wgServer = WebRequest::detectServer(); so based on the provided documentation I should just set it as $wgServer = "localhost:8181"?
Thank you!
UPDATE #1: Deleted everything to start from scratch for the fourth (or fifth?) time. I followed all of the steps and changed $wgServer = "localhost:8181" for loading in data. This actually made it so localhost:8181 stopped working in the browser, so this is (probably) not the solution.
Updater still isn't working, same stack as I posted above.
UPDATE #2: I've totally given up on this; this is an absolute nightmare just to get data from one instance to another and it seems nearly impossible to navigate. If you're in this situation, I'd just recommend giving up and either adding in everything manually or picking a different database system.
In T197868#7614475, @Lwangaman wrote:@hyperreview did you try this?
In T197868#6557406, @Lwangaman wrote:I had the same error message Error from line 35 of /var/www/mediawiki/extensions/Wikibase/lib/WikibaseLib.entitytypes.php: Class 'Wikibase\DataModel\Entity\ItemId' not found when trying to run the update.php script after an upgrade of my wiki from 1.34 to 1.35. Turns out it wasn't so much a composer problem, as it was that I simply hadn't run
git submodule update --init --recursivein the extensions/Wikibase directory. I had git cloned Wikibase from branch REL1_35, but then you need to run git submodule update in the Wikibase extension folder and then after that run composer update --no-dev.
@hyperreview did you try this?
So what is the solution?
Can you try adding something like this?
Great!
Following your advice, we use proper FQDN now instead of IP.
In particular, deleting data/data.jnl as mentioned in T207133#4681278 would wipe the blazegraph triple store, wouldn't it?
⛱ re-sent invite 🏖
I’m back from vacation now, and my invitation to the repo/org expired.
Current Docker distribution has Scribuntu included: https://github.com/wmde/wikibase-release-pipeline/tree/main/Docker/build/WikibaseBundle
I am unfortunately not savvy enough to provide a stack trace, but have the (amateurish) patch that solves the issue for Rhizome available on GitHub: https://github.com/rhizomedotorg/wikibase-docker/commit/d810a86021490b2a9aa99f476251fd4ac754bcb9 (both @Lucas_Werkmeister_WMDE and @Addshore are invited to the repo)
This does indeed look like your problem.
Thanks for checking back so quickly.
This select using an IP address looks wrong, this should be using the concept base URI for wikibase, something feels wrong with this configuration.
The wikibase-docker git repository will be going away.
This should be fixed in the newly released images etc
The wikibase-docker git repository will be going away.
I'm pretty sure this is fixed in the newly released images
They did not
The wikibase-docker git repository will be going away.
And I am assuming that this is fixed in the new images
Declining as we have no heard back about the issue in a year
This defiantly works in the new released images & build process
The wikibase-docker git repository will be going away.
Marking as resolved for now as the newer images certainly match the production properties, and 3.40 is the latest tagged version to try
Declining as no further discussion in years
Not reproduced since 2018