--- Day changed Fri Jul 08 2016 02:03 -!- roconnor [~roconnor@host-45-78-197-222.dyn.295.ca] has quit [Ping timeout: 252 seconds] 03:26 -!- waxwing is now known as waxwing123456789 03:26 -!- waxwing123456789 is now known as waxwing 04:39 -!- arubi [~ese168@unaffiliated/arubi] has quit [Quit: Leaving] 04:42 -!- arubi [~ese168@unaffiliated/arubi] has joined #secp256k1 05:15 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #secp256k1 05:15 -!- arubi [~ese168@unaffiliated/arubi] has quit [Disconnected by services] 07:17 -!- roconnor [~roconnor@host-45-58-246-126.dyn.295.ca] has joined #secp256k1 07:42 < afk11> Has anyone ever had issues with secp256k1_ec_pubkey_parse? My bindings occasionally fail on this function, and I have no idea what causes it besides possibly environmental factors. Another user switched shells and suddenly his reproduceable failure case went away. 07:42 < afk11> https://github.com/Bit-Wasp/secp256k1-php/blob/master/secp256k1/secp256k1.c#L683 its a tiny function, I'm mostly asking here because it seems secp256k1_ec_pubkey_parse is always being called, it just fails sometimes. 09:31 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has joined #secp256k1 09:32 < gmaxwell> afk11: presumably you're sending things in which aren't valid public keys. 12:34 < afk11> gmaxwell, yeah, it was something like that.. something messed with pubkeylen, so the length was neither 33/65 :/ 17:03 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has quit [Quit: Leaving.] 21:00 -!- roconnor [~roconnor@host-45-58-246-126.dyn.295.ca] has quit [Ping timeout: 260 seconds] 21:14 -!- roconnor [~roconnor@host-23-251-188-19.dyn.295.ca] has joined #secp256k1 21:18 -!- roconnor [~roconnor@host-23-251-188-19.dyn.295.ca] has quit [Client Quit] 21:41 -!- arubi_ is now known as arubi 22:28 -!- fifth_ [~fifth@80.215.178.37] has joined #secp256k1