That is a good point. I should move this to a backlog
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 8 2020
Oct 7 2020
Oct 6 2020
@Aklapper Not yet! That is going to be some upcoming phabricator tickets. :)
Ah sorry.
Oct 5 2020
Thanks @ACraze. I am talking to legal about it. They'll have the final say.
Hey! Yep, the modeling work needs to be completed first.
Oct 2 2020
can do!
I just had to do another service restart.
Oct 1 2020
@klausman @kevinbazira @ACraze My draft of the heavy wing product plan is complete. Can you all read it over the next few weekdays and add feedback to the doc.
No objection from me. The ORES data referred to in this ticket is not sensitive or PII.
Sep 30 2020
I'm going to close this ticket because the issue is being caused by Wikimedia Enterprise and will be resolved soon enough that this script isn't required.
I think the even simpler solution would be to change payment method to a Wikimedia credit card, that would remove any individual's liability if something goes wrong.
Sep 29 2020
can do!
Nope no deploys have happened recently. It has been happening every few hours since the 24th
If nobody else has worked on this yet I can take it.
Sep 28 2020
@Ladsgroup Let's figure out a way to get your personal paypal out of there. That is unfair to you and a vulnerability to the system. Now we have about 10 different reasons to have our call!
Sep 27 2020
Any ideas on causes and solutions @Halfak?
I've sudo service uwsgi-ores restart on all ORES200x boxes again. This fixes the problem temporarily (~24 hours)
and tomorrow we'll start on a permanent solution
Sep 26 2020
It started happening again, I went into each Ores200X box and manually sudo service uwsgi-ores restart to restart the service.
every time it starts at 16:00
Sep 24 2020
I am not certain what this ticket is about so I'll admit I have no thoughts smart or otherwise. Give me a bit to dig into the ticket discussion and figure it out
I've reopened it. We have been clearing out the backlog and this must have gotten caught up in it. Apologies from me
@Ghassanmas Huge thanks for the offer to help. To give context, we are planning on retraining all the models in the future from new data which would solve this particular task.
@kevinbazira where did we end up with this?