00:16 <stellar-slack> <richiela> might as well stop bugging jed diretly and ask in here heh

00:16 <stellar-slack> <richiela> hmm is there a stellarjs call taht wil get me back the current ledger height?

00:16 <stellar-slack> <jed> https://horizon-testnet.stellar.org/ core_latest_ledger :)

00:18 <stellar-slack> <richiela> meh .. okie..

00:18 <stellar-slack> <richiela> i'm doing a lot of back and forth of calling the url direct and using the server object from stellarjs :(

00:23 <stellar-slack> <jed> why do you need the ledger number?

00:24 <stellar-slack> <richiela> just keeping wallet stats locally

00:24 <stellar-slack> <richiela> we have a status page so it lets us know if blocks arent comnig in etc

16:14 <stellar-slack> <bartek> @sacarlson: you should use npm version / github tags instead of commit id. are you using any package manager?

16:15 <stellar-slack> <sacarlson> no I just get my stuf from github I'm new to java-script

16:15 <stellar-slack> <sacarlson> I don't want to be involved with compiling

16:16 <stellar-slack> <sacarlson> or packaging

16:16 <stellar-slack> <bartek> ok, but you should try npm or bower. they really improve workflow.

16:17 <stellar-slack> <dzham> prepare to swear a lot before you get on friendly terms with npm and/or bower

16:17 <stellar-slack> <sacarlson> I thought this was bower https://github.com/stellar/bower-js-stellar-sdk

16:18 <stellar-slack> <scott> I’m checking out what’s going on with the order book summary query at the moment. Should be able to get it fixed in not too many times

16:18 <stellar-slack> <bartek> this repo is used by http://bower.io|bower.io

16:19 <stellar-slack> <sacarlson> just add it to your script that updates changes to add it to the bower-js-stellar-sdk at the same time

16:19 <stellar-slack> <sacarlson> otherwise remove it

16:21 <stellar-slack> <sacarlson> I'm not sure there is a need to have mutiple conflicting releases that you guys release at different points

16:23 <stellar-slack> <bartek> this is a common standard that you have other repo for bower (ex. https://github.com/angular/bower-angular) and these releases are not in conflict, in fact this is the same codebase but in different forms.

16:25 <stellar-slack> <scott> sacarlson: the latest version released to the package managers of each language is what we recommend people use. If you want to track master, I would expect it to have unstabilities. The reality is, we only have a few engineers and we are spread across multiple projects. We cannot keep master coordinated across them all.

16:26 <stellar-slack> <sacarlson> understood scotty, I'm already happy with what you all do, and I have more than I want or need

16:28 <stellar-slack> <scott> +1

16:30 <stellar-slack> <scott> on the plus side, I should be tagging the 0.1 release of horizon real soon, and that will mark fewer breaking changes to horizon going forward

16:31 <stellar-slack> <scott> probably in the next couple of days after I knock some small issues out, along with the latest round of bugs that people have found

16:31 <stellar-slack> <sacarlson> did you guy look at nelisky's findings on horizon? does that sound like a problem?

16:32 <stellar-slack> <scott> I’m presently looking into it. Should be a pretty simple fix when I figure out where the problem is. The SQL appears to be behaving correctly, so it’s just some weird misalignment somewhere

16:33 <stellar-slack> <sacarlson> ok cool I'm not sure I have a full grasp on it as I never used horizon for that info

16:50 <stellar-slack> <scott> found the problem, should have a fix out in the next hour

17:04 <stellar-slack> <sacarlson> I knew you would

17:29 <stellar-slack> <scott> Alright, order book endpoint is fixed and deployed @nelisky. Thanks for the catch!

17:29 <stellar-slack> <nelisky> Fantastic, scott, I'll test in a bit!