A tag to collate all tasks which have an error log or stack trace attached from Miraheze Production.
Sat, Nov 28
Tue, Nov 24
Mon, Nov 23
Submitted merge request upstream to fix DPL3 entirly. If it is not merged upstream I will end up fully maintaining a forked version of the extension, as it is a very useful extension to have.
Sun, Nov 22
Thu, Nov 19
Wed, Nov 18
This is a DPL3 issue and not something we can solve at the moment, therefore not a high priority task.
For the record, the log reads:
2020-11-18 07:25:26 mw4 shiropediawiki: [b004753a561c960f43984063] /w/index.php?title=%E5%9F%8E%E3%83%9A%E3%83%87%E3%82%A3%E3%82%A2:%E8%AD%B0%E8%AB%96%E6%89%80&oldid=3252 Wikimedia\Rdbms\DBQueryError from line 1699 of /srv/mediawiki/w/includes/libs/rdbms/database/Database.php: Error 1054: Unknown column 'rev.rev_user' in 'field list' (db11.miraheze.org) Function: DPL\Query::buildAndSelect Query: SELECT DISTINCT rev.rev_timestamp,rev.rev_user,rev.rev_user_text,rev.rev_comment,`page`.page_namespace AS `page_namespace`,`page`.page_id AS `page_id`,`page`.page_title AS `page_title` FROM `revision` `rev`,`page` INNER JOIN `categorylinks` `cl1` ON ((`page`.page_id = cl1.cl_from AND cl1.cl_to = '進行中の議論')) WHERE ((`page`.page_title like'%議論所/%')) AND (`page`.page_id = rev.rev_page) AND (rev.rev_timestamp = (SELECT MAX(rev_aux.rev_timestamp) FROM `revision` AS rev_aux WHERE rev_aux.rev_page = rev.rev_page)) AND `page`.page_is_redirect = 0 AND `page`.page_namespace = 4 AND (`page`.page_id = rev.rev_page) AND (`page`.page_id = rev.rev_page) AND (rev.rev_timestamp = (SELECT MAX(rev_aux_max.rev_timestamp) FROM `revision` AS rev_aux_max WHERE rev_aux_max.rev_page = rev.rev_page)) AND (NOT (`page`.page_title like'議論所/秀逸記事審査認定課')) ORDER BY rev.rev_timestamp DESC LIMIT 500
Sat, Nov 14
If it is a DPL problem, it is likely upstream (i.e. for the developers to resolve). Unfortunately, Miraheze does not maintain every extension we have installed.
Fri, Nov 13
Numerous related tickets for DPL3 at https://gitlab.com/hydrawiki/extensions/DynamicPageList/-/issues
Assuming DPL is DynamicPageList, I noticed this issue yesterday on another customer wiki and @Paladox ran the trace. I'll try and post the trace results later today
As I said in T6391, it is certain that it is not normal if you look at the log.
I thought it wouldn't be resolved forever, so I took first aid. That's why it looks normal. Don't get me wrong.
You can confirm that this problem has not been solved yet by practicing rudimentary things such as looking at the diff from the page history.
This is a DPL problem, and if you enter a parameter that displays the user name such as adduser or addauthor, such as "addlasteditor = true", an error will occur. Investigate the cause and resolve it.
Thu, Nov 12
Normal for now.
As @Wedhro added a comment, and stated the page wasn't working, reopening due to error. Close if needed.
@Reception123 You mean the page I linked when opening this ticket? It works just because I deleted the author search from the DPL, but the old version will still give that error: https://nonciclopedia.org/w/index.php?title=Template:Bar7/Discussioni&oldid=2249158
This issue now seems to be resolved since myself and @Paladox are both able to access the page without seeing any error.
The page seems to be working now.
Thanks, @Zppix, for reopening this ticket. I wondered if this task was appropriately closed.
Ignore the above comment
Because the page wouldn't load.
Why is this a performance issue?
Wed, Nov 11
@RhinosF1 Oops, sorry, we Phabricator edit conflicted.
Upstream task per @RhinosF1's find is here. Re-closing this as declined. We'll have to look into what MW version this was fixed in, I think, or if Wikimedia locally deployed a patch/configuration hack to temporarily fix the issue locally. Perhaps we can replicate that, if that's the case?
Can we leave this open until investigated, possibly with a lowered priority?
They implemented a fix recently afaik. Will look for the task.
@RhinosF1 Can you link the upstream task on this request? Also, I just checked this deleted revision. They're on MW 1.36, I think, yes, but I am 99.98% positive the URL displayed that way when they were in MW 1.35.
The issue did exist in 1.34 and there's a task somehwere upstream that was being worked on.
Mon, Nov 9
Did it get fixed? Thanks, you guys are geniuses! I'm forever in your debt!
@Paladox Thanks...what was the issue? Can you paste the trace here for future reference purposes?
Can probably escalate this to high priority as it's a database / production error
And then, I keep getting codes like this, which vary all the time, like this one:
[988d550ea8bb7ef9eab631f3] 2020-11-09 20:54:13: Fatal exception of type "Error"
The code will vary all the time. It's a unique id given to every exception that's logged across all of Miraheze to help us find it for you.
There's an instance of when it malfuntions.