[03:31:33] legoktm: user [17:32:56] Reedy, is "idprivatewikimedia" correct dbname for wiki sitting at id-private.wikimedia.org? It is being created because they have one namespace in their current wiki (to be decommissioned) that isn't readable by general public, with WMF config, it isn't possible, so I'd advice to use additional wiki. Thank you in advance! [17:33:30] I think - becomes _ [17:33:52] Also, I'm not sure about creating more private wikis with a different naming scheme... [17:34:03] Different than what? [17:34:08] What solution would you suggest? [17:35:11] I don't know. We don't really host many non WMF private wikis [17:36:41] Well, at least https://noboard-chapters.wikimedia.org/ exist, it is for the board's use. [17:37:35] Yeah... It's not common [17:38:08] If we have no problem with hosting one wiki for chapters (no matter if public, fishbowl or private, there's at least 1 chapter wiki in each mode), why we should prohibit another wiki, when there's a reason for it? Maybe there's a reason for not having more than 1 wiki per chapter, but I cannot find it :) [17:38:36] Well, even chapter wikis hosted by the WMF isn't that common as chapters themself. [17:38:43] How much private stuff do they even have? [17:40:09] ~2000 pages are in private namespaces [17:40:24] I have an account on their current wiki, but..password reset didn't came, so I cannot tell more now. [17:41:18] You can compare it with ~3000 pages that are public [17:45:08] It's not a hard no from me or anything, just might need a bit more thinking about [17:47:10] Hmm... Anyway, do you think I should rename idprivatewikimedia to id_privatewikimedia in patches I pushed for review? [17:48:09] I think id-private for the domain, but use id_private for the dbname [17:48:13] IIRC we s/-/_/ [17:48:21] look at noboards_chapter in the dblists etc [17:48:47] Ok, will do. Thank you, anyway. [17:49:14] Regarding the thinking part, I just cannot find out any other solution, if I don't count hosting a separate private wiki themselves or not protect sensitive info anyway. [18:14:27] Hello, gerrit's main page throws "'is:wip' operator is not supported by change index version" error. Pushing and viewing individual patchsets works fine. [18:14:50] I also get a warning when pushing, saying "remote: Pushing to refs/publish/* is deprecated, use refs/for/* instead". [18:15:03] (I use git-review) [18:18:41] paladox: ^ [18:18:50] Hi, this is known [18:18:57] chad has started the online reindexer [18:19:00] but will take time [18:19:05] to prevent overloading the db [18:19:56] Ok, I just wanted to be sure somebody know about it :) [18:59:33] Are Meta-wiki regulars here? Please recommend a venue to discuss such things as JS gadgets (or user scripts) and MediaWiki API. [19:03:55] qq[IrcCity]: an on-wiki location? https://meta.wikimedia.org/wiki/Tech works [19:07:52] yes, on-wiki. Good suggestion. [19:22:25] [[Tech]]; Incnis Mrsi; /* Integration of CentralAuth into Gadget-markblocked.js or similar */ new section; https://meta.wikimedia.org/w/index.php?diff=18113304&oldid=18110394&rcid=11978273 [22:23:49] paladox, is it still supposed to be showing the is:wip error? [22:23:55] yep [22:24:01] reindexing is taking a long time [22:24:12] why is a reindex being run? [22:24:25] is that like a regular (ish) thing? [22:24:26] Krenair because it has to after a upgrade [22:24:28] yeh [22:24:29] ah [22:24:37] though we are doing it online [22:24:40] with one thread [22:24:41] do we know roughly how long this takes? [22:24:47] can take hours [22:24:53] possibly more then offline [22:24:54] well so far it has taken hours :) [22:25:02] yeh but more hours :) [22:25:05] ... I assume the 'with one thread' is not something we chose willingly [22:25:26] i think so we did that to prevent overloading the db when we upgraded from 2.13 -> 2.14 [22:25:33] meh [22:25:38] guess I'll have to be patient [22:25:47] but luckley that problem is from the past [22:25:51] we use notedb now [22:26:00] so once it's migrated all changes to notedb [22:26:07] the db will have very low traffic [23:16:39] (realised it still had Known issues from the other day)