[Bug 63254] Wikimedia Commons support for Flickr HTTPS
https://bugzilla.wikimedia.org/show_bug.cgi?id=63254 --- Comment #2 from Bawolff (Brian Wolff) bawolff...@gmail.com --- I think this might be an issue with commons javascript and not mediawiki (In which case it would have to be filed with the commons folks in order to be fixed). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 67303] Enable HSTS (HTTP Strict Transport Security) on Wikitech
https://bugzilla.wikimedia.org/show_bug.cgi?id=67303 fn...@outlook.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from fn...@outlook.com --- https://gerrit.wikimedia.org/r/148290 fixed this issue. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 43450] UploadWizard Flickr (tracking)
https://bugzilla.wikimedia.org/show_bug.cgi?id=43450 Bug 43450 depends on bug 67298, which changed state. Bug 67298 Summary: Flickr API method=flickr.photos.licenses.getInfo requires SSL, we don't use it https://bugzilla.wikimedia.org/show_bug.cgi?id=67298 What|Removed |Added Status|RESOLVED|PATCH_TO_REVIEW Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 67298] Flickr API method=flickr.photos.licenses.getInfo requires SSL, we don't use it
https://bugzilla.wikimedia.org/show_bug.cgi?id=67298 Gerrit Notification Bot gerritad...@wikimedia.org changed: What|Removed |Added Status|RESOLVED|PATCH_TO_REVIEW Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 67298] Flickr API method=flickr.photos.licenses.getInfo requires SSL, we don't use it
https://bugzilla.wikimedia.org/show_bug.cgi?id=67298 --- Comment #13 from Gerrit Notification Bot gerritad...@wikimedia.org --- Change 148593 had a related patch set uploaded by Brian Wolff: Remove flickrApiUrl from $wgUploadWizardConfig https://gerrit.wikimedia.org/r/148593 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 67976] Archives directory /vagrant/apt-cache/partial is missing.
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976 --- Comment #7 from Bryan Davis bda...@wikimedia.org --- (In reply to Tisza Gergő from comment #6) This might be only because this box is already in a messed-up state; I can try upgrading another box if you think it will work now. If you have the energy to try and recreate on a clean install I'd appreciate the data. If not, I'll try to find some time to setup a test starting from 3c6a6606b5217a2fb16cfde4db31d5a6c8e102c5 and then updating to the current HEAD of master plus the patch. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 66143] ?embedplayer=yes videos broken (again)
https://bugzilla.wikimedia.org/show_bug.cgi?id=66143 --- Comment #21 from Bawolff (Brian Wolff) bawolff...@gmail.com --- However, when I tried this out, reusing the div class=mediaContainer ... HTML (from this wiki page: https://meta.wikimedia.org/w/index.php?title=Wikimedia_Blog/Drafts/ A_Look_Back_at_Wikimania_2013oldid=9276912 ) in a separate HTML page, it did not work correctly - the box displays nicely and the video starts playing in the browser (Chromium), but only in low quality (160p, I guess) instead of the highest possible resolution for this div. This might be more appropriate for a separate bug - in that case, sorry for the offtopic discussion. Weird. That appears to be intentional: // Sort sources by bandwidth least to greatest ( so default selection on resource constrained // browsers ( without js? ) go with minimal source. uasort( $mediaSources, 'TimedMediaTransformOutput::sortMediaByBandwidth' ); Seems like a bad design decesion... -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 67655] Show blue highlight on links when clicked and remove when clicked outside
https://bugzilla.wikimedia.org/show_bug.cgi?id=67655 Santhosh Thottingal santhosh.thottin...@gmail.com changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|wikibugs-l@lists.wikimedia. |santhosh.thottingal@gmail.c |org |om -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 52061] Merge Poem extension into MediaWiki core
https://bugzilla.wikimedia.org/show_bug.cgi?id=52061 --- Comment #51 from MZMcBride b...@mzmcbride.com --- (In reply to comment #42) (In reply to comment #38) A Global Message Delivery to all Wikisource Scriptoriums/Village pump is higly recommended MZMcBride, could you advise how feasible this would be? I think a mention in [[m:Tech/News]] is sufficient here. Nothing is breaking, as I understand it, so this news is purely informational: In addition to poem, you can also now use some other tag name. If you really want to send a global message, you can use [[m:MassMessage]]. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 68196] HHVM crash loading San Francisco page
https://bugzilla.wikimedia.org/show_bug.cgi?id=68196 --- Comment #9 from Brett Simmers bsimm...@fb.com --- After some fun times with gdb, I'm almost certain this is luasandbox related, though I'm not yet sure what the root cause is. I was seeing what looked like some C++ frames disappearing without the relevant destructors being called, so I suspected something was going wrong with a longjmp somewhere and went with that. http://pastebin.com/mKeqJYLZ is a stacktrace I took right before everything went off the rails. Notice that ExecutionContext::invokeFunc and luasandbox_call_helper both appear twice, indicating that PHP called into lua, which called back into PHP, which is now calling into lua again (this is expected behavior, right?). I previously stepped through one longjmp that didn't escape the call to luasandbox_call_helper in frame #5, but the one about to happen doesn't go so well. I stepped through this longjmp up until it restored the previous stack and took another backtrace: http://pastebin.com/6UgHygPs. Notice that it appears to have jumped from the nested invocation of lua to the outer one, skipping over all the hhvm frames in between the two. This explains how we eventually end up in the outmost invokeFunc frame with the VM state still looking like the nested frame: the nested VM state is supposed to be popped by a destructor in invokeFunc that never ran. I'm done for today but the best theory I have so far is that there's some global setjmp/longjmp buffer in liblua that's being used improperly. Is liblua supposed to handle reentrancy like this? I noticed that lua_pushcclosure() is in the backtrace for the problematic longjmp but not for the previous one; maybe that's related? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 68414] Lazy-loaded pages are not enforcing upload restrictions on mobile
https://bugzilla.wikimedia.org/show_bug.cgi?id=68414 --- Comment #4 from Florian florian.schmidt.wel...@t-online.de --- Maybe we should think about to check permission to upload in PhotoApi.js, too? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 68418] New: investigate using a non-fixed bitrate for webm transcodes
https://bugzilla.wikimedia.org/show_bug.cgi?id=68418 Bug ID: 68418 Summary: investigate using a non-fixed bitrate for webm transcodes Product: MediaWiki extensions Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: TimedMediaHandler Assignee: wikibugs-l@lists.wikimedia.org Reporter: bawolff...@gmail.com CC: aarcos.w...@gmail.com, bawolff...@gmail.com, fflo...@wikimedia.org, gti...@wikimedia.org, jger...@wikimedia.org, md...@wikimedia.org, mtrac...@member.fsf.org Web browser: --- Mobile Platform: --- Currently we use a fixed bitrate for webm (and ogg for that matter) transcodes except for webm 720p where we use a variable bit rate( -qmin 18 -qmax 18). I just noticed there are some files, such as [[File:Hindesite_-_Lily_-_Focus_Stacking_(by).ogv]], where the 720p webm transcode is smaller (2733005 bytes) than the 360p webm transcode (2769705 bytes). This seems wrong. (Note, this is probably specific to the lily file which has a lot of still frames) I don't know what original considerations went into using a fixed bitrate, but maybe we should just be specifying a quality level instead. In my test of the lily file, using a quality level of 18 (like the current 720p setting) for the 480p version gave a file size of 1.5mb, compared to the current 480p settings of -qmin 1 -qmax 51 -vb '1024000' which gives a file size of 5.3mb. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 60385] MediaWiki message delivery autocreation does not integrate with CentralAuth
https://bugzilla.wikimedia.org/show_bug.cgi?id=60385 Kunal Mehta (Legoktm) legoktm.wikipe...@gmail.com changed: What|Removed |Added Keywords|easy| Summary|[[Special:CentralAuth/Media |MediaWiki message |Wiki message delivery]] is |delivery autocreation does |missing every wiki but |not integrate with |Meta-Wiki |CentralAuth --- Comment #3 from Kunal Mehta (Legoktm) legoktm.wikipe...@gmail.com --- I manually merged the account on the WMF cluster, so the page looks fine now. But the original issue still stands. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 67298] Flickr API method=flickr.photos.licenses.getInfo requires SSL, we don't use it
https://bugzilla.wikimedia.org/show_bug.cgi?id=67298 --- Comment #14 from Gerrit Notification Bot gerritad...@wikimedia.org --- Change 148593 merged by jenkins-bot: Remove flickrApiUrl from $wgUploadWizardConfig https://gerrit.wikimedia.org/r/148593 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 68196] HHVM crash loading San Francisco page
https://bugzilla.wikimedia.org/show_bug.cgi?id=68196 --- Comment #10 from Brett Simmers bsimm...@fb.com --- I don't know anything about the internals of the Zend engine. Is it possible that this is happening with PHP5 as well but everything happens to work out anyway? I'll try it tomorrow but it's possible that in a release build of HHVM without asserts on, things could mostly appear to work. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l