00:15 <stellar-slack> <scott> @powderfan: looks like the bug you found regarding path finding is fixed: https://horizon-testnet.stellar.org/paths?destination_account=GC7DJUFVMD5BYXS67MWAAQSJF6UASF47RY2AUCKOR5J2YTWS6ZNIGS6Y&source_account=GALYYRH5XCRLVQ3W56PNEZHRV37GY3VFRRFUYU4NNDKOGUAB22OQPUX4&destination_asset_type=native&destination_amount=0.0001

00:15 <stellar-slack> <scott> You can see it now shows 2 paths

00:15 <stellar-slack> <scott> one using XLM as the source currency

01:06 <stellar-slack> <hsxuif> I second a mailing listing/newsletter specially for developers; IMHO, it's really tough work to catch up when I don't keep on an eye on the commit changes. for slack dev channel, the problem seems that it is not thread oriented so we frequently get lost where we were last and it's hard to pick up the older discussions.

01:11 <stellar-slack> <lab> sdf need a tech writer.

01:14 <stellar-slack> <jed> Yep making one

01:15 <stellar-slack> <lab> there are enough stories about financial inclusion, but much lesser tech updates.

01:16 <stellar-slack> <lab> cool

03:16 <stellar-slack> <sacarlson> I have to assume that testnet horizon isn't really running this version of stellar-core "core_version": "v0.3.0-5-gf5b9f4e" as seen here https://horizon-testnet.stellar.org/ so I guess this PR https://github.com/stellar/horizon/pull/204 from mason isn't doing what I thought it would do by getting the real version from the stellar-core?

03:28 <stellar-slack> <mason> Hmmmm I updated the tests. Might be a bug. I can probably take a look tomorrow. Still got 3 hours of cyber monday shopping left to do haha

03:30 <stellar-slack> <mason> You're in Thailand @sacarlson correct?

03:30 <stellar-slack> <sacarlson> yup

03:31 <stellar-slack> <mason> I visited bangkok for a few days last summer and loved it!

03:32 <stellar-slack> <mason> I got one of those day passes to the river and just rode up back and forth all day

03:42 <stellar-slack> <mason> Yeah, I heard some crazy stories about the islands. Wish I had more time. I'll probably be back someday

07:11 <stellar-slack> <dzham> anyone else have problems with setting cursors in js-stellar-sdk?

07:12 <stellar-slack> <dzham> `server.operations(...).cursor is not a function`

07:16 <stellar-slack> <sacarlson> dzham: I've used it were borrowed from examples from powderfan

07:16 <stellar-slack> <dzham> working in the latest npm package, but not with the latest github

07:18 <stellar-slack> <sacarlson> it was working with v0.2.12 and now v0.2.21

07:19 <stellar-slack> <sacarlson> https://github.com/sacarlson/stellar_utility/blob/master/multi-sign-server/www/js/stellar_min_client.js

07:21 <stellar-slack> <sacarlson> http://zipperhead.ddns.net/stellar_min_client.html

09:47 <stellar-slack> <powderfan> I'm using v0.2.21

11:46 <stellar-slack> <bartek> @dzham can you share your code?

11:48 <stellar-slack> <dzham> @bartek: sure, it wasn’t anything more complicated than `server.operations().cursor('now’)`

11:49 <stellar-slack> <dzham> works in latest npm, didn’t work pulling from github

11:53 <stellar-slack> <sacarlson> I'm also running v0.2.21 and my memo is still working http://stellar.github.io/xdr-viewer/#xdr=AAAAABgjmdwgqRJl6q0FDO2xDlivEkSFTvjnfkrplpD99NioAAAAZAAJzDsAAABuAAAAAAAAAAEAAAAOc2NvdHR5X2lzX2Nvb2wAAAAAAAEAAAAAAAAAAQAAAADrg150TRtZJM0l%2F9VQcwNPbfawyTIxoLNEJ%2BG155X2jgAAAAAAAAAAAJiWgAAAAAAAAAAB%2FfTYqAAAAEBrpWGABK%2BGZIkoEEKmidEPhNrHv9LVBrqFh58EtpG6vlxyqk3ZlZDetUdut2iik6pAplpcYEGEBOs9HJYlXF4J&type=TransactionE

