Hi Brent,

What about:
a) Not storing the post files (1234.txt) if an error occurs
b) Simply looking for "gaps" in the numbering and retry those if the user
chooses to
E.g., this could work along the lines of: when BFAV starts it looks at the
posts it has and if it encounters any gaps it knows that there are things to
retry. If the user choose to, it can retry to load them (one of my problems
was that even when I choose to load updates they still didn't show up).

Cheers,
  - Andreas

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org 
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] On 
> Behalf Of Brent Vukmer
> Sent: Thursday, June 26, 2003 6:59 PM
> To: The general-purpose Squeak developers list
> Subject: RE: [BUG] BFAV not showing all posts (was: RE: 
> [Squeakfoundation]Shepherding large enhancements)
> 
> 
> 
> > 
> > I've just noticed that this can be incredibly hard if you 
> > don't see all of the appropriate messages. Looking for a 
> > specific set of enhancements (namely, Anthony's changes) I 
> > found absolutely nothing showing up in BFAV. Going to the 
> > SQFIXES archives showed me that the posts _were_ listed there 
> > and looking at the email-repository I found that the contents 
> > of the post in question simply said "an error occured... 
> > server not responding".
> > 
> > So it seems as if (that version of?) BFAV will simply drop 
> > messages if the server is not responsive. I just dumped the 
> > entire archive and reloaded it from scratch and (looking over 
> > all the posts manually) it seems that this time things went 
> > well (e.g., no server errors) but if it hasn't this bug 
> > should be fixed. It's very hard to review fixes if you don't 
> > even see them
> > ;-)
> > 
> 
> Crud.  Thanks Andreas.  This is an issue for all BFAV 
> releases.  I have
> been aware of this issue, and thinking about it, but haven't put a lot
> of work into it yet.  I've put it off mainly because I'm worried about
> introducing bad complexity to the "load-updates" process.  
> Right now the
> load-updates process *does* create a list of "retry" uids, but doesn't
> do anything with them.
> 
> I'm not sure what the simplest solution is.  How about the BFAV:
> (1) Have the load-updates process do one pass through the 
> retry uids.  
> (2) Provide a "check for gaps" button that reports any 
> missing uids, and
> offers to try and download 'em? 
>