[Wikitech-l] PHP 5.4 (we wish)
For those of you wishfully waiting for the day we can require PHP 5.4 to use MediaWiki feel free to add your wishes to: https://www.mediawiki.org/wiki/PHP_5.4 -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [tool labs] central logging service
https://github.com/benapetr/logger On Sat, Jun 8, 2013 at 9:34 PM, Tyler Romeo tylerro...@gmail.com wrote: Where is the source code for this logging script/software? *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Sat, Jun 8, 2013 at 6:36 AM, Petr Bena benap...@gmail.com wrote: Replies bellow On Sat, Jun 8, 2013 at 11:58 AM, Ori Livneh o...@wikimedia.org wrote: On Sat, Jun 8, 2013 at 1:44 AM, Petr Bena benap...@gmail.com wrote: Hi, per https://bugzilla.wikimedia.org/show_bug.cgi?id=48846 we are setting up a logging service for tools and bots, so that every tool or bot can easily log to a central logging base which in future should support some nice web-based gui with log filtering (eventually some 3rd notifications, like e-mails (sms) / irc pings) and so on. The website of this project is here: http://tools.wmflabs.org/logs/ I haven't got much feedback so far so I would appreciate some, in this moment we are in phase where we are discussing the best options how to design this feature. What does the 's' prefix mean? it is shortcut for store you can either type s ... or store ... it will do same, or you can use n (noreply) that will do same as s or store but will send no reply on success What is the expected character encoding of messages? You got me. I have no idea, either mono is smart enough to find out or it's uses some standard encoding by default, like utf-8 or unicode? I will find out. Google doesn't bring clear answer. How is malformed input handled? What happens if I log this message: s test 0 hi\ns fake_tool 0 evil_message\n? malformed (invalid) input gets response ERROR: explanation malformed (malicious) input is something I am still thinking of, I don't expect many users to intentionally break logs of others, but I am thinking of implementing optional authentication. If tool requested to use authentication (it would subscribe / register a folder somehow) it could for example get a temporary token that would stored somewhere like /data/project/logs/tokens/tool and which would be readable only by tool account. This token would be updated periodically for security reasons and tool would be required to provide it together with log message in order to write to its folder. But this is something I am still designing and I want to keep it opt-in as it complicate stuff and many users will likely not require it. Also we are getting far beyond possibilities of rsyslog now (another reason why using own daemon could be better). If I don't terminate my message with a newline, does my message swallow the next one to come along? I forgot to mention newline isn't required in UDP connection. You can send multiple log lines using newline or just 1 line and it will be parsed. If you terminate TCP connection before writing newline (which means - buffer is finished, store it - to daemon), it will be likely dropped (you won't get the STORED response either). How would you go about adding a field, if you discovered you needed one? Would clients using the old format break? What kind of field do you mean? How reliable does the service need to be? What is the cost of an outage? Is it OK for the service to be down for a few hours It's not OK for it to be down for few hours, however the clients should be able to recognize the server is down if they are using tcp (because they won't be able to connect). The wrapper script I made now (logeater) should be optimized to recognize this as well and keep retrying until successful or something. Outage is always a problem for any kind of logger. Some people believe that it would be best to use some already existing logging service such as facebook's scribe, I /think/ that despite the already made and working solution might be a good idea, on other hand these usually were designed for another purpose than what we need and thus it's quite complicated to set them up for our needs. Having said that I started working on simple, but powerful logging daemon which should do precisely what we need (and which can be infinitely extended for our purposes) - but of course we can set up multiple solutions and let tool operators pick what they prefer most. I think your intuitions are good. Everyone has their favorite message queue, but most are quite complex. Simple and adequate are the virtues you should optimize for. Get input from some early adopters of your service, then iterate. Let people know that the service is experimental for now, so that you have plenty of room to change the protocol if you need to. If you find yourself adding feature after feature, stop, and reconsider existing solutions. If it's simpler for a tool / bot operator to intergrate with syslog, then why we shouldn't have it as well? But I
Re: [Wikitech-l] PHP 5.4 (we wish)
To be honest, the upgrade isn't that exciting. The only real worthwhile new feature is traits. Everything else is just random fixes in syntax. As for the timetable for this, PHP 5.3 isn't going anywhere anytime soon, so there's no way we can stop supporting it. What I'm really excited about is PHP 5.5, which has generators, finally clauses, dereferencing of container literals, and a new password hashing API. Unfortunately it'll be literally a decade before we switch to that. :( *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Sun, Jun 9, 2013 at 7:18 AM, Daniel Friesen dan...@nadir-seen-fire.comwrote: For those of you wishfully waiting for the day we can require PHP 5.4 to use MediaWiki feel free to add your wishes to: https://www.mediawiki.org/**wiki/PHP_5.4https://www.mediawiki.org/wiki/PHP_5.4 -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] __**_ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP 5.4 (we wish)
Am 09.06.2013 19:49, schrieb Tyler Romeo: What I'm really excited about is PHP 5.5, which has generators, finally clauses, dereferencing of container literals, and a new password hashing API and let me add: . the integrated ZEND opcode cache in 5.5 see https://github.com/php/php-src/blob/php-5.5.0RC3/NEWS ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP 5.4 (we wish)
Le 09/06/13 13:18, Daniel Friesen a écrit : For those of you wishfully waiting for the day we can require PHP 5.4 to use MediaWiki feel free to add your wishes to: https://www.mediawiki.org/wiki/PHP_5.4 Thank you for that document. To me the only worthwhile feature is traits which would make some part of the code a bit cleaner or easier to organize. I like the short array syntax, but I do not think it is worth breaking PHP 5.3 compatibility just to save a few keystrokes :-) PHP 5.4 also brings some performances boosts (I have no metrics though). But nothing seems to our 5.3 codebase to run on 5.4, so there is no hurry to upgrade our requirement. -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHP 5.4 (we wish)
Closure changes and traits would indeed be really nice. Short array syntax is a plus too. -- View this message in context: http://wikimedia.7.x6.nabble.com/PHP-5-4-we-wish-tp5006788p5006809.html Sent from the Wikipedia Developers mailing list archive at Nabble.com. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Pager code review
Not sure who to add, but if somebody familiar with the TablePager class could review this patchset I'd appreciate it: https://gerrit.wikimedia.org/r/67627 First time I've used the class. It works, but I want to make sure I'm using it properly. *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bugzilla Weekly Report
MediaWiki Bugzilla Report for June 03, 2013 - June 10, 2013 Status changes this week Reports changed/set to UNCONFIRMED: 4 Reports changed/set to NEW: 17 Reports changed/set to ASSIGNED : 60 Reports changed/set to REOPENED : 18 Reports changed/set to RESOLVED : 217 Reports changed/set to VERIFIED : 20 Total reports still open : 10498 Total bugs still open : 5785 Total non-lowest prio. bugs still open: 5602 Total enhancements still open : 4713 Reports created this week: 302 Resolutions for the week: Reports marked FIXED : 137 Reports marked DUPLICATE : 31 Reports marked INVALID : 22 Reports marked WORKSFORME: 16 Reports marked WONTFIX : 22 Specific Product/Component Resolutions User Metrics Created reports per component WikidataRepo24 General/Unknown 19 UniversalLanguageSelector 16 Site requests 13 General/Unknown 12 Created reports per product MediaWiki 50 Wikimedia 59 MediaWiki extensions125 Datasets5 Security2 Top 5 bug report closers jforrester [AT] wikimedia.org 17 benapetr [AT] gmail.com 15 sam [AT] reedyboy.net 12 jrobson [AT] wikimedia.org 12 aklapper [AT] wikimedia.org 12 Most urgent open issues Product | Component | BugID | Priority | LastChange | Assignee | Summary -- Analytics | User Metrics | 47269 | Highest | 2013-04-16 | wikibugs-l[AT]lists. | Jobs idling in production, no way to MediaWiki | Installer | 47191 | Highest | 2013-05-25 | wikibugs-l[AT]lists. | [Regression] Installer: MySQL Fatal E MediaWiki ext | Echo | 47094 | Highest | 2013-05-30 | ebernhardson[AT]wiki | Notification preferences update (tool MediaWiki ext | Echo | 48183 | Highest | 2013-05-30 | wikibugs-l[AT]lists. | Show diff link when appropriate on ta MediaWiki ext | OpenID| 44819 | Highest | 2013-05-07 | mail[AT]tgries.de| [SUGGESTION] change $wgOpenIDConsumer MediaWiki ext | PdfHandler| 48834 | Highest | 2013-06-03 | wikibugs-l[AT]lists. | PdfHandler Fatal exception when used MediaWiki ext | ValueFormatte | 48937 | Highest | 2013-06-07 | wikibugs-l[AT]lists. | Implement value formatter for time da VisualEditor | ContentEditab | 48468 | Highest | 2013-06-03 | inez[AT]wikia-inc.co | VisualEditor: Pawn appears when creat VisualEditor | ContentEditab | 48526 | Highest | 2013-06-03 | inez[AT]wikia-inc.co | VisualEditor: Pressing Enter in a hea VisualEditor | ContentEditab | 48385 | Highest | 2013-06-03 | inez[AT]wikia-inc.co | VisualEditor: Delete contents of slug VisualEditor | Data Model| 48769 | Highest | 2013-05-24 | roan.kattouw[AT]gmai | VisualEditor: Link corruption oddity VisualEditor | General | 39599 | Highest | 2013-06-03 | jforrester[AT]wikime | VisualEditor: Support references ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] CHanging the name of Vector on 1.21.1
Hello everyone,
I want to modify the default Vector theme that comes with 1.21.1. But before I
do that I want to rename it. I want to name it nighttime. I created a folder
called nighttime and copied all the vector files into it. Then I made a copy of
Vector.php and called it Nighttime.php. I then modified the appropriate
contents of Nighttime.php as follows...
---
class SkinNighttime extends SkinTemplate {
protected static $bodyClasses = array( 'vector-animateLayout' );
var $skinname = 'nighttime', $stylename = 'nighttime',
$template = 'NighttimeTemplate', $useHeadElement = true;
...
unction setupSkinUserCss( OutputPage $out ) {
parent::setupSkinUserCss( $out );
$out-addModuleStyles( 'skins.nighttime' );
...
class NighttimeTemplate extends BaseTemplate {
-
You can see what the site looks after I renamed everything at
http://beta.dropshots.com/j00100/media/75373447 It appears as if there is no
formatting.
I did some searching on Google but everything I found dealt with older
versions. Does anyone know how to rename Vector and have it working on 1.21?
Thanks
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] CHanging the name of Vector on 1.21.1
The skinning tutorial is:
https://www.mediawiki.org/wiki/Manual:Skinning/Tutorial
And for creating derivative skins use this technique:
http://blog.redwerks.org/2012/02/28/mediawiki-subskin-tutorial/
New skins should be created using the skinname/skinname.php patterns in
those tutorials.
Mid-term plans for skinning are likely going to include dropping support
for custom/3rd-party skins which add php files directly to skins/ instead
of using autoloading and a file to require like how extensions do it.
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
On Sun, 09 Jun 2013 22:14:16 -0700, j00...@mail.com wrote:
Hello everyone,
I want to modify the default Vector theme that comes with 1.21.1. But
before I do that I want to rename it. I want to name it nighttime. I
created a folder called nighttime and copied all the vector files into
it. Then I made a copy of Vector.php and called it Nighttime.php. I then
modified the appropriate contents of Nighttime.php as follows...
---
class SkinNighttime extends SkinTemplate {
protected static $bodyClasses = array( 'vector-animateLayout' );
var $skinname = 'nighttime', $stylename = 'nighttime',
$template = 'NighttimeTemplate', $useHeadElement = true;
...
unction setupSkinUserCss( OutputPage $out ) {
parent::setupSkinUserCss( $out );
$out-addModuleStyles( 'skins.nighttime' );
...
class NighttimeTemplate extends BaseTemplate {
-
You can see what the site looks after I renamed everything at
http://beta.dropshots.com/j00100/media/75373447 It appears as if there
is no formatting.
I did some searching on Google but everything I found dealt with older
versions. Does anyone know how to rename Vector and have it working on
1.21?
Thanks
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
