#709 ✓resolved
duncanSF

bid accounting: success not flagged in list of completed auctions

Reported by duncanSF | February 21st, 2009 @ 03:25 AM | in 2.1 Release

JBidWatcher executed a snipe, bought me a VoIP phone, and moved the auction to the "complete" tab. In the list there, the maximum bid was colored red and the collection of status icons showed only a camera. Looking at the list I would miss that it was successful.

Missing success could be a real problem with multisnipes.

The "Show information" dialog indicates a successful snipe. Does it mean a bid was placed or that the bid won?


Listing has ended. Events
Thu Feb 19 23:05:03 PST 2009: We appear to be waking from sleep; networking may not be up yet. (2) 
Fri Feb 20 09:36:47 PST 2009: Preparing snipe. 
Fri Feb 20 09:36:49 PST 2009: Done loading bid request, got form... 
Fri Feb 20 09:36:49 PST 2009: Loading bid request... 
Fri Feb 20 09:38:48 PST 2009: Submitting bid form. 
Fri Feb 20 09:38:48 PST 2009: Firing actual snipe. 
Fri Feb 20 09:38:49 PST 2009: Successfully sniped a high bid on SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ! 
Fri Feb 20 09:38:49 PST 2009: Done loading post-bid data. 
Fri Feb 20 09:38:49 PST 2009: Loading post-bid data. 
Fri Feb 20 09:38:49 PST 2009: Done submitting bid form.

The logfile around the time of the snipe, contains essentially the same lines in a slightly different order:


Fri Feb 20 05:12:52 PST 2009: JBidwatcher 2.0-800
Fri Feb 20 05:12:52 PST 2009: Sun Microsystems Inc. Java, version 1.6.0_11 on Windows Vista
Fri Feb 20 05:12:53 PST 2009: Loaded the appropriate driver.
Fri Feb 20 05:13:07 PST 2009: Connected to database jbdb (JBidwatcher DataBase)
Fri Feb 20 05:13:08 PST 2009: Auction information database already exists.
Fri Feb 20 05:13:08 PST 2009: Closed connection
Fri Feb 20 05:13:08 PST 2009: Database shut down normally
Fri Feb 20 05:13:08 PST 2009: Loaded the appropriate driver.
Fri Feb 20 05:13:09 PST 2009: Connected to database jbdb (JBidwatcher DataBase)
Fri Feb 20 05:13:09 PST 2009: Closed connection
Fri Feb 20 05:13:10 PST 2009: Database shut down normally
Fri Feb 20 05:13:11 PST 2009: Error setting up scripting: java.lang.NoClassDefFoundError: org/jruby/runtime/builtin/IRubyObject
Fri Feb 20 05:13:11 PST 2009: Loaded the appropriate driver.
Fri Feb 20 05:13:12 PST 2009: Connected to database jbdb (JBidwatcher DataBase)
Fri Feb 20 05:13:15 PST 2009: Loading listings from the database (30/53/53 entries, 64/73 auctions)
Fri Feb 20 05:13:16 PST 2009: Done with the initial load (got 30 active entries)
[...]
Fri Feb 20 07:02:14 PST 2009: 160315721649 (D-Link DVX-4010 Expandable SIP phone system w/ 10 phone) - Communications failure talking to the server.
Fri Feb 20 07:02:14 PST 2009: Failed to parse auction!  Bad return result from auction server.
Fri Feb 20 07:02:14 PST 2009: 160315721649 (D-Link DVX-4010 Expandable SIP phone system w/ 10 phone) - Failed to load from server!
Fri Feb 20 09:36:47 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Preparing snipe.
Fri Feb 20 09:36:47 PST 2009: Getting the sign in cookie.
Fri Feb 20 09:36:49 PST 2009: Done getting the sign in cookie.
Fri Feb 20 09:36:49 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Loading bid request...
Fri Feb 20 09:36:49 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Done loading bid request, got form...
Fri Feb 20 09:38:48 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Firing actual snipe.
Fri Feb 20 09:38:48 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Submitting bid form.
Fri Feb 20 09:38:49 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Done submitting bid form.
Fri Feb 20 09:38:49 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Loading post-bid data.
Fri Feb 20 09:38:49 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Done loading post-bid data.
Fri Feb 20 09:38:49 PST 2009: 400031144047 (SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 ) - Successfully sniped a high bid on SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 !
Fri Feb 20 09:38:49 PST 2009: Successfully sniped a high bid on SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 !
Fri Feb 20 13:01:29 PST 2009: Error loading URL (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=370161290535)
connect timed out

