02:49 <stellar-slack> <sacarlson> @bitmynt: we need to hear the concept before we can respond to it

02:55 <stellar-slack> <sacarlson> I ran an experiment on testnet horizon with the wrong network passphrase instead of "Test SDF Network ; September 2015" I used "Not my network; September 2015" I got no returned error from horizon and return result of undefined.

03:52 <stellar-slack> <jed> The network pass phrase is just used for signing messages

09:17 <stellar-slack> <dchrist22> Hi, can someone tell me where I can find the latest pre compiled debian version of stellar-core?

09:35 <stellar-slack> <dchrist22> Never mind, found it :)

15:44 <stellar-slack> <scott> @sacarlson: Can you give me the tx envelope that triggered the bug? What do you mean by “undefined”? I’m assuming that’s a javascript undefined, which probably means your code isn’t setup to handle the way in which horizon is responding (Perhaps it is just closing the socket?). I would actually expect horizon to simply return a failed result with `tx_result_code == “tx_bad_auth”`

15:59 <stellar-slack> <sacarlson> @scott it

16:01 <stellar-slack> <sacarlson> no error as far as I can tell is flaged

16:02 <stellar-slack> <sacarlson> I can setup a prototype of the results if needed

16:04 <stellar-slack> <sacarlson> I've now changed my status output to flag as error? until a result is seen

16:22 <stellar-slack> <scott> @sacarlson: I’m not really motivated to hunt down the bug by investigating through your own product… I’m cool digging into code that we write, and definitely around the portions of your code that work with our libraries, but it’s not really prudent for me to spend company time starting from your interface and digging from there. If you can provide a transaction blob that triggers the error in your c

16:22 <stellar-slack> horizon, or if you can point me to the section of your code where you are handling horizon’s response I can speculate on a potential error in your own code.

16:23 <stellar-slack> <sacarlson> no problem I'll make a simple prototype tomaro

16:26 <stellar-slack> <scott> cool! thanks

16:48 <stellar-slack> <sacarlson> oh but @scott I'm also learning this line link thing on github that the error is at this location https://github.com/sacarlson/sacarlson.github.io/blob/93b9226b30299a38160599fd25a40e4bdacaf432/my_wallet/js/transaction_toolsv0.4.0.js#L699

16:48 <stellar-slack> <sacarlson> if that's of any benifit

16:49 <stellar-slack> <scott> So, you need to make sure to return the promise created on https://github.com/sacarlson/sacarlson.github.io/blob/93b9226b30299a38160599fd25a40e4bdacaf432/my_wallet/js/transaction_toolsv0.4.0.js#L686

16:49 <stellar-slack> <scott> That’s one cause of your problem

16:51 <stellar-slack> <scott> If you change that line i linked to `return server.submitTransaction(transaction)…..` I would expect things to work

16:51 <stellar-slack> <scott> Don’t you just love promises /sarcasm

16:56 <stellar-slack> <sacarlson> cool I'll try that

16:56 <stellar-slack> <sacarlson> I have no idea what a promises is ha ha

16:56 <stellar-slack> <sacarlson> I should have remained a ruby programer

17:01 <stellar-slack> <scott> :) I feel the same way sometimes. Luckily, go is a much more pleasant experience for me. I wish I could have the best of go along with the best of ruby, which is why I’m patiently watching http://crystal-lang.org/

20:24 <stellar-slack> <brian.ebert> javascript is icky. like having to learn English because it's become dominant.

21:37 <stellar-slack> <scott> lol, I love the `javascript == english` comparison. Or should it be `javascript === english`?

23:13 <stellar-slack> <scott> so, since go 1.6 landed, horizon is going to the http 2 support on the cheap! https://github.com/stellar/horizon/pull/248