Score extension now leaving large amounts of space on rendering
Closed, ResolvedPublic
Actions

Description

Recently new scores using the score snippet are rendering with large amounts of white space. For an example, see this enWS page I worked on a few minutes ago. This would appear to be due to the latest MW release, because this page was initially rendered a few days ago and it doesn't show the problem.

Details

	Subject	Repo	Branch	Lines +/-
	Partially revert "Enable musical notation datatype in wikidata"	operations/mediawiki-config	master	+1 -3

Customize query in gerrit

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Resolved		• alaa_wmde	T218535 Score extension now leaving large amounts of space on rendering
		Duplicate		• alaa_wmde	T218643 Reset default wgScoreTrim to true

Event Timeline

Beeswaxcandle created this task.Mar 18 2019, 5:10 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 18 2019, 5:10 AM

Peachey88 added projects: Regression, MediaWiki-extensions-Score.Mar 18 2019, 9:48 AM

A baffling example can be seen at en:Help talk:Score#Image size.

Aklapper removed a project: MW-1.33-notes (1.33.0-wmf.21; 2019-03-12).Mar 18 2019, 8:43 PM

The generated image is way too large and the source of the whitespace

TheDJ mentioned this in T216730: Enable musical notation datatype.Mar 18 2019, 9:08 PM

More thorough description:

Polish Wikisource users reported recent problems with rendering of newly transcribed notes (Extension:Score). I compared "old" transcripts (with last change within <score> tags more than several weeks) and a "new" transcript. The issue is reproduceable.

Steps to Reproduce:
Scenario 1 (regression bug - show that pages rendered correctly earlier are broken after any changes)

Pick any page that uses Score extension without any recent changes. Example: https://pl.wikisource.org/wiki/Strona:PL_Roger_-_Pieśni_Ludu_Polskiego_w_Górnym_Szląsku.djvu/44. This is the respective .png rendered for this score: https://upload.wikimedia.org/score/d/q/dq6kxl0muwambka4wk07y9xnvr6em88/dq6kxl0m.png
Edit the page. Change any note within <score> tag to force rerendering and pick "Show preview" instead of saving.
Scenario 2

Check the rendering of any newly created page using Score extension. Example: https://pl.wikisource.org/wiki/Strona:PL_Roger_-_Pieśni_Ludu_Polskiego_w_Górnym_Szląsku.djvu/241 (rendered .png: https://upload.wikimedia.org/score/6/c/6c428f0gjrqkgc6blrlu6p6dfetm00g/6c428f0g.png )

Actual Results:
Scenario 1:
The score will be rendered as a full page .png which is incorrect as it leaves too much space between the score and MIDI player and the subsequent text on the page.
Scenario 2:
The same as in scenario 1: score is rendered as a whole page that results in a large gap between the score and the text below and MIDI player (visible on wikisource page)

Expected Results:
Scenario 1:
Score should resemble "old" layout, its size should be adequate to the length of the score, rerendering should only include changed note and not change the whole layout
Scenario 2:
As in scenario 1: the .png should be large enough to fit the score, but not larger

Rodomonte subscribed.Mar 18 2019, 10:11 PM

Ankry subscribed.Mar 18 2019, 10:15 PM

Aklapper merged a task: T218603: score extension generates only full-page images with empty space at the bottom.Mar 18 2019, 11:56 PM

The problem is that ImageMagick, the program used to crop the scores, is not working. However, how ImageMagick is called has not changed in a while...

Shoot, I thought I had posted this in the morning!

Change 497433 had a related patch set uploaded (by Ebe123; owner: Ebe123):
[operations/mediawiki-config@master] Partially revert "Enable musical notation datatype in wikidata"

https://gerrit.wikimedia.org/r/497433

gerritbot added a project: Patch-For-Review.Mar 19 2019, 3:21 AM

Will be fixed with T218643

Addshore triaged this task as High priority.Mar 19 2019, 9:40 AM

Addshore added a subtask: T218643: Reset default wgScoreTrim to true.

• alaa_wmde added a project: Wikidata-Campsite.Mar 19 2019, 1:44 PM

Restricted Application added a project: Wikidata. · View Herald TranscriptMar 19 2019, 1:44 PM

• alaa_wmde closed subtask T218643: Reset default wgScoreTrim to true as Invalid.Mar 19 2019, 1:45 PM

• alaa_wmde mentioned this in T218643: Reset default wgScoreTrim to true.

• alaa_wmde edited projects, added Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)); removed Wikidata-Campsite.

• alaa_wmde moved this task from To Do (prioritised from top to bottom) to Peer Review on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board.

Ebe123 merged a task: T218643: Reset default wgScoreTrim to true.Mar 19 2019, 5:39 PM

Ebe123 added a subscriber: • alaa_wmde.