At least from this side of the curtain this looks related to ticket #696 (spelling corrected): "I've won 13 items [...] None is realized as won in the 'completed' tab."

No green checkmark, no green price.

duncan.

Comments and changes to this ticket

  • Morgan Schweers

    Morgan Schweers February 21st, 2009 @ 10:46 AM

    • State changed from “new” to “open”

    Greetings,

    It's possible; if you do a 'Show Information' on the ended item (the SNOM 300 SIP BASED VOIP BUSINESS PHONE above), what does it show in the 'High bidder' field?

    -- Morgan Schweers, CyberFOX!

    p.s. 'Successful snipe' just means that the bid was placed successfully; that's all it can know at snipe time. Whether you won or not is for later, when the auction actually ends.

  • duncanSF

    duncanSF February 21st, 2009 @ 03:29 PM

    Thanks for the clarification on 'successful snipe'.

    The 'High bidder' field in the output of 'Show information' is '(unknown)':

    
    SNOM 300 SIP BASED VOIP BUSINESS PHONE SNOM300 (400031144047) 
     
    Currently
    $26.00 (2 Bids)
    High bidder
    (unknown)
    Your max bid
    $29.92
    Shipping
    $11.50
    Insurance (optional)
    $11.50
    Seller
    donation4
    Listing ended at
    Fri Feb 20 09:39:02 PST 2009
    Listing has ended.
    

    In the auction details served from ebay after login today I see my account as the winner.

    
    Item location:	los angeles, CA, United States
    History:	2 bids
    Winning bidder:	duncan.campbell( 30)
    
    
    <tr><td nowrap="yes" width="25%" align="left"><span class="titlePurchase">History:</span></td><td width="100%" colspan="2"><span id="DetailsBidHistory"><a href="http://offer.ebay.com/ws/eBayISAPI.dll?ViewBids&amp;item=400031144047">2 bids</a></span></td></tr><tr><td align="left" nowrap><span class="titlePurchase">Winning bidder:</span></td><td colspan="2"><span id="DetailsHighBidder"><a class="findresulttitle" title="Bidder " href="http://myworld.ebay.com/duncan.campbell/">duncan.campbell</a><img src="http://pics.ebaystatic.com/aw/pics/s.gif" width="4" border="0">( <a href="http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedback&amp;userid=duncan.campbell&amp;iid=400031144047">30</a><img align="absmiddle" border="0" height="25" width="25" alt="Feedback score is 10 to 49" title="Feedback score is 10 to 49" src="http://pics.ebaystatic.com/aw/pics/icon/iconYellowStar_25x25.gif">)<span> <img src="http://pics.ebaystatic.com/aw/pics/s.gif" width="4" border="0"></span></span></td></tr><tr><td colspan="4"><hr class="hrwhite"></td></tr>
    
  • Morgan Schweers

    Morgan Schweers February 21st, 2009 @ 05:54 PM

    Greetings,

    It's the High bidder: (unknown) that's the problem, unfortunately.

    I don't know why JBidwatcher wasn't able to retrieve the winning bidder at the end. That's definitely a problem.

    -- Morgan Schweers, CyberFOX!

  • duncanSF

    duncanSF February 21st, 2009 @ 06:06 PM

    From the activity log JBW doesn't seem to have tried to look up the auction since submitting its snipe. The 'Show information' info remains stale.

    I'm not a coder but this looks like a race condition between submit snipe - check for win - update status and note passing of auction close - move to completed

    Auctions sitting in 'completed' appear to be no longer updated, whether or not a bid was placed. The auction ends between the snipe and the check and the check never happens.

  • Morgan Schweers

    Morgan Schweers February 21st, 2009 @ 06:27 PM

    Greetings,

    I can understand how it might seem like that, but an auction shouldn't be getting marked as 'complete' unless it's updated after the end of the auction.

    It's during the update step in fact, after the completed check that it checks the high bidder, and if it is the current user it clears the rest of the multisnipe.

    The problem here appears to be that it's not parsing the high bidder correctly out of the auction at the end-step. I'm wondering if maybe they show a different piece of text to identify the high bidder during the first few minutes after an auction ends... If you update that auction (right-click and 'Update', or double-click on the item), does it then pick up the correct high bidder?

    -- Morgan Schweers, CyberFOX!

  • duncanSF

    duncanSF February 21st, 2009 @ 11:43 PM

    Yes, it does. Right-click and update on that auction did indeed add the green checkmark and the blue P and changed the max bid text color from red to blue.

    I'm on a Windows laptop today so no zless but here are the before and after files from auctionsave:

    
    02/20/2009  09:39 AM            18,476 400031144047_aftersnipe.html.gz~
    02/21/2009  11:23 PM            19,075 400031144047_nextday.html.gz
    

    duncan.

  • duncanSF

    duncanSF February 21st, 2009 @ 11:44 PM

    (one file per comment - here's the second one)

  • Morgan Schweers

    Morgan Schweers February 22nd, 2009 @ 12:27 AM

    Greetings,

    Errrrrgh; the after-snipe one is the 'new' format eBay page, and it snapshotted at 0sec(!), not after the auction was over. I'm also a little shocked to see that the newest new-format page doesn't actually have a 'high bidder' field if you're the high bidder... :(

    Instead it shows a text box at the top, mentioning that you're the high bidder.

    That's pretty bad; eBay's evidently still changing things on that page, and injecting the beta version randomly into some percentage of the view item pages.

    -- Morgan Schweers, CyberFOX!

    p.s. By the way, Best Use of Cached Auctions Ever! I hadn't even thought of that...

  • duncanSF

    duncanSF February 22nd, 2009 @ 01:52 AM

    Huh. The snaps are from (after the snipe but before the close) and from (just now), after I called for an update.

    Maybe someone with the same symptom can post snapshots before updating.

    And thank you!

  • Morgan Schweers

    Morgan Schweers February 22nd, 2009 @ 03:33 PM

    (from [822]) When setting a snipe, mark the item that is set to be updated 30 seconds after the end of the auction, to try and capture the winning bidder information with a little more certainty. JBidwatcher usually does this implicitly, by virtue of updating until it detects that it's completed, but this makes it explicit. Should help with [#709].

  • The_Ln2
  • The_Ln2
  • Morgan Schweers

    Morgan Schweers February 22nd, 2009 @ 11:36 PM

    Greetings,

    @The_Ln2 - Yours was a win, though, as far as I can tell, and you didn't have any subsequent multisnipes that fired?

    By the way, Ico is an awesome game. :)

    -- Morgan Schweers, CyberFOX!

  • duncanSF

    duncanSF February 23rd, 2009 @ 03:07 AM

    "When setting a snipe, mark the item that is set to be updated 30 seconds after the end of the auction"

    While solving the issue for the single snipe case, this solution sets a fairly large window of danger in the multisnipe case and makes troubleshooting the root problem (didn't find what we were looking for in the eBay page) more difficult by writing over the confusing page in the cache.

    Perhaps confusing responses from eBay could be renamed or otherwise flagged for later inspection. The flag should appear in the completed auction listing (another status icon?) or the user is likely never to notice.

    Or not. :)

  • Morgan Schweers

    Morgan Schweers February 23rd, 2009 @ 03:15 AM

    Greetings,

    It shouldn't be that large a window of danger; the 'last update' typically should happen between 0 and 59 seconds after the end of an auction anyhow. This just should ensure that.

    JBidwatcher tries to warn about dangerous multisnipes, that is multisnipes that are too close together for JBidwatcher to be able to adequately know the status of one before the next's snipe is to fire.

    I am continuing to work on improving the handling of eBay's potentially confusing responses, but in the mean time the 2.0.1 version is better enough than 2.0 to warrant a release to help folks who are frustrated now.

    -- Morgan Schweers, CyberFOX!

  • Morgan Schweers

    Morgan Schweers May 16th, 2009 @ 03:58 AM

    • Tag changed from 2.0, bug, snipe to 2.0, @moved, bug, snipe
    • Milestone changed from 2.0 Full Release to 2.1 Release

    [milestone:ID#38598 tagged:"@moved" bulk edit command]

  • Morgan Schweers

    Morgan Schweers February 14th, 2010 @ 01:10 AM

    • State changed from “open” to “resolved”
    • Tag changed from 2.0, @moved, bug, snipe to 20, @fixed, @moved, bug, snipe

    Greetings,

    This is believed to be fixed. Either in some earlier release, the current (2.1pre5), or a soon-to-be released version. If the problem still occurs with 2.1pre5 (or a the latest, if a newer version has been released), please re-open.

    -- Morgan Schweers, CyberFOX!

    {triaging}

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

People watching this ticket

Referenced by

Pages