#1000 Unknown error sniping

[ghostechoes]

$ java -Xmx512m -jar JBidWatcher-1.0.jar
Mon Oct 02 02:59:44 GMT 2006: Mon Oct 02 02:59:42 GMT
2006: 220031470815 ((7) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Preparing snipe. (1)
Mon Oct 02 02:59:46 GMT 2006: Mon Oct 02 02:59:46 GMT
2006: 220031470825 ((6) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Preparing snipe. (1)
Mon Oct 02 02:59:47 GMT 2006: Mon Oct 02 02:59:47 GMT
2006: 220031470834 ((5) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Preparing snipe. (1)
Mon Oct 02 02:59:49 GMT 2006: Mon Oct 02 02:59:49 GMT
2006: 220031470827 ((5) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Preparing snipe. (1)
Mon Oct 02 03:01:43 GMT 2006: Mon Oct 02 03:01:43 GMT
2006: 220031470815 ((7) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Firing actual snipe. (1)
Mon Oct 02 03:01:43 GMT 2006: Mon Oct 02 03:01:43 GMT
2006: 220031470815 ((7) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Unknown error sniping on (7) - #4 SPLINE - 6 point NAME
BRAND INDUSTRIAL SOCKETS (1)
Mon Oct 02 03:01:45 GMT 2006: Mon Oct 02 03:01:45 GMT
2006: 220031470825 ((6) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Firing actual snipe. (1)
Mon Oct 02 03:01:45 GMT 2006: Mon Oct 02 03:01:45 GMT
2006: 220031470825 ((6) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Unknown error sniping on (6) - #4 SPLINE - 6 point NAME
BRAND INDUSTRIAL SOCKETS (1)
Mon Oct 02 03:01:46 GMT 2006: Mon Oct 02 03:01:46 GMT
2006: 220031470834 ((5) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Firing actual snipe. (1)
Mon Oct 02 03:01:46 GMT 2006: Mon Oct 02 03:01:46 GMT
2006: 220031470834 ((5) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Unknown error sniping on (5) - #4 SPLINE - 6 point NAME
BRAND INDUSTRIAL SOCKETS (1)
Mon Oct 02 03:01:46 GMT 2006: Mon Oct 02 03:01:46 GMT
2006: 220031470827 ((5) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Firing actual snipe. (1)
Mon Oct 02 03:01:46 GMT 2006: Mon Oct 02 03:01:46 GMT
2006: 220031470827 ((5) -
#4 SPLINE - 6 point NAME BRAND INDUSTRIAL SOCKETS) -
Unknown error sniping on (5) - #4 SPLINE - 6 point NAME
BRAND INDUSTRIAL SOCKETS (1)

[Sinbios]

Logged In: YES
user_id=1633240

Was the snipe over $500? It may be the same problem as 1582571.

[ghostechoes]

Logged In: YES
user_id=1611016

No, the snipes were not over $500. All of the snipes were
pretty small, maybe $35 max and most were smaller than that.
Nobody else bid on these auctions, so the items did not sell.

[Nobody/Anonymous]

Logged In: NO

I just had the same problem with 1.0 on ebay.co.uk. Tiny amount (approx $2USD), the snipe fired at the right time
according to the log, and I was synced & cookie'd (an hour prior anyway). I haven't used JB for a couple of weeks
or so, but this never happened before. Details:

Fri Nov 10 19:43:44 GMT 2006: Preparing snipe.
(1) Fri Nov 10 19:45:45 GMT 2006: Firing actual snipe.
(1) Fri Nov 10 19:45:46 GMT 2006: Unknown error sniping on <item> (1)
--
gl

[ghostechoes]

Logged In: YES
user_id=1611016

I just got the "unknown error sniping" again yesterday, auction 290046437936.
Looking at the bidding, my bid actually made it to the auction. I had to shut
down my computer and run to catch a plane, so I was not able to capture
the output or do any investigation.

[Nobody/Anonymous]

Logged In: NO

.. update from my earlier report, like ghostechoes I just found that the snipe actually got through, I just didn't
win it.
--
gl

[Nobody/Anonymous]

Logged In: NO

... update2, another snipe just completed succesfully. I won this one, maybe the (fake) error is related to losing?
--
gl

[Morgan Schweers]

Logged In: YES
user_id=19745

Greetings,
Right now if your bid isn't high enough, instead of letting
you know that, JBidwatcher is saying that an unrecognized
error occurred. This is because (get this!) eBay changed
the text from, 'You have been outbid' to 'You've been
outbid'. *sigh*

I want to get this fixed up and out, but it's going to take
a little bit as work (and the upcoming Seattle MindCamp) is
keeping me hopping. (The issue isn't the change; I've
already made that. The issue is doing a full release, which
takes time.) I'm also dithering on whether to adjust the
way it recognizes these messages, so that I can put updates
into the update XML that fixes future changes as well.

Anyhow, it only affects auctions that weren't bid high
enough; the bids should still be going through. If you're
worried, you can always 'View last error' in the auction
context menu to see what happened.

Sorry about the confusion folks!

-- Morgan Schweers, CyberFOX!

[ghostechoes]

Logged In: YES
user_id=1611016

It would help a lot if the code would print out some or all of the ebay message that is not recognized. That way we'd have a better
clue as to what was going on if/when this happens in the future.

[Morgan Schweers]

Logged In: YES
user_id=19745

Greetings,
That's what 'View Last Error' is for. It captures the
entire ebay message that isn't recognized.

It goes away when you close JBidwatcher, though.

-- Morgan

[Morgan Schweers]

Logged In: YES
user_id=19745
Originator: NO

Greetings,
Bugs filed after 1.0 and with submitters are being juggled in terms of priority (9 is highest priority). I'm raising bugs filed with a submitter, post-1.0 to P6.

For everything else, bugs which are filed post-1.0, but without a submitter remain P5. Before 1.0 bugs with a submitter are becoming P4, and pre-1.0 bugs without a submitter name become P3.

Thanks for your patience, while I try to pare back the bug list to what may actually still be in the program. I may also start to close bugs which are referring to the same issue, leaving either the oldest, or the one with the most activity.

-- Morgan Schweers, CyberFOX!