12:07 <stellar-slack> <powderfan> @bartek: thanks, that solved the issue. I like the addMemo variant.

13:14 <stellar-slack> <bartek> looks like a network halt.

13:15 <stellar-slack> <bartek> or horizon-importer issue.

13:15 <stellar-slack> <bartek> http://stellar.github.io/horizon-status/

13:18 <stellar-slack> <bartek> no, actually looks like a live network halt. I was checking testnet status.

13:30 <stellar-slack> <eno> live network goes well.

13:31 <stellar-slack> <eno> Got consensus: [seq=1105121, prev=a8c67d

13:31 <stellar-slack> <bartek> then, horizon may have some problems connecting to stellar-core db: http://stellar.github.io/horizon-status/ last ledger is 1100111 according to status page

13:34 <stellar-slack> <eno> i guess sdf_watcher1 which horzion may connect to lost consensus.

15:59 <stellar-slack> <scott> yeah, looks like the stellar-core node that http://horizon.stellar.org|horizon.stellar.org is talking to is not responding. Checking it out now

16:00 <stellar-slack> <jed> sctt" I'm on the box

16:22 <stellar-slack> <scott> alright, horizon is back @namic sorry about the issue.

20:07 <stellar-slack> <sacarlson> for manageOffer what is the correct default value for offerid opts.offerId = null; it seems null and empty string won't work. what is needed for it to auto create a new offerid number?

20:28 <stellar-slack> <sacarlson> cancel last request all that is needed is just don't define it at all

20:41 <stellar-slack> <sacarlson> so I added to my super crapy javascript collection, the new Stellar Order Tool http://zipperhead.ddns.net/order_tools.html so I can now create, cancel and search sorted price orders on any asset.

21:00 <stellar-slack> <scott> @sacarlson: 0 is the id to use for creating a new offer

21:01 <stellar-slack> <sacarlson> oh ok well I found not defining it also worked but good to know thanks

21:01 <stellar-slack> <sacarlson> oh in the comments it says 0 will delete the order

21:48 <stellar-slack> <scott> yay: horizon now automatically creates github releases when we tag a new version: https://github.com/stellar/horizon/releases

21:49 <stellar-slack> <scott> with cross platform build! (thanks, go)

22:02 <stellar-slack> <sacarlson> I also note on horizon that the "core_version": "v0.3.1-2-g4e632f5" changed so I'm guessing that's now set from what it see's from the core no longer manually set. so maybe I can set my auto compile update to track horizon?

22:11 <stellar-slack> <scott> it was never manually set. Horizon has always loaded the core_version from the stellar-core it is connected to.

22:13 <stellar-slack> <sacarlson> then you just now started to run stellar-core v0.3.1-2?

22:16 <stellar-slack> <scott> do you mean horizon-testnet or horizon? jed typically deploys new stellar-core code, which I believe he’s done recently on both live and testnet

22:17 <stellar-slack> <sacarlson> I mostly look at testnet

22:22 <stellar-slack> <scott> That’s all up to jed, as mentioned he manages when new versions of stellar-core roll out to either environment

22:23 <stellar-slack> <sacarlson> I just assumed the version horizon displayed was incorrect as that version was not stable for me here

22:23 <stellar-slack> <scott> It’s looks to me like you were mistaken about seeing `v0.3.1-2-g4e632f5` on testnet… those processes have been running for 12 days now

22:24 <stellar-slack> <scott> what do you mean “not stable”? shifting back and forth between two values?

22:26 <stellar-slack> <sacarlson> not stable I mean I couldn't keep sync on "core_version": "v0.3.0-5-gf5b9f4e" or around that version that is now shown to be running on testnet as seen https://horizon-testnet.stellar.org/

22:31 <stellar-slack> <scott> oh! the version numbers presented by horizon provide no indication about whether that version is stable in the sense that you mean. It’s just an informational display about what is that horizon instance is currently running and what the version is being reported by the stellar-core that the horizon server is configured to communicate with.

22:32 <stellar-slack> <sacarlson> ok