 | Semantic MediaWiki | 194 Members |
| SMW lets you store and query data within MediaWiki pages. Mirrored in the SMW Telegram, which you can join at https://t.me/joinchat/MCG84k3OMoaYZoFA9yhyMg | 10 Servers |
| Semantic MediaWiki | 194 Members |
| SMW lets you store and query data within MediaWiki pages. Mirrored in the SMW Telegram, which you can join at https://t.me/joinchat/MCG84k3OMoaYZoFA9yhyMg | 10 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Mar 2024 | ||
 krabina | Thank you to HMS Analytical Software for their generous donation to SMW! https://lnkd.in/dvfXiiF7 Every donation helps! https://opencollective.com/smw | 12:55:36 |
| 27 Mar 2024 | ||
 Антон changed their display name from Aнтон Курашев to Антон. | 13:34:35 | |
| 28 Mar 2024 | ||
 justinl | Hey all, I accidentally posted this in the Extensions room, copying here. When trying to create a new property (on 1.39.6) following these steps:
This gives an error: Property "TestProperty" was altered and requires assigned entities to be reevaluated using a change propagation process. The property page has been locked until the primary specification update is completed to prevent intermediary interruptions or contradictory specifications. The process may take a moment before the page can be unlocked as it depends on the size and frequency of the job queue scheduler. Then the odd workaround:
Any thoughts on what's wrong here? | 17:22:23 |
| justinl | Based on https://www.semantic-mediawiki.org/wiki/Help:Change_propagation, could this just be slow job queue processing, even though there's nothing else going on in the test wiki I'm using? | 17:29:04 |
| justinl | I did another test while watching runJobs.php --wait and saw the CirrusSearch and SMW change propagation jobs happen within 2 seconds of step 4. | 17:33:01 |
| justinl | Reading through this now: https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/4344 It's a lot, but in case it jogs memories of anyone here... | 18:34:02 |
| justinl | So far I'm not seeing anything helpful there. Any thoughts here? Would it be a good idea to update the issue with my specific issue and workaround? This may have to delay our upgrade planned to be done next week or the following. | 18:51:26 |
| justinl | Never mind. Our editors report this is normal, their "workaround" is to just wait several seconds. | 20:10:37 |
| 30 Mar 2024 | ||
 revansx | ok.. hopefully a noob question with a simple answer.. I upgraded MW from 1.35 to 1.39. When I visited one of the wikis, I got the well-known SMW error page that says, "Semantic MediaWiki was installed and enabled but is missing an appropriate upgrade key." So, as instructed, I ran both Both scripts ran without error, issue, or warning.. all seems good from the command line, but I'm still seeing the "Semantic MediaWiki was installed and enabled but is missing an appropriate upgrade key." error page when I visit the wiki. Is there something obvious I'm missing? | 15:37:54 |
| revansx | * Hopefully a noob question with a simple answer.. I upgraded MW from 1.35 to 1.39. When I visited one of the wikis, I got the well-known SMW error page that says, "Semantic MediaWiki was installed and enabled but is missing an appropriate upgrade key." So, as instructed, I ran both Both scripts ran without error, issue, or warning.. all seems good from the command line, but I'm still seeing the "Semantic MediaWiki was installed and enabled but is missing an appropriate upgrade key." error page when I visit the wiki. Is there something obvious I'm missing? | 15:38:05 |
 freephile | I'm not an expert on the 'setup consistency' checks in SMW, but I do know that if you're referring to a Meza instance, that the .smw.json file was moved in the latest version of Meza 39.6 That could be causing your problem. | 16:07:24 |
| freephile | You could ignore the consistency checks altogether with the new setting https://www.semantic-mediawiki.org/wiki/Help:$smwgIgnoreUpgradeKeyCheck (maybe not the best approach) | 16:08:47 |
| freephile | You could search for .smw.json files to see if there are multiple
| 16:09:54 |
| freephile | also, either enable debugging and look in the mw_debug log file, or visit the page generating the error with ?requestDebug=true (meza only) | 16:19:31 |
| freephile | SMW should be generating some detailed info about what it thinks is wrong: https://www.semantic-mediawiki.org/wiki/Help:Setup_check | 16:21:00 |
| krabina | Usually update.php fixes this (by invoking SetupStore.php) So after that the message should go away. | 18:35:20 |
| revansx | I'm not sure what I did to fix it but it works now | 18:37:54 |
| revansx | Thank you both | 18:39:49 |
| 3 Apr 2024 | ||
 Jonathan Lee | Hi folks - I'm investigating an issue where creating a large number of redirects quickly on a wiki using SMW can cause the webserver to get overwhelmed with parses of the target page. After some investigation, I think the it's because any time a redirect gets created, it triggers a "ChangeTitleUpdate" deferred job, which does a full parse of the target page | 03:30:35 |
| Jonathan Lee | Does anyone know what the purpose of this job is? I am having a hard time understanding why the creation of a redirect would require a re-parse of the target page | 03:31:30 |
| Jonathan Lee | If it's indeed necessary, I wonder if it would be better to move it to the job queue, rather than a deferred update. Since it's deferred (but still on the main webserver), it's quite easy for someone bot-creating a bunch of redirects to subtly DOS the server with all the re-parses, since their api.php edit requests won't wait for the parse to finish | 03:33:24 |
| Jonathan Lee | digging a bit more, it seems to be related to https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/895 | 04:06:44 |
| Jonathan Lee | but I still don't understand why this requires a re-parse of the target page | 04:06:54 |
| 4 Apr 2024 | ||
 Bertrand Gorge | Hello, I just logged what seems to be a regression in SMW 4.1.3 - it seems linked to ElasticStore. I am available with a debugging environment if someone with knowledge of the SMW code wants to dig this out...! https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/5618 | 07:55:52 |
| 10 Apr 2024 | ||
 Heric Dreri joined the room. | 09:06:51 | |
| 17 Apr 2024 | ||
| revansx | Bernhard Krabina, Great MWCon presentation, Bernhard! Thank you! | 19:33:54 |
| 23 Apr 2024 | ||
| revansx | We are testing a new MW 1.39 wiki server running SMW 4.1.3 and have encountered a strange behavior; namely, that "null edits" (editing a page source by adding a white space at the end and hitting save) no longer forces the SMW properties to update as it does on our existing production MW 1.34 server running SMW 3.2.3. Does anyone confirm this new (to us) behavior between SMW 3.2.3 and SMW 4.1.3? Thanks! | 20:07:45 |
| justinl | I can try to test ours. | 20:08:50 |
| revansx | In reply to @justinl:matrix.orgThank you! | 20:10:43 |
| krabina | I did not notice differences. Null edits don't need inserting spaces btw. They should ttigger jobs and if your job queue is working, everything is fine. | 21:21:04 |