07:49 <stellar-slack> <powderfan> there seems to be a sever bug in horizon or stellar-core testnet at the moment. When I submit payments, it takes a while and then throws an empty error (really no info at all). The balance is reduced but the effect for account does not show up neither in stream nor in batch retrieve.

16:46 <stellar-slack> <eva> @powderfan: is this still happening for you?

16:47 <stellar-slack> <sacarlson> I noted I was still able to do transactions after his problem was noted, but I don't use his stream stuf

17:00 <stellar-slack> <bartek> @powderfan: @eva I can confirm it's happening

17:04 <stellar-slack> <eva> thanks @bartek

17:05 <stellar-slack> <eva> @powderfan and @sacarlson seems like something @scott will be able to help with when he’s around

17:07 <stellar-slack> <scott> I’ll check things out momentarily.

17:12 <stellar-slack> <eva> thanks!

17:17 <stellar-slack> <scott> @bartek: if you’re interested in looking at the code for my little experiment from yesterday: https://github.com/nullstyle/wallet-one

17:17 <stellar-slack> <bartek> ok, great! thanks!

17:18 <stellar-slack> <scott> So, it looks like a bug in horizon-importer got tripped on testnet. Working on a fix now. When history cannot be imported, a transaction submission will timeout since we cannot confirm the transaction was successful.

17:55 <stellar-slack> <scott> Fix for testnet should be up in about 10 minutes

17:56 <stellar-slack> <scott> Then I’ll get back to fixing the effect endpoint issues from yesterday

18:04 <stellar-slack> <powderfan> cool! brings me closer to my first official release on new network!

18:12 <stellar-slack> <scott> alright, horizon testnet is caught back up. Sorry about the snafu y'all

19:40 <stellar-slack> <scott> deploying some fixes for horizon to testnet and prod.

19:51 <stellar-slack> <powderfan> great! fixed it for me. thx

19:51 <stellar-slack> <scott> sweet! happy to help

21:27 <stellar-slack> <jed> is there something in js-stellar-base that tells you if an address is valid?

21:27 <stellar-slack> <bartek> `Account.isValidAddress(address)`

21:30 <stellar-slack> <jed> richiela you can just use that ^ to see if the address is valid or not. If it doesn't exist then use the create account op rather than payment

21:31 <stellar-slack> <richiela> hmm...

21:31 <stellar-slack> <richiela> ok

21:46 <stellar-slack> <jed> scott did you add memo to the payments for account endpoint or you still have to look up the tx itself?

21:47 <stellar-slack> <scott> presently I was thinking that would happen after we get the importer ported to go, but I can front load that if you like and get it done in the next couple of days if you’d like me to

21:48 <stellar-slack> <richiela> that would help us out alot ;)

21:50 <stellar-slack> <richiela> hmm to touch on isValidAddress again...

21:51 <stellar-slack> <richiela> thats goign to return false if the accoutn is invalid or just bad input right?

21:51 <stellar-slack> <richiela> our users enter the darnest things... so if they enter "aldksfjsladfkajsdfl" thats going to return invalid, but then we'd try to createaccount on it

21:51 <stellar-slack> <jed> no I was just couldn't remember if it was there or not. I wouldn't reprioritize

21:53 <stellar-slack> <jed> richiela: yeah it tells you if it is a validly formed address not if it exists or not

21:53 <stellar-slack> <jed> so afdsfsf would fail

21:55 <stellar-slack> <richiela> ok so i need to check if its valid, and then if its been funded?

21:56 <stellar-slack> <jed> yeah

22:00 <stellar-slack> <scott> To further jed’s point: You would normally use `isValidAddress` to decide whether or not you should perform federation on the input. If the address is invalid (i.e. it is a person's federated name) you would look their address up using the federation protocol.

22:04 <stellar-slack> <richiela> honestly.. i'd keep it simple...

22:04 <stellar-slack> <richiela> if the address isn't valid, i'm just going to reject it unless i have an easy way to tell invalid vs unfunded vs good

22:09 <stellar-slack> <jed> bartek where are the docs for dealing with the response from txs https://horizon-testnet.stellar.org/transactions/6c5c647f2c40b815a62beb7b2001d702cb988c7f76097b80f9d4abc18301268c

22:10 <stellar-slack> <jed> there is some easy way to get the operations and result and everything out right?

22:12 <stellar-slack> <richiela> basically looking for a single, cursor enabled list, with src/dest/amount/memo

22:12 <stellar-slack> <bartek> `var transaction = new StellarBase.Transaction('{tx envelope b64 encoded}');`

22:13 <stellar-slack> <bartek> @jed here's a doc: https://github.com/stellar/js-stellar-base/blob/master/docs/learn/building-transactions.md#transaction

22:14 <stellar-slack> <richiela> hmm so i have to process the transaction list and then build my own list or something.. hmm

22:14 <stellar-slack> <richiela> think i'll just wait till memo is added to the payments endpoint

22:15 <stellar-slack> <bartek> @richiela: so basically, you need to retrieve a list of transactions for an account, right?

22:15 <stellar-slack> <richiela> else i'm doing alot of json munging for no erason..

22:15 <stellar-slack> <richiela> bartek: yes

22:15 <stellar-slack> <richiela> bartek: all i want is the payments endpoint with memo ...

22:19 <stellar-slack> <jed> richiela: the easiest thing to do is just what that example does here: https://www.stellar.org/developers/learn/integration-guides/exchange.html

22:20 <stellar-slack> <jed> you will be able to remove the extra call to look up the memo when we implement it but right now it is very minimal overhead

22:23 <stellar-slack> <richiela> i dont think i can make that work cause i'm not streaming..

22:23 <stellar-slack> <richiela> basically doing a .call() and returning the json blob

22:24 <stellar-slack> <jed> it is the same

22:24 <stellar-slack> <jed> .call() will return an object you can call .transaction() on like in the example to get the memo

22:25 <stellar-slack> <jed> handlePaymentResponse will be the same

22:26 <stellar-slack> <jed> you will just get one batch of responses instead of responses continuously

22:26 <stellar-slack> <richiela> i must be reading this wrong

22:27 <stellar-slack> <richiela> but the way this reads is a blob is passed to the handler, the handler deciphers the memo, and then acts on it..

22:28 <stellar-slack> <richiela> that wont work for us cause the way we're dmz'd crazily... the only thing i epxect is a list of transactions that i can process somewhere else..

22:28 <stellar-slack> <richiela> this would work if i get the paymetns list.. enumerate through them to add the memo manually using the tx, and then creating a new list and returning it..

22:29 <stellar-slack> <richiela> just a lot of json munging work heh

22:30 <stellar-slack> <jed> Here I'll put an example of what you need to do in the docs...