Subject: Re: [htdig3-dev] a couple of bugs I've found with beta 2
From: Arthur Prokosch (email@example.com)
Date: Wed Aug 09 2000 - 13:53:22 PDT
On Wed, 9 Aug 2000, Geoff Hutchison wrote:
> Thanks for your bug reports--there have been a few bugs reported in the
> betas, but we're only starting to get a significant number of them. I'm
> going to sit down tonight and see what progress I can make on a 3.2.0b3.
> It would help if someone would start to work in the existing patches.
> Have you tried later versions beyond 3.2.0b2?
only quickly, to test whether the AND bug was present there too. since
the project isn't using most of the features that trigger the bugs I
listed, I'm a little loathe to leave my employer with snapshot code
(although they're going to have to bite the bullet and revise my setup at
some point anyhow)...if I have time the next few days, I'll give it a try.
> > - some error conditions result in an error message followed by what seems to
> > be an attempt to output an excerpt (when there are obviously no documents).
> > This results in gibberish (sometimes fragments of htdig.conf, sometimes what
> This is very strange--it sounds like a memory corruption bug, but it
> hasn't been caught by any of the leak toolkits (e.g. Purify) we've used so
> far. Further testing will be needed, especially after we're code complete.
when you get an error message, is can <blockquote><strong> be found
_anywhere_ in the resulting html?
> > - when using long.html and short.html (as opposed to the built-in formats or
> > a custom format) to display results, certain queries will say "results 1-x
> > shown" but not show any results. Which query produces this seems
> > unpredictable, but the same query will always either return a "blank list"
> > or return normally.
> This sounds quite bizzare, espcially since you say its not consistent. It
> may be related to a memory leak.
What I meant to say is that it's consistent within one query string, but I
couldn't figure out the rhyme or reason that governed which query strings
> > - This is more of a feature request... a search for '"phrase with prefix*"'
> > doesn't currently get expanded like 'prefix*' does. This might seem to go
> > against the whole idea of an exact phrase, but would be useful at least in
> > one thing I'm doing.
> For right now, phrase searching will not include fuzzy matching. However,
> the new ParseTree system will make it easier for people to add this sort
> of thing. Each match method will be a distinct class and will receive a
> call to "expand" based on a list of fuzzy types.
spiffy. I look forward to it.
> [many other bugs already reported and thought to be fixed]
> In general, it helps if bug reports are done separately so they can be
> forwarded to the bug DB.
is there a way to search the DB for bugs reported, say, only for the 3.2
To unsubscribe from the htdig3-dev mailing list, send a message to
You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Wed Aug 09 2000 - 03:53:24 PDT