whipper cd rip reports accurate rip but whipper image verify reports NOT accurate rip

[pvtischler]

I have restarted my quest to rip my CD collection. I decided to use whipper because of the accurate rip feature. I have noticed with several of my CDs that the ripping process produces an accurate rip, but then when I run whipper to check the image the files are reported as not accurate. I have noticed that the disc Id and the accurate rip bin file are from different CDs.
For example, I am trying to rip an Alice Cooper, Killer CD. On the whipper cd rip call it identifies the CD as:

DEBUG:whipper.common.accurip:downloading AccurateRip entry from http://www.accuraterip.com/accuraterip/e/d/8/dBAR-008-000a88de-004746d3-7608a708.bin

But on the whipper image verify call it identifies the CD as:

DEBUG:whipper.common.accurip:downloading AccurateRip entry from http://www.accuraterip.com/accuraterip/e/b/7/dBAR-008-000a87be-00474134-7108a708.bin

I have complete debug logs, I just don't know how to upload them.

[pvtischler]

This is not an answer. These are additional comments... I noticed that the cue file has a partial reference to the AccurateRip database entry:

REM DISCID 7608A708

But it looks like during the "whipper image verify" processing it is recalculating the TOC incorrectly. The whipper cd rip log shows the following:

11775 DEBUG:whipper.image.table:leadout LBA: 166197
11776 DEBUG:whipper.image.table:cddb values: DiscID(offsets=[182, 13050, 28127, 65790, 81545, 92645, 109100, 134962], total_length=2215, track_count=8, playable_length=2215)
11777 DEBUG:whipper.image.table:cddb disc id debug: 7608a708 8 182 13050 28127 65790 81545 92645 109100 134962 2217

While the whipper image verify shows this:

377 DEBUG:whipper.image.table:leadout LBA: 166165
378 DEBUG:whipper.image.table:cddb values: DiscID(offsets=[150, 13018, 28095, 65758, 81513, 92613, 109068, 134930], total_length=2215, track_count=8, playable_length=2215)
379 DEBUG:whipper.image.table:cddb disc id debug: 7108a708 8 150 13018 28095 65758 81513 92613 109068 134930 2217

Something seems to be wrong. I have not dug into the code to figure out what is going on. I was hoping that I did not have to learn how this part of the code worked.