02:10 <stellar-slack> <sacarlson> not sure what you want to explore but this is a cool tool https://stellar.github.io/network-explorer/#

02:12 <stellar-slack> <sacarlson> maybe this would be more of an explorer tool https://www.stellar.org/laboratory/#

03:35 <stellar-slack> <richiela> @sacarlson: i sent in a string amount to stellar-sdk for a withdrawal and it sent a different value all together

03:36 <stellar-slack> <sacarlson> any code?

03:36 <stellar-slack> <richiela> can i PM you?

03:36 <stellar-slack> <sacarlson> sure but I don't know why you would want to keep any secreets

08:48 <stellar-slack> <regisg> Hello, I don't find the documentation explaining Authorize Trust Line... what is it for ?

08:53 <stellar-slack> <sacarlson> you speaking of these? AUTH_REQUIRED_FLAG: AUTH_REVOCABLE_FLAG: . I've never tried them

08:54 <stellar-slack> <sacarlson> you can try play with them to see what they really do if you try play with them in setoptions in https://stellar.github.io/network-explorer/

08:55 <stellar-slack> <sacarlson> it might have something to do with making it possible for a issuer to freeze accounts.

09:02 <stellar-slack> <sacarlson> oh also have to set this bit Allow an account to hold trustline to your account. This requires that your account have AUTH_REQUIRED_FLAG set, and the account you're authorizing has already set a trustline to your account for the asset you're authorizing.

09:04 <stellar-slack> <eno> let me guess : if A set AUTH_REQUIRED_FLAG =1 , issue 'BEER' , and make a allow_trust op to B , B and C can set trustline to A for BEER, but B cann't send 'BEER' to C.

09:05 <stellar-slack> <regisg> @sacarlson: yes, this is AUTH_REQUIRED_FLAG & AUTH_REVOCABLE_FLAG

09:07 <stellar-slack> <regisg> @eno, I'm going to test the usercase you describe to see if you guess well. Thanks

14:09 <stellar-slack> <fredolafritte> Is there a way to cancel an order just by knowing its id ?

14:59 <stellar-slack> <eno> i am not sure ,you may need to test this : post a new manage_offer op , take this id and set price to 0 .

15:07 <stellar-slack> <jed> Yeah but set amount to 0 not price

15:23 <stellar-slack> <fredolafritte> buying selling code/issuer are not necessary then ?

15:25 <stellar-slack> <fredolafritte> I've had the orders cancelled already but I was filling buying selling code/issuer,

15:26 <stellar-slack> <fredolafritte> however, the order id should be enough, shouldn't be ?

15:26 <stellar-slack> <jed> Oh I see. I think so but I'm not in front of a computer so can't check.

15:56 <stellar-slack> <fredolafritte> unfortunately, it seems that buying and selling are required to cancel an order, otherwise: `Cannot read property 'toXdrObject' of undefined`

16:31 <stellar-slack> <powderfan> Any ideas on my issue with `paths` request? Do I miss something, or is it a bug? Should I open an issue for that?

16:35 <stellar-slack> <jed> Scott ^

16:36 <stellar-slack> <scott> let me check it out

16:41 <stellar-slack> <jed> Fredolafritte: the fields have to be there but I think you can set them to 0 or garbage

16:47 <stellar-slack> <scott> @powderfan: I believe this is an issue when trying to find paths involving a destination account that is also the issuer of the destination asset.

16:48 <stellar-slack> <scott> (i’m starting to regret that stellar-core doesn’t track issuer balances)

16:50 <stellar-slack> <sacarlson> I wrote a function that creates issuer balance from stellar-core db data

16:50 <stellar-slack> <sacarlson> not that this will help in this case

16:51 <stellar-slack> <scott> yeah, if it’s not tracked in the core it doesn’t really help me here

16:52 <stellar-slack> <sacarlson> I think my test orders of AAA BBB

17:09 <stellar-slack> <scott> I don't really understand what your test is, or what you’re expecting. If you can explain a little more concretely I can look into it.

