| 13 Feb 2025 |
 Paladox | guess i can do http-request set-header X-Request-ID | 18:37:22 |
| Paladox | hmm unknown keyword 'hash-header' in 'listen' section; did you mean 'hash-type' maybe ? | 18:44:14 |
| Paladox | chatgpt seems to suggest like: | 18:44:52 |
| Paladox | balance hdr(X-Request-ID)
hash-type consistent
| 18:44:53 |
| Paladox | ok got it working now (not sure if it'll work just yet as in stop "is not readable.") | 18:47:13 |
| 14 Feb 2025 |
| Paladox | Since i deployed it, i haven't seen it error out with that error. I've done https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/6021 (not tested) as there should not be a assumption that jobs run on the same host. | 18:27:39 |
 justinl | We're seeing 504 timeouts on certain pages that our editors think may be due to heavy SMW templates (some of our pages uses dozens, some over 80). One method to replicate this, I was shown, is to go to https://wiki.guildwars2.com/wiki/Special:ExpandTemplates and put in "Dragon Slash" as the title and {{ related traits }} as the wikitext. Any ideas off the top of anyones' heads why that might be happening? The editors also say that if the page e.g. https://wiki.guildwars2.com/wiki/Special:Browse/:Dragon-5FSlash doesn't generate, the SMW properties don't get fully created. | 23:03:51 |
 Jeroen De Dauw | Are any people here running serious SMW wikis with MediaWiki 1.43? | 23:47:04 |
| justinl | A couple more comments, tldr version, from the editor:
I suspect the SMW database query it does in the background is too big
I think I can fix this issue by removing some of the middle sort keys for now, but this feels like it should safely detect its asking for too much information and reject the query
imo this is a flaw in the SMW extension, which should check if there's at least 1 result in the first bit ( [[Is for skill.Has context::Trait]] [[Has fact type::+]] [[Has fact::Dragon Slash]] [[Is for skill.Has availability::Current]] ) , before attempting to sort the rest
| 23:52:08 |
| justinl | And before that first comment
seems to be a SMW sort thing, if the query is incredibly vague (e.g. effectively select all results), and has 7 different sort keys, then at some level it is probably fetching ALL of the sort keys for ALL results, even if its only displaying 5 results
| 23:53:08 |
| 15 Feb 2025 |
| justinl | https://wiki.guildwars2.com/index.php?title=Template:Trait_list&curid=268741&diff=2932699&oldid=2657056 | 00:27:23 |
| Paladox | We recently upgraded to MW 1.43. I don't personally run one but we have wikis that use SMW. | 13:49:20 |
| Paladox | Wondering if references to SMW freenode channel (not sure if you are still on it?) could be updated to this element channel on https://www.semantic-mediawiki.org/wiki/Contact and https://www.semantic-mediawiki.org/wiki/Help:Introduction_to_Semantic_MediaWiki please? I know it's referenced elsewhere which was hard to find. | 16:41:37 |
| 16 Feb 2025 |
 nikerabbit | Not yet. Still a bit afraid to upgrade. I have one wiki running 1.42 and rest still on 1.41. | 14:17:22 |
 freephile | I've been running the test suites and now that I finally have XDebug working too, I hope to fix some issues | 14:48:43 |
| 17 Feb 2025 |
| Paladox | https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/6044/ i got the tests working... | 19:57:37 |
| freephile | On 1.43 there are still ~13 failures. I've recorded them here
Is there anything out of those 13 I should focus on as a priority; or conversely anything I should ignore at the moment?
| 23:13:40 |
| 18 Feb 2025 |
 Alexander Mashin | Does the fact box in preview mode work without "parser state reset" errors? | 02:08:29 |
| Paladox | I think they would all be a priority. I'm not aware of one that takes priority over the other. | 12:41:53 |
| Paladox | iirc all those failures happens without my change. So my change doesn't cause those failures (you can compare using https://github.com/SemanticMediaWiki/SemanticMediaWiki/actions/runs/13369923640/job/37335997326) | 12:43:15 |
| freephile | I can attest that those failures were pre-existing and do NOT come from your changes. I've seen them earlier. | 12:44:36 |
| 24 Feb 2025 |
 krabina | Why can I not set everything in composer.local.json to "dev-master"?
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires mediawiki/semantic-media-wiki dev-master, ~3.1|~4.0, found mediawiki/semantic-media-wiki[dev-revert-docker-compose-ci, ..., dev-paladox-patch-6, 1.9beta1, ..., 1.9.2, 2.0-RC1, ..., 2.5.x-dev, 3.0.0-rc.1, ..., 3.2.3, 4.0.0, ..., 4.2.0, 5.x-dev (alias of dev-master)] but it does not match the constraint.
| 16:20:39 |
| freephile | It looks like you've got a requirement for ~3.1 that is blocking it | 16:30:47 |
| freephile | you probably need to delete composer.lock and then run composer install --dry-run followed by composer install | 16:41:42 |
| freephile | composer info -vvv will give you an idea of what composer is reading from and what is installed | 17:34:09 |
| 6 Mar 2025 |
|  witchit changed their display name from witchIT to Christine Hennig / witchIT. | 13:58:09 |
| witchit changed their display name from Christine Hennig / witchIT to Christine / witchIT. | 14:00:19 |
| 8 Mar 2025 |
| Paladox changed their display name from Paladox none to Paladox. | 16:38:46 |
| 9 Mar 2025 |
|  VulcanSphere in the Matrix.org changed their profile picture. | 15:52:35 |
|  ironnorivn joined the room. | 18:33:01 |
