Hi!
I'd like to welcome you to join us at the CREDIT showcase next week,
Wednesday, 3-May-2017 at 1800 UTC / 1100 Pacific Time. We'd like to see
your demos, whether they're rough works in progress or polished production
material, or even just a telling of something you've been studying
recently. For more information on the upcoming event, as well as recordings
of previous events, please visit the following page:
https://www.mediawiki.org/wiki/CREDIT_showcase
And if you'd like to share the news about the upcoming CREDIT showcase,
here's some suggested verbiage. Thanks!
*Hi <FNAME>*
*I hope all is well with you! I wanted to let you know about CREDIT, a
monthly demo series that we’re running to showcase open source tech
projects from Wikimedia’s Community, Reading, Editing, Discovery,
Infrastructure and Technology teams. *
*CREDIT is open to the public, and we welcome questions and discussion. The
next CREDIT will be held on May 3rd at 11am PT / 2pm ET / 18:00 UTC. *
*There’s more info on MediaWiki
<https://www.mediawiki.org/wiki/CREDIT_showcase>, and on Etherpad
<https://etherpad.wikimedia.org/p/CREDIT>, which is where we take notes and
ask questions. You can also ask questions on IRC in the Freenode chatroom
#wikimedia-office (web-based access here
<https://webchat.freenode.net/?channels=%23wikimedia-office>). Links to
video will become available at these locations shortly before the event.*
*Please feel free to pass this information along to any interested folks.
Our projects tend to focus on areas that might be of interest to folks
working across the open source tech community: language detection,
numerical sort, large data visualizations, maps, and all sorts of other
things.*
*If you have any questions, please let me know! Thanks, and I hope to see
you at CREDIT.*
*YOURNAME*
--
Lani Goto
Project Assistant, Engineering Admin
I'm running into a weird problem, which made me reset my whole vagrant.
I assume this is not strictly a MediaWiki issue, but probably an HHVM
problem, but maybe someone can help me here.
So, if I start a fresh MediaWiki Vagrant installation, and the vagrant ssh
into the virtual machine, the fastest way to reproduce the issue is to
start hhvmsh and type
function f():int { return 1; };
=f()
I get:
Hit fatal : Value returned from function f() must be of type int, int given
#0 at [:1]
#1 f(), called at [:1]
#2 include(), called at [:1]
Any way to circumvent this (besides getting rid of the type hint,
obviously)? Update to a new HHVM version (According to Special:Version, the
HHMV version is 3.12.14 (srv)?
Hello, as you may or may not already know there will be a datacentre
switch back to Eqiad, WMF's main data centre, on May 3rd at approximately
14:00 UTC. For approximately 20-30 minutes you will NOT be able to save
edits to any WMF project. If you have any questions feel free to reply back
to this email, or ask on IRC on freenode channel #wikimedia-tech. If there
any major issues that occur during this time please report them to
#wikimedia-tech on freenode!
Thanks,
Zppix
Volunteer Developer for WMF
www.enwp.org/User:Zppix
Hello. Could you help me, please? It's about 90 minutes I can't open the
Special:Watchlist. Sometimes I get white screen, sometimes Wikimedia Error
Request from 2.53.62.243 via cp2023 cp2023, Varnish XID 514255803
Error: 503, Service Unavailable at Sun, 30 Apr 2017 12:36:30 GMT
I would file a phab ticket, but seems it's just me. The safemode=1 does not
change.
Thank you,
Igal
User:IKhitron, hewiki, Android 6.0 inner browser.
Hello everyone.
Unfortunately there's been a mistake in generating the 1.28.1 and 1.27.2
tarball releases, where the wrong version of SyntaxHighlight_GeSHi
extension was included. The version of this extension that was included has
publically known severe security issues in it.
Until such a time as a new release is issued (which will hopefully be soon)
I reccomend that people either disable that extension or download a new
version from
https://www.mediawiki.org/wiki/Special:ExtensionDistributor/SyntaxHighlight…
. The version of this extension in git, or from extension distributor is
fine. Only the version in the most recent tarball is wrong. The rest of the
release is also fine. The 1.23.16 and 1.23.17 release was not affected by
this issue.
Sorry for the confusion,
--
Brian
TL;DR: I'm proposing deprecating a bunch of parameters. See
https://phabricator.wikimedia.org/T164106.
In the action API, there are two ways to parse a page/revision: using
action=parse, or using the rvparse parameter to action=query&prop=revisions.
Similarly, there are two ways to get a diff: using action=compare, or using
parameters such as rvdiffto to action=query&prop=revisions. And then
there's action=expandtemplates versus the rvexpandtemplates parameter to
prop=revisions. This is a somewhat annoying bit of code duplication.
Further, the prop=revisions versions of these features have somewhat
strange behavior. rvparse forces rvlimit=1. rvdiffto and related parameters
will sometimes output "notcached" with no way to directly handle the
situation.
So, I propose deprecating all of these parameters. The parameters that
would be deprecated are the 'rvdifftotext', 'rvdifftotextpst', 'rvdiffto',
'rvexpandtemplates', 'rvgeneratexml', 'rvparse', and 'rvprop=parsetree'
parameters to prop=revisions, and the similarly named parameters to
prop=deletedrevisions, list=allrevisions, and list=alldeletedrevisions.
Following the normal action API deprecation policy, they'd output warnings
but would continue to function until usage drops sufficiently or until it
becomes too much trouble to fix them, and they wouldn't receive new feature
development.
If anyone would object to this plan, please reply at
https://phabricator.wikimedia.org/T164106, or here if you really hate
Phabricator. If there aren't major objections, I'll probably do the
deprecation in the next week or two. Thanks.
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation