Bug#966649: Request for feedback on upload_history re-implementation

2020-08-22 Thread Andreas Tille
Hi Asheesh, On Sat, Aug 22, 2020 at 11:21:55AM -0700, Asheesh Laroia wrote: > You noticed that the date column was an integer. That's fixed now; if you > update from git, and if you delete upload_history.sqlite on your machine, > and re-run the tool, the upload_history column will use a datetime

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-22 Thread Asheesh Laroia
Hi Andreas! You noticed that the date column was an integer. That's fixed now; if you update from git, and if you delete upload_history.sqlite on your machine, and re-run the tool, the upload_history column will use a datetime for the date column. It won't do many HTTP queries, so it's peaceful

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-21 Thread Lucas Nussbaum
On 21/08/20 at 00:04 -0700, Asheesh Laroia wrote: > Great! > > It sounds to me like if we use the *mtime* of /srv/ > udd.debian.org/email-archives/debian-devel-changes/debian-devel-changes.current > (but not its contents), that would smoothly and solidly overcome the > worries about unnecessary

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-21 Thread Asheesh Laroia
Great! It sounds to me like if we use the *mtime* of /srv/ udd.debian.org/email-archives/debian-devel-changes/debian-devel-changes.current (but not its contents), that would smoothly and solidly overcome the worries about unnecessary polling. If the file's mtime is the same as the last time the

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-21 Thread Lucas Nussbaum
Hi, On 20/08/20 at 22:55 -0700, Asheesh Laroia wrote: > Hi Lucas! > > I'm rereading this, and I have a follow-up question. > > It looks to me, based on reading the bug carefully, that /srv/ > udd.debian.org/email-archives/debian-devel-changes/debian-devel-changes.current > on ullmann

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-20 Thread Asheesh Laroia
Hi Lucas! I'm rereading this, and I have a follow-up question. It looks to me, based on reading the bug carefully, that /srv/ udd.debian.org/email-archives/debian-devel-changes/debian-devel-changes.current on ullmann successfully receives any new emails to debian-devel-changes. Is that accurate?

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-20 Thread Asheesh Laroia
On Thu, Aug 20, 2020, 05:45 Lucas Nussbaum wrote: > Hi Asheesh, > Hi! :) > > I think that the changes compared to the current table structure should > be minimized, to avoid rewrite all tools that use this data. > Improvements are welcomed of course, but please don't make changes if > there's

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-20 Thread Lucas Nussbaum
Hi Asheesh, On 19/08/20 at 23:03 -0700, Asheesh Laroia wrote: > Hi Andreas & Lucas & all, > > Lucas -- I'm making progress on re-implementing this. I'd love your input > by email or IRC about my approach, but if you're busy, feel free to ignore > this and I'll mention you again when I submit a

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-20 Thread Andreas Tille
Hi Asheesh, I'm currently testing your code from the git repository. Interestingly it also respects future ;-) : ... Computed upload history for 2020-05 Computed upload history for 2020-06 Computed upload history for 2020-07 Computed upload history for 2020-08 Computed upload history for

Bug#966649: Request for feedback on upload_history re-implementation

2020-08-20 Thread Asheesh Laroia
Hi Andreas & Lucas & all, Lucas -- I'm making progress on re-implementing this. I'd love your input by email or IRC about my approach, but if you're busy, feel free to ignore this and I'll mention you again when I submit a patch. Andreas -- The codebase at