Last modified: 2014-11-17 10:36:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48374, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46374 - Score extension broken on test2.wikipedia.org
Score extension broken on test2.wikipedia.org
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: High major with 1 vote (vote)
: ---
Assigned To: Jan Gerber
:
Depends on:
Blocks: 33193
  Show dependency treegraph
 
Reported: 2013-03-20 17:58 UTC by MZMcBride
Modified: 2014-11-17 10:36 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2013-03-20 17:58:15 UTC
(In reply to bug 33193 comment #40)
> Tim: So, just to be explicit, we're at a point where this could be deployed
> to the cluster?

Looking at bug 33193 comment 35, it seems the Score extension is deployed to test2.wikipedia.org (cf. <https://test.wikipedia.org/wiki/Special:Version>).

However, trying to use the extension seems to error horribly: <https://test2.wikipedia.org/wiki/Score>.

Page contents:

---
<score>\relative c' { f d f a d f e d cis a cis e a g f e }</score>
---

Output:

---
Unable to compile LilyPond input file:
Processing `.../file.ly'
Parsing...
Interpreting music... 
Preprocessing graphical objects...
Interpreting music... 
MIDI output to `file.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `file.eps'...
Converting to PNG...
---
Comment 1 Jan Gerber 2013-03-21 06:19:34 UTC
are the required packages installed already? a grep for lilypond in puppet(production) does not show anything.
Comment 2 Greg Grossmeier 2013-03-21 21:22:17 UTC
Adding Tim to this issue since he is the most familiar with the extension and what it needs and what we have.
Comment 3 Greg Grossmeier 2013-03-25 21:18:40 UTC
Hey Jan,

Could you write up a puppet config for this (lilypond specifically and anything else Score-related/dependent) and submit it for review in Gerrit?

Thanks!
Comment 4 Jan Gerber 2013-04-02 10:44:17 UTC
puppet config pending review at https://gerrit.wikimedia.org/r/#/c/56577/
Comment 5 Greg Grossmeier 2013-04-09 23:09:46 UTC
That change is now merged. lilypond is now installed on all the mediawikis.

However, the same error message is still there on the /Score page. I even made a simple edit to the markup to force a regen.

Thoughts, Jan?
Comment 6 Sam Reed (reedy) 2013-04-09 23:14:50 UTC
		$cmd = wfEscapeShellArg( $wgScoreLilyPond )
			. ' ' . wfEscapeShellArg( '-dsafe=#t' )
			. ' -dbackend=eps --png --header=texidoc '
			. wfEscapeShellArg( $factoryLy )
			. ' 2>&1';
		$output = wfShellExec( $cmd, $rc2 );
		$rc = chdir( $oldcwd );
		if ( !$rc ) {
			throw new ScoreException( wfMessage( 'score-chdirerr', $oldcwd ) );
		}
		if ( $rc2 != 0 ) {
			self::throwCallException( wfMessage( 'score-compilererr' ), $output, $options );
		}


I guess giving the return code could be helpful. And even an error message..
Comment 7 Gerrit Notification Bot 2013-04-10 13:49:10 UTC
Related URL: https://gerrit.wikimedia.org/r/58509 (Gerrit Change I05946b492cbe5eed2ccb199f9ba29fbb3c303a5a)
Comment 8 Gerrit Notification Bot 2013-04-10 14:02:14 UTC
Related URL: https://gerrit.wikimedia.org/r/58512 (Gerrit Change I871dd28d367b0f9ecdf4637bef4f67fdc6129194)
Comment 9 Jan Gerber 2013-04-10 14:04:30 UTC
the problem is that on the apache nodes $wgMaxShellMemory is 100 Mb ($wgMaxShellMemory = 102400;) but lilybond only works with more memory.

this can be fixed buy switching to the ps backend (https://gerrit.wikimedia.org/r/58512)


to support vorbis generation, we also need to install timidity
(https://gerrit.wikimedia.org/r/#/c/58504/)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links