Menu

#749 Error encountered in function parseBidHistory in history.c line 181

v1.0 (example)
closed
nobody
None
5
2019-03-10
2018-04-08
No

paste this into "Detailed Description":
Automated esniper bug report.
esniper version 2.33.0
libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3
Error encountered in function parseBidHistory in history.c line 181
auction = 263585152524, price = 1.21, remain = 0
latency = 0, result = -1, error = 0
buf = 0xa1767f0, size = 37927, read = 0xa1767f0
time = 1523179200, offset = 0
pagename = "eBay Item Bid History", pageid = "(null)", srcid = "(null)"
specified options or config values:
1 x (P) = ***
1 x (U) = "philpem"
1 x (i) = 1
no item number
then upload and attach esniper.21546.3.bug.html and click submit.
Auction 263585152524: Unknown item

Auction 263585152524: Unknown item

1 Attachments

Discussion

  • Matt Schreiner

    Matt Schreiner - 2018-04-09

    Seconded. ParseBidHistory problem with the reduce flag to Y or N, both result in same error.

    Automated esniper bug report.
    esniper version 2.33.0
    libcurl/7.29.0 NSS/3.28.4 zlib/1.2.7 libidn/1.28 libssh2/1.4.3
    Error encountered in function parseBidHistory in history.c line 181
    auction = 112919816583, price = 17, remain = 0
    latency = 0, result = -1, error = 0
    buf = 0x18b9790, size = 37779, read = 0x18b9790
    time = 1523291818, offset = 0
    pagename = "eBay Item Bid History", pageid = "(null)", srcid = "(null)"
    specified options or config values:
      1 x username(u) = ***
      1 x password() = ***
      1 x seconds(s) = 5
      1 x quantity(q) = 1
      1 x (c) = "/home/user/.config/eSniper/sniper-config.txt"
      1 x (f) = "/home/user/auction.txt"
      1 x reduce() = 0
      1 x bid() = 1
      1 x debug(d) = 1
      1 x batch(b) = 0
      3 x logdir(l) = "/home/user/.config/eSniper/"
    no item number
    
     
  • Matt Schreiner

    Matt Schreiner - 2018-04-09

    Ah, just see there was a fix put for the history problem with latest git source. Cloned and compiled, and works now.

     
  • Tony Hammond

    Tony Hammond - 2018-04-12

    Just noticed this. When one new version doesn't work and changes are made to the code to make it work shouldn't there be a new version...2-34?

     
  • franzmueller

    franzmueller - 2018-05-15

    This is pretty messy. The new version does indeed work and in the git a commit has been made which clearly states 2.34.0 is the new version. However, even after compiling "esniper -v" still says it'd be 2.33.0. Someone must've forgotton to update the internal version number and make a new releae here.

     
  • Michael S.

    Michael S. - 2019-03-10
    • status: open --> closed
     

Log in to post a comment.