| Addshore added a comment. |
In T182394#3828826, @Smalyshev wrote:If on an empty wikibase install this was actually the date of the first run of the updater then everything would work as expected.
Updater does not mark its own runs if nothing was actually imported to the database.
So this is what is happening, there are no edits in recent changes (expect perhaps the default MainPage creation by mediawiki, but the updater is adding a date to blazegraph, and the date seems rather wrong.
Also, is the 30 days configurable?
No, currently it's hardcoded. But it's not hard to make it configurable if needed.
Configurable would be great, should I create a seperate ticket?
I'm still not sure what is the scenario though - what use case is this? Why DB is empty and what is supposed to happen?
So the use case is a sample docker-compose system, that creates a fresh wikibase install, installs a query service and has an updater running.
If the user sets this system up, but doesn't make an edit, and then restarts their machine the updater will suddenly break because of the bad / old date being added to blazegraph by the initial run of the updater.
I would feel bad adding a note to the readme that says something like "NOTE: on the first run you MUST make an entity or the updater will break on subsequent runs."
Cc: Smalyshev, Addshore, Aklapper, Lahi, Gq86, Lucas_Werkmeister_WMDE, GoranSMilovanovic, QZanden, EBjune, merbst, Avner, Gehel, Jonas, FloNight, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
