01:06 <stellar-slack> <sacarlson> @ant I think maybe both those Interledger and Hyperledger are mostly vaporware (not really fully exist yet and maybe never will). But one that looks promising to me is https://www.ethereum.org/ but it has a long way to go yet also, but coming along fast. It looks to have unlimited possibilities. But that's just my opinion.

04:12 <stellar-slack> <lab> ethereum is like a blackhole attracting people. stellar is becoming a white dwarf meanwhile.

04:14 <stellar-slack> <sacarlson> ha ha white dwarf I like that

04:23 <stellar-slack> <lab> white dwarf in nutshell: a burned stellar with destroyed surrounding and small hard core.

14:59 <stellar-slack> <mvaneijk> Ethereum script are written in a Turing complete language, so unlimited possibilities indeed

15:02 <stellar-slack> <mvaneijk> meanwhile, does someone here has experience with subscribing to a Horizon stream event? I also implemented 'onerror' but it fires every second

15:03 <stellar-slack> <sacarlson> yes I note that when I subscribe to horizon stream events as it must pole\

15:04 <stellar-slack> <sacarlson> mvaneijk: I have example in my code that use horizon stream events

15:04 <stellar-slack> <sacarlson> not the best code I must admit

15:05 <stellar-slack> <mvaneijk> I have working code, but sometimes it stops the onerrors, and than the stream is dead

15:05 <stellar-slack> <mvaneijk> But the idea of a stream is that the application don't have to pole

15:05 <stellar-slack> <sacarlson> it has a content limit on horizon if you supass some amount it locks you out for some time

15:06 <stellar-slack> <sacarlson> yes but I don't think it uses sockets on horizon. I think the code poles.

15:07 <stellar-slack> <mvaneijk> That sounds logical, but that means streams are not useable.

15:07 <stellar-slack> <sacarlson> well if you setup to your own horizon I guess you won't have to deal with that problem

15:07 <stellar-slack> <mvaneijk> As streams at least

15:08 <stellar-slack> <mvaneijk> I have my own Horizon running and it happens there

15:08 <stellar-slack> <sacarlson> I setup sockets on my mss-server that interfaces to stellar-core that is also another option

15:08 <stellar-slack> <mvaneijk> I'll check how it is implemented

15:08 <stellar-slack> <mvaneijk> Omitting horizon you mean

15:09 <stellar-slack> <sacarlson> yes my multi sign server bypasses horizon and does most basic functions of horizon

15:10 <stellar-slack> <sacarlson> it's primitive compared to horizon

15:10 <stellar-slack> <sacarlson> and never tested to scale

15:11 <stellar-slack> <sacarlson> oh and I think I failed to get it to work from a chrome browser for some security issue but works on firefox

15:14 <stellar-slack> <mvaneijk> I'm testing with chrome, maybe another browser makes a difference

15:14 <stellar-slack> <sacarlson> the documentation has also fallen behind in the development https://github.com/sacarlson/stellar_utility/tree/master/multi-sign-server

15:14 <stellar-slack> <sacarlson> no I think horizon works fine on horizon. never know any problems with chrome and horizon

15:15 <stellar-slack> <mvaneijk> But with the streams

15:15 <stellar-slack> <bartek> @mvaneijk: what error do you get?

15:16 <stellar-slack> <sacarlson> I do all my tests with firefox and I've had drop outs that I assume are due to hitting the usage limits

15:16 <stellar-slack> <mvaneijk> Not really an error

15:16 <stellar-slack> <bartek> what's the payload?

15:16 <stellar-slack> <mvaneijk> I guess the javascript sdk just returns the eventsource upon error

15:17 <stellar-slack> <mvaneijk> I request effects for account

15:17 <stellar-slack> <sacarlson> my payloads I have setup as trying to get 45 events that then also have to look up each of them to pull all the transaction of each

15:17 <stellar-slack> <sacarlson> and I start repeating a few times with small changes and hit stops

15:21 <stellar-slack> <sacarlson> but I would think in normal operation this wouldn't happen

15:34 <stellar-slack> <sacarlson> as I look closer it seems I have to do 3 lookups for each transaction detected in effects to get all the info I wanted from horizon

15:35 <stellar-slack> <mvaneijk> I guess I solved at least part of the problem by stating that the account doesn't exist :thinking_face:

15:36 <stellar-slack> <sacarlson> oh maybe you need better error checking

15:37 <stellar-slack> <sacarlson> I was looking in the wrong places to try to find out what caused errors

15:41 <stellar-slack> <mvaneijk> but that explains why it stopped when I sent the first transaction. Ok, I will first debug with already funded account. Then see how to act on funding operation. Thanks for the help @sacarlson

15:47 <stellar-slack> <sacarlson> I'm not sure if this will help but the error catching was hard for me so maybe check this out

15:49 <stellar-slack> <mvaneijk> Thanks!

17:20 <stellar-slack> <graydon> scott: possibly fiddle with the await_sync: option in recipe?

17:21 <stellar-slack> <scott> graydon: yeah, I figured it out, sorry about not pinging you. When in manual close mode, await_sync now gets forced to off