17:13 <stellar-slack> <sacarlson> well that is part of the problem as I'm not sure what to expect in the results of path

17:14 <stellar-slack> <scott> in that case, path should be `[]`, the source and destination asset are the same

17:14 <stellar-slack> <sacarlson> that makes sence

17:15 <stellar-slack> <scott> the `path` attribute will contain “asset” objects each intermediary hop needed for a given result

17:16 <stellar-slack> <sacarlson> then I need to setup test orders so that a path is required

17:16 <stellar-slack> <scott> yep. horizon does have test cases for a bunch of the scenarios, but the specific case powderfan is encountering is not covered

17:18 <stellar-slack> <sacarlson> so I should have an order setup that could require a hop with three assets on order. I'll try to find a way to make one show in the path

17:43 <stellar-slack> <scott> Alright, I’ve confirmed it’s not specifically related to the issuer being the destination. Further checking the situation now

17:50 <stellar-slack> <scott> ah! Found the cause. The current pathfinder won’t continue searching for longer paths using a given asset if that asset is already an acceptable end point. Looking into the solution now

19:19 <stellar-slack> <sacarlson> I was attempting to try to cancel an offer using stellar-sdk.js. I'm getting this error TypeError: amount argument must be of type String and represent a positive number. I have opts.amount = '0'; isn't that how you cancel offers is by setting amount to "0" ? maybe need "0.0"?

19:20 <stellar-slack> <scott> Are you sure you’re on the latest released version. bartek fixed a similar issue a while back: https://github.com/stellar/js-stellar-base/commit/6c21fe8f4f20d7c81fe58651e245110625758e62

19:21 <stellar-slack> <sacarlson> no I'm on older 0.2.12 so I'll try upgrade

19:24 <stellar-slack> <scott> np!

19:43 <stellar-slack> <scott> alright, so the short circuit issue I found doesn’t fix the paths issue that powderfan was seeing. I now believe the cause is due to how we handle the native currency in pathfinding. Getting a regression test in place first before solving the issue, but it’ll probably take a bit longer (hopefully before EOD)

19:53 <stellar-slack> <sacarlson> now using stellar-sdk.js v 0.2.21 and got my first offer transaction to cancel ok. but seems everything must be entered and match the order, not just the orderid

20:15 <stellar-slack> <richiela> you guys should update people when important sdk bugs get fixed ;)

20:16 <stellar-slack> <richiela> i think 0.2.12 was the version out when the new blockchain came up

20:16 <stellar-slack> <richiela> so a lot of people are probably still on that version

20:16 <stellar-slack> <sacarlson> yes I only change when I have to now when they come out

20:18 <stellar-slack> <scott> richiela: have recommendations about how we notify people? I believe bartek discussed the fix being pushed to npm in this channel back when it was made

20:19 <stellar-slack> <richiela> tweet, email lists, blog...

20:19 <stellar-slack> <richiela> ETH does a realy good job with their blog and a tweet

20:19 <stellar-slack> <richiela> personally contacting exchanges/service providers wouldn't hurt but its a lot to ask ;)

20:20 <stellar-slack> <bartek> @scott @richiela this bug was fixed about month ago. @jed sent emails to partners. I think tweeting and email to devs is ok.

20:22 <stellar-slack> <scott> IMO, if we’re going to email developer releases we should really just setup a mailing list and announce there. Our current newsletter mailing list is not appropriate, IMO

20:22 <stellar-slack> <richiela> who actually owns the sdk?

20:22 <stellar-slack> <richiela> from a github standpt?

20:23 <stellar-slack> <scott> What do you mean own? The canonical repo is here: https://github.com/stellar/js-stellar-sdk

20:23 <stellar-slack> <richiela> whos the main maintainer

20:24 <stellar-slack> <richiela> things like critical bug fixes taht get merged should get communicated somehow.. thats my thinking

20:24 <stellar-slack> <scott> We don’t have a single maintainer. it’s “The stellar platform development team” i.e. Me, Bartek, Iris and Jed

20:24 <stellar-slack> <richiela> ok.. just curious..