I think that this is because page uses the talk page in a way that it is included as a template. (ie. there is a link in templatelinks database table between page and the talk page) the edits of the talk page will be handled like the edits to templates used in the article.

select * from arwiki_p.templatelinks where tl_from=657450 and tl_namespace NOT IN (828,10);

The inclusion of the talkpage itself seems to come from template linked below but i am not sure what it tries to do

• https://ar.wikipedia.org/wiki/%D9%82%D8%A7%D9%84%D8%A8:%D8%B4%D8%B1%D9%8A%D8%B7_%D8%A8%D9%88%D8%A7%D8%A8%D8%A7%D8%AA

The inclusion of the talkpage itself seems to come from template linked below but i am not sure what it tries to do

Hello @Zache this inclusion for track project assessments, but I don't think this iclusion made above issue, as the inclusion exist since November 2019, and this problem appeared only after 12 December 2019.

Probably related to edits made on MediaWiki-extensions-FlaggedRevs (MediaWiki 1.35/wmf.10)

Probably related to edits made on MediaWiki-extensions-FlaggedRevs (MediaWiki 1.35/wmf.10)

There was "No changes for FlaggedRevs" on MediaWiki 1.35/wmf.10 update.

https://www.mediawiki.org/wiki/MediaWiki_1.35/wmf.10#FlaggedRevs

There was "No changes for FlaggedRevs" on MediaWiki 1.35/wmf.10 update.

I see now! So do you recommend to remove this tracking inclusion (to try if it'll fix the issue)?

The second option could be to set wgFlaggedRevsHandleIncludes to FR_INCLUDES_CURRENT ( value = 0 ) in InitialiseSettings.php so that FlaggedRevs would not track the included pages. However, this would mean that there would not be notifications from the file, module or template changes in articles either. If you doesn't need those notifications then this would simplify the user interface and this would be my recommendation.

Currently, arwiki is using default value FR_INCLUDES_STABLE which means that try to use a stable version or/and notify for the changes.

@Zache

Mr. Ibrahem stopped the tracking, and as I see the issue fixed now.