[19:26:19] bd808: ping about the addon, did you see my earlier message about it working? [19:26:49] I did [19:28:15] bd808: do you want to upload a new version? or give me access and I can do it? [19:31:51] There isn't any "org" account for the Mozilla stuff. I can try uploading a new version, or you could just start a new project there for the new one [19:34:29] do you want to upload a new version? that way people don't have to install a new addon [19:35:07] I also created https://github.com/wikimedia/ChromeWikimediaDebug/pull/8 [19:36:04] legoktm: yeah, I'll look into it. Probably not today, but soon. [19:36:21] poke me if you don't see change and think I'm slacking :) [19:37:59] * no_justification has merge rights there :p [19:38:15] I'll poke you whenever my Firefox upgrades to FF 56 ;) [19:41:17] Now I have to find my notes on how to actually build and upload a FF extension :) [19:49:58] legoktm: So I've just installed ContentTranslation, and it uses JWT (JSON Web Token) from composer. I forgot to run "composer install" initially, and so things broke because JWT wasn't installed. Now that I have run "composer install", class_exists('Firebase\JWT\JWT') returns true in mwscript eval.php but false when doing API calls over http. Help? :/ [19:50:16] I tried restarting HHVM to no avail [19:50:42] And "load_composer_autoloader" was already set to true in extension.json [19:50:59] o.O [19:51:19] eval.php and the API should match in terms of autoloaded classes... [19:51:23] Restarting Apache now because I'm not actually sure if I'm using HHVM or Zend [19:51:43] Ha that did it [19:51:45] Sorry for bothering you [19:53:24] :) [19:53:38] so probably something got stuck in OpCache [20:01:12] bd808: I don't think you need to build anything, just zip and upload. https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Publishing_your_WebExtension [20:49:03] James_F: how much do we still care about LiquidThreads? [20:49:47] Enough that every bug I've filed in the last 4ish years has gone unresolved :p [20:49:53] legoktm: A bit. It's still live (not just a placeholder) on a handful of wikis. [20:49:59] legoktm: Why? [20:52:06] I'm seeing buggy behavior when I use it locally related to the OOUI-ification of EditPage (I can't reproduce on testwiki, still tracking down more specifics). New post + reply functionality still works, but the jquery.spinner never goes away [21:16:51] legoktm: I submitted the FF build for review. :) I had to click past a big red THERE IS NO GOING BACK warning for the switch to the new extension format [21:24:20] bd808: sweet, thanks :D [21:40:07] legoktm: Hmm. If you or someone files a task I'll look at it, but it's not a priority.