@Ebe123 was this deployed in yesterday's swat?

Change 497433 had a related patch set uploaded (by Ladsgroup; owner: Ebe123):
[operations/mediawiki-config@master] Partially revert "Enable musical notation datatype in wikidata"

https://gerrit.wikimedia.org/r/497433

Change 497433 merged by jenkins-bot:
[operations/mediawiki-config@master] Partially revert "Enable musical notation datatype in wikidata"

https://gerrit.wikimedia.org/r/497433

Mentioned in SAL (#wikimedia-operations) [2019-03-20T11:28:30Z] <ladsgroup@deploy1001> Synchronized wmf-config/InitialiseSettings.php: SWAT: [[gerrit:497433|Partially revert "Enable musical notation datatype in wikidata" (T218535)]] (duration: 00m 50s)

• alaa_wmde moved this task from Peer Review to Done on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board.Mar 20 2019, 11:29 AM

• alaa_wmde closed this task as Resolved.Mar 20 2019, 11:32 AM

• alaa_wmde claimed this task.

Lydia_Pintscher reopened this task as Open.Mar 20 2019, 11:45 AM

Lydia_Pintscher moved this task from Done to Needs Announcement on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board.

Oops sorry resolve it by mistake .. meant to resolve only the other one.. thanks for fixing Lydia

@Lydia_Pintscher, why would a bug-fix for a bug that never affected Wikidata need to be announced there?

I think, this still needs some maintenance to regenerate broken score images, created while the wrong configuration was active.

Impossible to have a full list of broken scores, but they can be fixed by adding a comment to the scores, which will force regeneration.

@Ebe123 This is handled by the Wikidata team and the Wikidata team has a specific process about how tickets flow through the pipeline. A part of that is product management and community communications testing the feature or bugfix to make sure everything is ok. So please leave the ticket open when someone reopens it when their team is the one working on it.

In T218535#5040209, @Ebe123 wrote:

Impossible to have a full list of broken scores, but they can be fixed by adding a comment to the scores, which will force regeneration.

No true. This is possible. Only pages with the "score" property edited in specific time period are affected and number of wikis that use score effectively is limited. Basing on such a query:
https://quarry.wmflabs.org/query/34588
I can likely provide a full list of broken score images.

Will it be helpful?

@Lydia_Pintscher: I understand that you have your processes, that was not the concern. It was more asking why Wikidata has taken an interest in this bug, seeing that it did not affect Wikidata (some sort of taking responsibility as the cause of the bug?)

@Ankry: It would be helpful, thanks! I didn't know about this quarry-ing :) Would be good to group by page, but also make sure that content in the score tag was modified in the timeframe, and include all wikis)

In T218535#5040598, @Ebe123 wrote:

@Lydia_Pintscher: I understand that you have your processes, that was not the concern. It was more asking why Wikidata has taken an interest in this bug, seeing that it did not affect Wikidata (some sort of taking responsibility as the cause of the bug?)

Yes. It was caused in the process of enabling showing of musical notations in Wikidata statements.

In T218535#5040528, @Ankry wrote:

In T218535#5040209, @Ebe123 wrote:

Impossible to have a full list of broken scores, but they can be fixed by adding a comment to the scores, which will force regeneration.

No true. This is possible. Only pages with the "score" property edited in specific time period are affected and number of wikis that use score effectively is limited. Basing on such a query:
https://quarry.wmflabs.org/query/34588
I can likely provide a full list of broken score images.

Will it be helpful?

I would rather deal with my five scores on enWS myself. Even if a bot amends them, I'll still have to go back into the pages to do other tasks. I would be surprised if there were any other enWS scores affected as I'm the principal editor of such and I would have been contacted by anyone else seeing the problem.

In T218535#5040598, @Ebe123 wrote:

@Ankry: It would be helpful, thanks! I didn't know about this quarry-ing :) Would be good to group by page, but also make sure that content in the score tag was modified in the timeframe, and include all wikis)

Here is the list of broken images generated among wikis:

In T218535#5041247, @Beeswaxcandle wrote:

I would rather deal with my five scores on enWS myself. Even if a bot amends them, I'll still have to go back into the pages to do other tasks. I would be surprised if there were any other enWS scores affected as I'm the principal editor of such and I would have been contacted by anyone else seeing the problem.

I confirm: 5 from enwikisource, 8 from plwikisource; others distributed among various wikipedias

WMDE-leszek moved this task from Needs Announcement to Done on the Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) board.Sep 17 2019, 12:28 PM

Score extension now leaving large amounts of space on renderingClosed, ResolvedPublicActions

Description

Details

Related ObjectsSearch...

Event Timeline

Score extension now leaving large amounts of space on rendering
Closed, ResolvedPublic
Actions

Related Objects
Search...