[02:10:21] having trouble getting https://en.wikipedia.org/wiki/Special:Log?type=newusers&user=&page=&wpdate=2017-06-11&tagfilter= to load [02:14:03] You're not the only one :P [02:14:10] It was slow, but loaded on PHP7 for me [02:17:27] It took long enough for me (PHP7 as well) that I got bored and closed the tab [02:26:26] It just throws a "too long" error [02:26:33] for me anywayz [11:13:33] what would it take to enable webm embedding on our phabricator? https://phabricator.wikimedia.org/T215360 [12:39:20] Hi, I'd need some quick help with my bot, it's getting "Please wait 5 minutes before trying again" from two different servers now [13:01:36] For login? [13:02:04] Make sure the password is right and wait 5 minutes before trying again [13:02:41] The ratelimitting is crosswiki. So you should wait 5 min for all sites [13:03:14] Hi, bawolff [13:03:27] The problem is that is not just 5 minutes [13:03:54] This has happened again in the past and it went over for days until someone fixed it [13:04:28] And for no clear reason it says 5 minutes first, then 2 days... [13:05:16] It was hapenning in the Wikimedia Spain server, I moved to Toolforge, then I did a test and now both servers have the same problem [13:06:44] Well there's a good reason. If you hit the five minute warning too many times the system thinks you are trying to bruteforce passwords and locks you out for two days [13:06:47] Last time: https://phabricator.wikimedia.org/T195541 , anomie fixed it and I have tried to ping him [13:07:23] How many times would be "too many"? [13:07:41] Yes, developers can manually delete the lock out [13:07:57] I think it has been one or two times in Toolforge, I would say [13:08:51] But making sure your bot isnt hitting the login form repetitively is also a good solution [13:10:10] Well, I stopped the bot from running from the WM-ES server 5 days ago, I have just made one or two single tests a day since then [13:11:20] Just a second I'll check the logs [13:11:24] for reference, you get the five minute warning after five failed attempts, and the 2 day lockout after 150 attempts [13:11:30] Thanks, bawolff_ [13:12:03] I'd say it's not the case but maybe there's something strange going on [13:12:21] So there are two recent attempts n the last 20 minutes that were both using the wrong password [13:12:47] And there's been 5076 attempts in the last 30 days [13:13:32] The last attempt that was due to the 5 minute lock out was at 2019-02-13T12:46:45 UTC [13:13:52] Ok, 5076 in 30 days with the correct password should be right [13:13:53] After that there were 6 attempts using the wrong password [13:14:06] These are all with the wrong password [13:14:12] 5076 ? [13:14:34] largely from feb 9 [13:16:07] Well, on feb 9 the WM-ES had a problem, but I don't understand why that creates logins with wrong password [13:16:18] WM-ES server* [13:17:25] And why that has happened two o three times before... [13:17:29] or* [13:19:27] So you do also generally have lots of good logins too (except major falloff around feb 10. The number of good logins falls in half starting around feb 12 (from ~100 hour -> ~30 an hour) [13:20:01] That is quite strange [13:20:50] So maybe you have multiple bot processes, and one of them has an old config file or something, that's trying to login with the wrong bot password, and occasionally locking out the account [13:20:52] I had to launch it manually but on feb 11 I decided to use the crontab [13:21:42] Well, the password is correct in both servers, maybe it is a problem when reading the secret file [13:21:52] I can't think of another explanation [13:22:07] If it helps, the failed logins are from from WMF labs ips. and see to be for eswiki only [13:23:01] hmm or at least the recent ones are [13:23:41] There's a failed attempt at 2019-02-13T12:28:18 which is from wikimedia.es server [13:23:59] The most recent ones... well, I have tried but always with the right password, but I was getting the "incorrect" or "5 minutes" answers [13:24:12] From both servers [13:25:15] It definitely seems to be only for login attempts to eswiki [13:25:35] There are some login attempts that fail due to account lockout for other wikis, but all the wrong password failures are for eswiki only [13:26:12] And the wrong passwords come from WMF or WM-ES IPs? [13:28:11] Volker_E: ping ? [13:29:13] jem: Most recent ones are WMF, but older ones (that are still reccent) are WM-ES [13:29:57] I'm quite shocked then [13:31:29] So there are 53 failures in the last 3 hours [13:32:04] Then nothing until feb 12 at 9:00 UTC [13:32:30] Although many of those 53 are the five minute lockout [13:33:08] ok, ignoring throttling [13:33:57] Thanks, bawolff_, so I can try now? [13:33:59] 29 failures between feb 13 12:00 UTC and 14:00 UTC. then 13 failures at feb 12 9:00 UTC [13:34:47] yeah, none of the most recent failures were throttle related [13:35:14] Well, I'd like to check if there's some wrong config somewhere, but right now I have no clues [13:35:37] All the edits use the same function, which uses the same secret file... [13:36:22] I try again from WM-ES now [13:37:47] Ok, seems good [13:40:48] And now another fail :/ [13:42:24] bawolff_: I really don't understand, I'm seeing the debug of the parameters for the API, and the password is the same, it just changes the lgname from Jembot (ok) to jembot (fail) [13:44:20] And supposedly the first letter is not case sensitive... anyway, I'll try to change that... [13:44:39] yeah. Maybe API is picky somehow? That'd be odd [13:44:47] FWIW, everything in the logs use capital J [13:46:15] I changed to Jembot in the code but the debug still says jembot [13:46:43] And of course it failed again [13:47:10] I think you're back to hitting the more than 5 attempts in 5 minutes throttle [13:48:48] Ok, that's because I activated the crontab [13:48:56] Deactivated again [13:50:47] And now I see Jembot, correct password, but again "wait 5 minutes" [13:53:08] This is a little annoying, anyway, thanks for the help, bawolff_ [13:54:44] fwiw, i looked in a different logfile, and I can confirm that sometimes you login with jembot and sometimes Jembot [13:55:12] I have used a third server now and it seems Ok [13:55:48] So I'll do a few manual launchs, as I have to leave now [13:56:26] Maybe I can be in time for the technical hour in URC and get more help [13:56:31] in IRC* [13:56:57] You do seem right, that the password fail ones seem to correspond with using lowercase j [13:58:00] except the most recent failed wrong pass login at 2019-02-13T13:56:58 was using an uppercase J [13:58:07] so maybe that's just a coincidence [14:07:03] jem: maybe you are hitting captchas. I think failing captcha will result in wrong pass error [14:07:20] * bawolff not sure how captchas work from api [14:08:54] Logs suggest thats not the case [14:10:27] Captchas for a 390K edit account... that would be so strange [14:10:42] (now writing from a tablet) [14:12:45] The last manual launchs from the third server seem ok [14:30:30] The login process will send you captchas after a certain number of failures [14:30:48] I think 3 [14:31:06] But i think the tool labs ips are whitelisted [14:34:01] omg its a wild sumanah! [14:34:05] * bawolff_ waves [14:34:10] Hi bawolff_! how are you? [14:34:17] I'm good [14:35:05] I was in the museum of pop culture in Seattle a while back, and totally saw your name there [14:35:27] so this is possibly a ridiculous request, but do you have access to a quotes database where Andrew Garrett once said something about a cake vending machine as a very American thing? I looked in https://tools.wmflabs.org/bash/ and couldn't find it [14:35:38] bawolff_: oh nice :-) right, that interview about Star Trek [14:36:08] Hmm, was it in the old bugzilla quips db? [14:36:21] bawolff_: I thought it was. But maybe it's something in a staff-only space. [14:36:33] unfortunately bugzilla isn't a thing anymore and I don't know what happened to its quip db [14:37:02] I found out! The quips db went to https://tools.wmflabs.org/bash/ [14:37:11] But the cake thing is not there AFAICT [14:37:13] There's a big page at https://office.wikimedia.org/wiki/Bash that's staff only [14:37:23] Might be there then [14:37:24] I don't see andrew on it [14:38:08] https://www.mediawiki.org/wiki/Quips [14:39:01] Krinkle: I think that links to the same thing I just mentioned? Also, hi! [14:39:12] https://www.mediawiki.org/w/index.php?title=Quips&oldid=2100736 [14:39:39] Yeah, this shows it got imported to Bash in tools [14:39:43] (hi!) [14:40:28] Maybe I'll just email Andrew. "Hi, hope you are well, but the reason I am reaching out is that ... did you say a funny thing 10 years ago about a vending machine?" [14:40:45] wait [14:40:51] "When I first came to the US, I bought cake-flavored soda from a vending machine that took AMEX. Everything about that experience was American. " [14:40:57] THAT. THANK YOU. [14:41:08] I was looking for his fullname and werdna [14:41:11] It was under andrew [14:41:36] bawolff_: I vote you the hero of the hour. [14:41:39] https://office.wikimedia.org/wiki/Bash/archive#January_2011 (staff only) [15:00:36] Technical Advice IRC meeting starting in 60 minutes in channel #wikimedia-tech, hosts: @milimetric & @amir1 - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [15:30:35] Okay yet more template/CSS interactions [15:30:36] https://en.wikisource.org/wiki/Wikisource:Scriptorium/Help#Okay_why_does_parameterising_line-height_completely_stop_something_working? [15:30:55] line-height parameter is ignored for SPANs that aren't also blocks [15:31:11] Yet somene in writing the relevant template thought otherwise [15:31:14] (sigh) [15:31:23] *Someone [15:36:58] hello there [15:39:24] Hello superyetkin! [15:39:57] If I'm not back for the tech meeting, could phab T213616? [15:40:17] I'm happy to give access if needed. [15:42:42] Off now [15:50:18] Technical Advice IRC meeting starting in 10 minutes in channel #wikimedia-tech, hosts: @milimetric & @amir1 - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [15:59:14] hello world [15:59:27] hi [15:59:35] I'm here to help [15:59:54] I'm one of the https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting people [16:00:26] o/ [16:00:28] quick background: I'm on the Analytics team, I build and publish datasets and dashboards [16:01:12] I don't know if that is in scope, but https://commons.wikimedia.org/wiki/File:Edittools_JS_errors.png [16:01:14] And as of my background: I work in two projects: wikidata and ores [16:02:26] yannf: let me check [16:02:35] Can I see the code for edittools? [16:02:54] (Basically steps to reproduce the issue) [16:03:21] (also - everything is in scope :)) [16:03:45] rhinosf1: ill make a note to nag some people about that [16:04:12] It was sort of already on my todo list to nag some people about it [16:04:19] Hello, [16:04:19] I thought of working on the Special:ViewData to improve the UI and make it much more user friendly manner, for that I made a mock-up https://app.moqups.com/TdoAvwD2nF/view which is not so great though, So any suggestions or examples to make the ViewData much more userfriendly ? [16:04:44] Amir1, do you see Edittools above the editbox (in source mode) on Commons? [16:05:32] yannf: yup [16:05:42] it seems to be on for everyone [16:06:15] for me, it appears around once every 10 edits, with these JS erros [16:06:25] *r [16:06:48] Maybe load order related if its that intermittent [16:07:15] Chrome Version 71.0.3578.98 (Official Build) (64-bit) [16:08:28] yannf: okay. It's a little bit hard to reproduce, my gut feeling is that there is something with your enabled tools/custom js [16:08:30] the conflict [16:08:49] so 1- Try disabling all and enabling them one by one [16:08:53] Gopa: taking a look [16:09:11] :) [16:09:33] I'm not familiar with Special:ViewData, so I have some catching up to do first, but I could help with the UI [16:09:35] Bawolf - Thanks, I'll be on at some point [16:09:37] 2- if still it's not working with everything disabled. Put a debug=true at the end of your url and report the error to phabricator [16:09:39] Amir1, I ama pretty sure I didn't change my setup [16:09:54] it is like this for 2-3 days now [16:10:09] yannf: yes but it might be someone edited one of those gadgets, etc. [16:10:31] Maybe related to the onload shenagians in mediawiki:edittools.js [16:10:46] Gopa: which wiki is this enabled on so I can play with it [16:10:48] yannf: try with this https://commons.wikimedia.org/w/index.php?title=File:Edittools_JS_errors.png&action=edit&safemode=1 [16:11:08] bawolff has a point too [16:11:12] Special:ViewData is the cargo extension. [16:12:10] Amir1, no Edittools [16:12:29] Gopa: we have a design style guide that you can find at design.wikimedia.org (which has detailed resources) [16:12:40] Gopa: Also you can make it work with OOUI [16:12:49] I think Edittools crashes, so it does appear [16:13:19] Gopa: https://phabricator.wikimedia.org/project/view/24/ look at the column "Conversion to OOUI" [16:13:39] e.g. https://phabricator.wikimedia.org/T192099 [16:13:52] * Gopa Looking through [16:14:16] I dont even know if mediawiki:edittools.js is used though. So may be false lead [16:14:17] yannf: https://commons.wikimedia.org/w/index.php?title=MediaWiki:Edittools.js&action=history it's not changed in the past couple of months [16:14:19] I am trying to get output of the JS console [16:14:49] yannf: try with debug=true (https://commons.wikimedia.org/w/index.php?title=File:Edittools_JS_errors.png&action=edit&debug=1) [16:14:50] The current ui looks like https://ibb.co/QKz1rjc [16:15:18] It's already ooui, that's good [16:15:44] Err. Nevermind it is loaded from common.js [16:16:01] Amir1, no tool at all with debug=1 [16:16:17] Amir1: I think Special:ViewData is using OOUI for now. [16:16:17] what's the output in console? [16:16:26] I doesnt think* [16:16:41] Hmm, let me check the codebase [16:17:05] I mean, I doesn't think It is using OOUI now. [16:17:09] Sure :) [16:18:23] https://github.com/wikimedia/mediawiki-extensions-Cargo/blob/master/specials/CargoViewData.php [16:18:45] you're right, making it use ooui would help it align more with wikimedia design style guide [16:19:42] there's some light use of OOUI, https://github.com/wikimedia/mediawiki-extensions-Cargo/search?q=OOUI&unscoped_q=OOUI [16:19:44] do you have any idea to make it more user friendly ? May be somethings like auto filling or tokens method or something [16:20:15] Gopa: so this allows people to query any table or just tables that have data used in templates? [16:20:43] Yeah you are right :) [16:21:02] Gopa: Using HTMLForm and defining which type of input they are would help greatly https://www.mediawiki.org/wiki/HTMLForm [16:21:27] for example it has a dedicated type of page which has auto filing [16:21:57] HTMLTitleTextField: Textbox to take Page Name [16:22:08] https://www.mediawiki.org/wiki/HTMLForm/tutorial3#Class [16:22:14] Bawolf - Thanks for The help. It definitely doesn't show on Oversight just revdel (using visual diff). Let me know if you get an estimated fix date. [16:22:23] ^ Bawolff [16:22:31] agreed with Amir1 that using the style guide and OOUI elements would help a lot [16:22:39] Do you know any UI in any wiki such a way already? for Inspiration ! [16:22:57] Gopa: Moving pages is one of them [16:23:13] https://www.mediawiki.org/wiki/Special:MovePage/Manual_talk:Coding_conventions/PHP [16:24:04] Gopa: VisualEditor uses OOUI more heavily than any other project, so if you're looking for examples you'd probably find them there: https://github.com/wikimedia/mediawiki-extensions-VisualEditor [16:25:47] Yeah I already have VisualEditor and any interface had the implementaion of the autofilling? That gives the best services to the users. [16:26:08] milimetric: thanks. It's really good. Some demos can be found in https://doc.wikimedia.org/oojs-ui/master/demos/?page=widgets&theme=wikimediaui&direction=ltr&platform=desktop [16:27:29] Gopa: yeah, if you can generate a list of tables that the users can query, then you can auto-complete the Table input box. Then, when they tab out of there, you can query "desc the_table_they_chose" and auto-complete the Field(s) input box [16:28:35] You could also add a little info icon that you either click or hover to see the full list of columns listed in alphabetical order or something [16:29:12] you could also run a basic "select * from the_table_they_chose limit 10" to show them a sample [16:29:15] I know it's user maintained but anyone know anything about this https://en.wikipedia.org/wiki/User_talk:Scottywong#https://tools.wmflabs.org/jackbot/snottywong/cgi-bin/afdadminstats.cgi?max=250&name=Evad37_-_is_unavailable? [16:29:20] Oo okay :) [16:30:53] rhinosf1: it probably means the query is too heavy. If you get it all the time [16:31:00] Do you advice me to use any specific thing in making the mock up to propose the new UI? Generally how the Wikimedia's General mock ups are made ? [16:31:16] if it's a one time thing, just try to reload (it happens sometimes due to network issues) [16:31:26] rhinosf1: I agree, that query would time out, that join is really rough on enwiki [16:32:18] Amir1, I got the JS console https://commons.wikimedia.org/wiki/Commons:Village_pump/Technical#Edittools_JS_errors [16:32:31] Gopa: design.wikimedia.org is a good starting point IMO [16:32:43] Anything I can do on my end?? [16:32:56] page/revision join without timestamp filter. Basically any range greater than a few days to weeks on enwiki revision will most likely not work [16:33:21] Thank you Amir1 :) [16:33:42] Gopa: do you mean what tools should you use for drawing up the actual mockup? [16:33:54] Yes ! [16:34:00] Gopa: there's no real standard there, whatever tool you like, but the designers have some opinions, I believe Sketch is popular [16:34:30] rhinosf1: nothing unfortunately, you can contact the maintainer and ask them to improve the query optimization [16:34:47] but nothing much can be done [16:34:51] Oook thanks your insights milimetric [16:35:01] yannf: checking [16:35:08] rhinosf1: oh, I didn't see the user filter, maybe that's not so bad then. Lemme see [16:35:23] I've messaged the maintainer as linked above but they're not active [16:37:06] rhinosf1: I'm working on the query now to see if there's any easy fix. If there is we can just see where the repo is and send a patch [16:37:18] if not, you could always run the query in quarry and get your results manually [16:38:02] Let me know if you find anything if not, how would quarry work? [16:38:20] rhinosf1: what wiki were you working on? [16:38:28] AFD is not enabled everywhere [16:38:43] Amir1, there is clear error message about MediaWiki:Edittools [16:39:01] yes [16:39:11] enwiki [16:39:23] for whatever reason $toolbar = $( '#wpTextbox1' ); doesn't work [16:39:45] yannf: can you run "$toolbar = $( '#wpTextbox1' );" in your console and tell me what you get? [16:40:01] I'm trying to query AfD closes on Evad37 (as he's at RfA) [16:40:10] then run "$toolbar.wikiEditor" [16:41:21] Amir1, jQuery.fn.init {} [16:41:24] rhinosf1: actually, you can have higher timeout by querying the database directly through quarry.wmflabs.org [16:41:37] rhinosf1: have you worked with it? [16:41:39] __proto__: Object(0) [16:41:51] No Amir1 [16:42:07] yannf: it can't find your textbox :/ something has changed that [16:42:29] rhinosf1: is it okay if I write the query for you? [16:42:54] Definitely Amir1 [16:43:52] jQuery.fn.init [textarea#wpTextbox1.mw-editfont-monospace] [16:44:17] Amir1: I can mess with this query if you want [16:44:47] milimetric: sure thing! it's fun it doesn't have a limit, try adding that [16:45:11] rhinosf1: what would've been the startdate in the query you were running? That tool is trying to pass it in the regex for the page title [16:47:13] Last 2-3 months would probably be good enough - I think it was doing last 250 AfDs in the check [16:47:35] Hi, when it's possible I'd need some advice, bawolff knows about it [16:49:09] rhinosf1: right, but I'm not familiar with these page titles, so the query looks for titles that DO match Articles_for_deletion%, but DO NOT match Articles_for_deletion/Log/%<> [16:49:18] jem: how can we help? [16:49:25] so I was wondering what the "some-start-date-goes-here" should be to make the query work [16:50:03] Amir1: I'm having some very very strange issues when logging in with my bot with action=login [16:50:37] o/ [16:50:38] Lucas_WMDE: Do you feel comfortable with me to merge at least the non-icon change patches like https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/490358? [16:50:41] The current situation is that sometimes it is ok, sometimes it fails, with the same password and from the same host [16:50:59] Amir1, see pm [16:51:02] jem: are you using botpasswords? [16:51:17] No, just action=login with two steps [16:51:22] millimetric - Yes?? [16:51:32] It began to fail after problems with the server, and then it was throttled... now I just don't know [16:51:41] rhinosf1: I was wondering what the "some-start-date-goes-here" should be to make the query work [16:52:33] I still believe it is related to throttling because from a third server it has no problems [16:53:15] Volker_E: yeah, sure [16:53:17] But first in WM-ES server and this morning in Toolforge, it has [16:53:26] jem: It's very possible. We need to dig the logs. Can you send me username of the bot? [16:53:26] *since this morning [16:53:28] (but CI seems to be broken at the moment, due to the WMCS outage I guess?) [16:53:34] Yes Amir1: Jembot [16:53:35] (private message if you prefer) [16:53:42] No problem :) [16:53:42] okay [16:54:03] millimetric - Id be unsure - Amir1, you understand? [16:54:11] A few minutes ago I've been doing more tests, from WM-ES and from the third server [16:54:20] And from WM-ES it justs fails randomly [16:54:30] rhinosf1: I'm seeing examples like Articles_for_deletion/Log/2005_March_29 [16:55:13] it's weird, it's as if the query tries to exclude a single day of Article_for_deletion titles [16:55:30] maybe I'll just ignore that for now, and you can see what the results are without it [16:55:31] jem: In the logs there are two UAs that try to log in to that account [16:55:49] the first one succeeds the second is giving wrong passowrd [16:57:13] jem: so you have the right passowrd in one of the tools and wrong password in the other (or someone is trying to break into your bot's account) [16:57:52] Millimetric- so some data might be missing??? [17:01:12] rhinosf1: no, there will just be extra data [17:01:24] that check was in the negative, so it would exclude. Leaving it out means more will be included [17:01:30] rhinosf1: ok, I gotta run but I got your query here: [17:01:30] https://quarry.wmflabs.org/query/33384 [17:01:36] it looks like there are no results [17:01:55] Amir1: if you want to check my logic, feel free, but it looks like that user has no results for this query, meaning I guess no AfD? [17:02:08] rhinosf1: if you know of a counter-example, let me know and I'll see where the query went wrong [17:02:39] I need to go to a meeting right now [17:02:46] will check later. Sorry [17:03:25] (Thanks, Amir1, we're in private now) [17:04:09] millimetric- You could try against me as I should have a few closes [17:05:50] rhinosf1: is your wiki name also rhinosf1? [17:06:02] Yes millimetric [17:07:10] rhinosf1: no it's not :) https://en.wikipedia.org/wiki/User:Rhinosf1 [17:09:14] Oh yeah didn't think about caps. [17:09:32] ^milimetric [17:09:53] rhinosf1: how do you spell it exactly, because that one still doesn't exist [17:10:04] like, send me a link to your actual user page [17:10:56] https://en.wikipedia.org/wiki/User:RhinosF1 [17:14:56] Millimetric - Is that working? [17:22:59] Hi again, I have used botpasswords for my login problem but I'm still stuck or I don't understand it... [17:24:05] I just gave permissions to the bot, the page returned a new password and... this is it? the API code is still the same, two steps, just with the new password? [17:24:33] (I tried and I still get incorrect password, of course) [17:24:55] Hi, if I use two-factor authentication and my old cell phone with the Google Authenticator app is broken, is there a way to maintain my existing 2FA setup when reinstalling the app on my new phone, or do I have to disable and re-enable 2FA, and then set it up all afresh (I suppose that would work?)? Or do I have to do something else? [17:26:19] Need to go again, either ping me or use PM to follow up (PM might be easier) [17:27:17] Amir1: milimetric: thanks for helping Gopa! Gopa: Let me know when you want more feedback [17:28:13] Thanks Volker_E for reaching me Sure :) [17:28:17] Gopa: We've got SVGs with OOUI widgets as downloads in the Design Style Guide repo's 'resources' folder https://github.com/wikimedia/WikimediaUI-Style-Guide [17:28:23] There's also the Sketch files [17:29:07] WMDE designers also use Figma as alternative design tool [17:29:08] https://www.figma.com/ [17:29:10] But Sketch can be used only in mac os I guess ? [17:29:15] indeed [17:29:33] Figma is web-based and hence cross-platform [17:29:53] it has SVG import as well [17:30:29] Ookay I'm going through :) [17:33:14] Gopa: when looking at Special:ViewData screenshot https://ibb.co/QKz1rjc I would recommend to evaluate if all fields are needed from the beginning [17:33:15] Any help? This is getting worse :( [17:34:22] or if some of those could be hidden by default. General rule: Less user inputs needed leads to better form conversion and simpler usage [17:34:29] yeah all the fields are needed to pass the sql query. [17:34:50] Give them options to fill out when they really need them, not all the options there are [17:35:21] so are some of those fields pre-fillable, like you've said and dependent on others in the form? [17:36:12] No :) [17:37:50] but somethings like table names, fileds we can make the user autofillable if atleast the user types first two charecters of the Table_Name or such things. I hope you understood ? [17:38:34] jem: i think you need to use "@" as your password when logging in. where is the name you input in the "Bot name:" field, and is the generated password [17:41:39] MatmaRex: Thanks, I'll try [17:43:56] No, fail again :( [17:48:44] Gopa: I guess you meant autocomplete… yes, that would be an improvement [17:49:45] Gopa: if I understand you correctly, you're saying that every form input needs to be filled out before 'submitting' [17:50:15] btw, I'd consider renaming the button from 'submit' to 'View data' or 'View' [17:53:00] MatmaRex: After reading again, it seems that the user name must be changed to -jem-@Jembot, but the Jembot account still has the old password (I just did a web login), so who will be those edits assigned to? [17:53:56] Sorry Volker_E I expressesd autofilling in the wrong way, I actually ment to say, Lets assume the table name is "Employees", If the user just types 'Em', It has the particular input box has to autofill 'Employees' [17:55:02] Yeah Your Idea seems coool to replace "Submit" with "View data", Thanks :) [17:55:15] rhinosf1: ok, here's what I got as a result: [17:55:18] https://www.irccloud.com/pastebin/khhkx2Ug/ [17:55:41] jem: there are actually two ways to log in with a botpassword - username=username, password=botname@botpassword; or username=username@botname, password=botpassword. both of these will log you in as "username" (the '@' character is normally invalid in usernames). [17:56:09] (i forgot about the second way, i found the documentation after i already answered your previous question) [17:56:36] Ok, now I see, it works but the edits are assigned to -jem- [17:56:58] (I used the second way) [17:57:18] note that the botpassword on your main account is not related to your separate bot account [17:57:34] I'm noting that now [17:57:36] So I guess I have to use Special:Botpasswords from inside the Jembot account [17:57:38] you probably want to create another botpassword while logged in to your bot account [17:57:41] yeah [17:57:47] rhinosf1: so that's the same query but running for you. Running that with the other user you mentioned, Evad37, gives no results. That means that after October 1st, 2018, that user made no edits on pages called "Articles_for_deletion<>". Unless those pages were deleted since then, for which you'd have to run the same query but inside of the archive table. [17:58:35] rhinosf1: you can always edit this query: https://quarry.wmflabs.org/query/33384 by changing the user_id and the date [17:59:09] for example your user_id is "select user_id from user where user_name = 'RhinosF1';" --> 34741242 [17:59:27] (And now I understand why I could give permissions from my user account to my bot account) [18:00:10] Well... no, I see those permissions also appear now [18:03:30] Millimetric-that covers AfD edits not specific closes. [18:08:04] Evad37 makes little edits might have to widen search range. [18:09:11] (to that area) [18:10:30] Would it be possible to go back to 2014? [18:10:53] That's the last votes (not sure on close) [18:12:17] MatmaRex: Ok, things look good, but now it seems the second login with token isn't needed, but it is not clear for me when it is needed and when it isn't [18:36:21] Ok, MatmaRex, I think all is working now with BotPasswords... thanks again for the help :) [18:54:13] Volker_E: I have made a patch by taking your suggestion, but I always wonder why jenkins is always bad with me ^_^' [18:54:22] https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Cargo/+/490384/ [19:06:17] haa got it, I was in the old branch, cherry picked to the master now, fixed the problem :) [19:25:51] rhinosf1: yeah, you see where it says rev_timestamp >= '20181001000000'? Just change that to rev_timestamp between '20140101000000' and '20140701000000'. That would search the first 6 months of 2014, and you can do a similar thing to search the next 6 months. I would recommend searching 6 months at a time, that's what seems to be about on the border of what will execute quickly [19:26:19] rhinosf1: and you can play with the title you're searching for, the page_title like ... clause [19:46:27] Okay, what about looking for AfD closing. It would need to search for certain content being added/removed millipede [20:05:02] rhinosf1: if you need to search for pages being deleted, you can look in the archive table. If you have a very precise question you can write it on the Quarry talk page: https://www.mediawiki.org/wiki/Talk:Quarry [20:05:43] rhinosf1: if you write your questions well there, people can help you work on the query to run. Make sure to include a link to the query I sent you or any modified version of it that you're working on. [20:14:14] I might try there later in the week.