Xapian discuss - Feb 2010 - xapian.DocNotFoundError: regression?

Hello,

I've installed xapian-core 1.1.3 and xapian-bindings 1.1.4 from the
tarballs announced by Olly the other day.  With these versions,
Enquire.get_mset() seems to consistently be raising
xapian.DocNotFoundError.

I've attached a small test case which reproduces this.  The same test
case works fine with 1.0.16 (not the latest 1.0.x, but it's what I had
installed).

Program output with 1.1.3 (core) / 1.1.4 (bindings):
        
        tack at orion:~$ rm -rf xapdb/; python xaptest.py 
        Traceback (most recent call last):
          File "xaptest.py", line 23, in <module>
            print enquire.get_mset(0, 10)
        xapian.DocNotFoundError: Document 2 not found


Program output with 1.0.16:

        tack at orion:~$ rm -rf xapdb/; python xaptest.py 
        Xapian::MSet(Xapian::MSet::Internal(firstitem=0,
        matches_lower_bound=10, matches_estimated=10,
        matches_upper_bound=10, max_possible=0.047060994820388071802,
        max_attained=0.023530497410194035901, Xapian::MSetItem(1,
        0.023530497410194035901, ), Xapian::MSetItem(2,
        0.023530497410194035901, ), Xapian::MSetItem(3,
        0.023530497410194035901, ), Xapian::MSetItem(4,
        0.023530497410194035901, ), Xapian::MSetItem(5,
        0.023530497410194035901, ), Xapian::MSetItem(6,
        0.023530497410194035901, ), Xapian::MSetItem(7,
        0.023530497410194035901, ), Xapian::MSetItem(8,
        0.023530497410194035901, ), Xapian::MSetItem(9,
        0.023530497410194035901, ), Xapian::MSetItem(10,
        0.023530497410194035901, )))

Should I report a bug, or have I neglected to take note of some relevant
API changes?

Thanks,
Jason.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xaptest.py
Type: text/x-python
Size: 568 bytes
Desc: not available
URL:
<http://lists.xapian.org/pipermail/xapian-discuss/attachments/20100218/70c33c63/attachment.py>

On Thu, Feb 18, 2010 at 10:53:08AM -0500, Jason Tackaberry
wrote:
> I've attached a small test case which reproduces this.  The same test
> case works fine with 1.0.16 (not the latest 1.0.x, but it's what I had
> installed).
It works for me with trunk, and nothing relevant has change since 1.1.4
that I can see.
> Should I report a bug, or have I neglected to take note of some relevant
> API changes?
It's not an API change.

I wondering if it is picking up the wrong xapian library, which could
cause odd problems.  What does this report (_xapian.so is the compiled bit of
the Python module, you may need to adjust the directory path):

ldd /usr/lib/python2.5/site-packages/xapian/_xapian.so

Assuming that your platform has ldd that is - what platform is this?

Cheers,
    Olly

On Fri, 19 Feb 2010 20:12:04 -0000, Jason Tackaberry <tack at urandom.ca>
wrote:
>
> Linux (Ubuntu 8.04).
I had this problem with a recent version of trunk earlier this week.
`delve -dt <aterminthedatabase>` would list a docid found in the
postlist for that term, but then show an error when trying to pull the
document data, saying that the document with that docid didn't exist.

Ubuntu 8.04 has gcc/g++ 4.2 as the default version. Try it with 4.1 or
4.3 (4.1 has the advantage of being in 8.04's apt; 4.3 worked for me
in Debian sid); that fixed the problem for me (after some dead ends
down other options).

-- 
Munchkin