Snipe failing to check current price before snipe
|
|
I just got the program 2 days ago and I love it. Today I noticed something of a bug/annoyance. Here is the scenario: I placed a snipe for an item with 15 seconds left before the auction for $40 and the current price was $28 about 30 minutes before the auction ended (12:25:37am). When jbidwatcher went to place the snipe I got an Unknown Error message. I figured out that jbidwatcher doesn’t check to see if the current price is above the snipe price, it will still place the snipe and ebay will send an error that the bid is to low (I bid $40 when the current price was $52) which ultimately caused the Unknown Error. This was the error text from ebay: “The following must be corrected before continuing: Enter US $53.00 or more” and this was the log from jbidwatcher (Item name and ID replaced with xxxxxxxx): Thu Jun 19 12:23:00 EDT 2008: Loaded the appropriate driver. Thu Jun 19 12:25:00 EDT 2008: Thu Jun 19 12:25:00 EDT 2008: xxxxxxxxx (xxxxxxxxxxxxxxxxxxxxx) – Unknown error sniping on xxxxxxxxxxxxxxxxxxxxx |
|
|
Greetings, There are several things that join forces to make not checking the price in advance the right decision…
That said, JBidwatcher should definitely be recognizing an underbid situation. A quick look tells me that the issue is the data type eBay is serving its pages with has changed, and JBidwatcher wasn’t using the appropriate content-type. This led to garbage characters in the stream… I’ll poke at it, and hopefully have a fix at least checked in (although I’m not sure when my next release is) soon. The core idea is that JBidwatcher should have recognized the underbid, and not repeatedly tried to snipe… — Morgan Schweers, CyberFOX! |