[15:40:27] hello [15:41:00] can someone help me for a scribunto problem? [15:49:13] well, here my problem: i followed the instructions how to install scribunto on my own wiki, once done, i tried to test a module:test with a simple hello world coding [15:50:11] i got a nasty message error which i managed to get the backtrace thing given with this magic code line: $wgShowExceptionDetails = true; [15:50:24] allaze-eroler: you'll want #mediawiki [15:50:40] ah? [15:50:53] wrong place to ask help? [15:51:08] hum... [15:51:11] alright [15:51:55] bye [16:42:14] mobrovac: so I'm wondering how extensive the x-amples stuff should be. Should it try and test every variation of the API? or just one sanity check per thing? [16:44:54] that's a good question legoktm [16:45:11] just checking super-basic for now should be enough [16:45:48] but having an automated way of checking each module's functionalities would be awesome [16:45:56] so that developers don't have to worry about it [16:50:50] mobrovac: ok, and what is the authoritative thing on the spec? because anomie pointed out how https://github.com/earldouglas/swagger-test and service-checker differ in some fields like title/description, query/params [16:51:54] yeah, swagger-test is slightly different, and should not be thought as the authority on it [16:52:04] legoktm: service-checker is what is executed, so that one [16:52:55] mobrovac, legoktm: Even more fun, we made our own slightly-different version of someone else's extension. [16:53:04] fun fun fun [16:53:09] fun^2 [17:17:02] isn't that fun^3? [17:18:41] ha! [17:18:42] depends [18:10:42] mobrovac: okay, I started writing a spec at https://www.mediawiki.org/wiki/Service-checker based on the implementation (even the README in service-checker is wrong :S) please edit! [18:12:17] anomie: ^