I am a Release Engineer on the Wikimedia Release-Engineering-Team.
Thu, Jul 12
I created an access token and replaced the stored password with the access token.
The password hasn't changed.
I've added 2factor to wmfphab on github
maybe we need to adjust content security policy?
Note that the rate limiting is disabled only temporarily. We need to remove the config from puppet to make it permanent.
Wed, Jul 11
I've disabled the rate limit because even after merging 7562c262da5699d61634ffb8e4ea3aab54a0048d we still saw regular users hitting the limit. I think the rate limiting code is buggy or somehow not working as intended.
I submitted a patch to raise the limits. I just need someone from sre to merge.
Tue, Jul 10
I changed the default edit policy here.
@atgo: I'm actually not sure why the aren't logged. I'll see what I can do.
Somehow a custom filter was applied but it didn't exist in the database, causing a 404. I'm going to look into changing the behavior when the filter cannot be found. A 404 isn't very helpful.
Looks good to me.
Why would "Task author, administrators, WMF-NDA" deny the author?
Fri, Jul 6
Indeed, I don't think we can whitelist labs IPs. The best we can do is somehow whitelist the API key that wikibugs uses. That's tricky to do, however, without revealing the api key publicly.
Thu, Jul 5
The problem with using PHIDs is that it makes testing difficult - on my test instance the PHIDs differ from production. I suppose I could fix it manually in the database though.
I'm not sure why this is happening.
This isn't technically feasible. The rate limit is based on IP and the throttle doesn't necessarily know which user is associated with an IP.
Tue, Jul 3
Mon, Jul 2
Sun, Jul 1
scap lints every single file regardless of whether it would ever be executed by unit tests. I don't think CI is quite as strict with the way things are linted?
Sat, Jun 30
D1074 will add the ability to set task types from herald rules.
It's just another field on the already long list of fields to fill out when creating a task.
Thu, Jun 28
@daniel: can you try again and see if it works better now? I changed the configuration on the "edit release" form.
- Currently all file uploads get stored in mysql database tables, not locally on the phab host. There shouldn't be a significant amount of traffic to the phabricator file store - it's mostly used for screenshots and whatnot.
- Replication across datacenters would indeed be a good thing. We aren't quite multi-datacenter with phabricator yet but that is a goal for the near future.