04:14 <stellar-slack> <regisg27> @bartek server.payments().forAccount(******).order("desc").call() throw this error

04:14 <stellar-slack> <regisg27> ``` at PaymentCallBuilder._sendNormalRequest (/home/regisg/projets/proxiweb/node_modules/stellar-sdk/lib/call_builder.js:168:16) at PaymentCallBuilder.call (/home/regisg/projets/proxiweb/node_modules/stellar-sdk/lib/call_builder.js:72:21)```

04:20 <stellar-slack> <regisg27> The same code on node v 0.12 works fine

08:12 <stellar-slack> <regisg27> @bartek: sorry, works fine now... don't understand what happened ... maybe a cache problem...

10:43 <stellar-slack> <armed10> Good morning everyone!

10:45 <stellar-slack> <armed10> I was trying to add a new asset to my standalone node, and I'm doing something wrong, but the javascript stellar-sdk doesn't give me any error.

10:45 <stellar-slack> <armed10> I know it hangs when building the transaction, but that's about it

10:46 <stellar-slack> <sacarlson> @armed10: I think we will need to see some code to get a clue ok now we have something

10:47 <stellar-slack> <sacarlson> from quick glance it looks like an incomplete transaction

10:47 <stellar-slack> <armed10> If I log between every operation the last log I get is before transaction.build()

10:47 <stellar-slack> <armed10> any idea what I'm missing here/

10:47 <stellar-slack> <armed10> ?

10:48 <stellar-slack> <sacarlson> well a transaction I think needs to have a function of say payment to start

10:49 <stellar-slack> <armed10> Isn't a payment an operation?

10:51 <stellar-slack> <bartek> @armed10: `transaction` variable in your code is really transaction buider. `build` method returns the actual transaction: https://stellar.github.io/js-stellar-sdk/TransactionBuilder.html#build

10:53 <stellar-slack> <bartek> so it should be: ``` transaction = transaction.build(); ``` but it would be more elegant to simply chain all functions together: ``` var transaction = new StellarSdk.TransactionBuilder(account, { fee:1 } ) .addOperation(StellarSdk.Operation.changeTrust({ asset: new StellarSdk.Asset('TEST', rootKey), source: rootKey })) .build(); ```

10:54 <stellar-slack> <armed10> The reason I unchained it was because of debugging. Thanks, I'm trying it out now.

10:55 <stellar-slack> <armed10> The code still hangs at build();

10:55 <stellar-slack> <bartek> can you upload the whole file somewhere (gist maybe)?

10:57 <stellar-slack> <armed10> https://gist.github.com/anonymous/ec34e7ae2d59222102d8

10:57 <stellar-slack> <armed10> You'll probably want other files as well

10:57 <stellar-slack> <sacarlson> well it's done at build your not submiting it

10:57 <stellar-slack> <armed10> @sacarlson: the snippet is incomplete, please look at the gist

10:58 <stellar-slack> <sacarlson> ok

10:59 <stellar-slack> <bartek> what's the last output you see before it hangs?

11:00 <stellar-slack> <armed10> create transaction

11:02 <stellar-slack> <armed10> I'm probably not creating the asset the right way. Are there any prerequisites before adding an asset this way?

11:02 <stellar-slack> <sacarlson> I don't know what sendTransaction() does

11:03 <stellar-slack> <armed10> The source account for the transaction should probably be root

11:03 <stellar-slack> <sacarlson> normaly at that point we would have server.submitTransaction(transaction).then(function(result) { ...

11:04 <stellar-slack> <armed10> Yes but since running Horizon is problematic the sendTransaction method actually sends it directly to the stellar-core

11:05 <stellar-slack> <armed10> localhost/tx?blob=

11:05 <stellar-slack> <sacarlson> well again we must have missing code

11:07 <stellar-slack> <armed10> https://gist.github.com/anonymous/486cdc58b1da11891270

11:07 <stellar-slack> <armed10> I've an idea why it fails, i'll report after lunch.

11:09 <stellar-slack> <bartek> I have one too. can you try to remove line 41 in your file and check if it goes further?

11:16 <stellar-slack> <sacarlson> yes that line 41 source thing don't know what that is. that must be it

11:17 <stellar-slack> <bartek> it's the source of this operation. it's correct but it might be a bug in this single operation in sdk code.

11:37 <stellar-slack> <armed10> I'm a little confused as to how this works.. You have an Asset that you want to create, this Asset has an issuer. In my case root. Then I want to change trust on an account, but you don't target an account, you just name the source account, which is optional.

11:38 <stellar-slack> <armed10> So both the issuer and the one you give trust are both root?

11:38 <stellar-slack> <armed10> since root will sign the transaction

11:39 <stellar-slack> <armed10> I don't see where you would specify the 'other' account the documentation speaks of

11:40 <stellar-slack> <sacarlson> I'm guessing that the source if not provided defaults to one generating the transaction? did you try take out line 41?

11:40 <stellar-slack> <armed10> Yes, it does not help.

11:41 <stellar-slack> <sacarlson> and create transaction is still the last mesage?

11:41 <stellar-slack> <armed10> yes

11:43 <stellar-slack> <armed10> But root does not have the asset yet, do I need to create an asset another way before creating a trustline for it?

11:44 <stellar-slack> <bartek> no, someone needs to trust issuer and then issuer can send the asset

11:44 <stellar-slack> <bartek> what do argument of `createAccounts` mean?

11:45 <stellar-slack> <sacarlson> I'm not sure what the value or even objecdt types are of rootkey and rootprivate

11:46 <stellar-slack> <armed10> The root account is saved in my application for testing. rootkey is the public key and rootprivate is the private key of said root accout.

11:48 <stellar-slack> <armed10> @bartek: the first is the number of accounts to create and the second is the amount of lumens to add to each account

11:48 <stellar-slack> <armed10> It's from another segment where we test how fast accounts can be created

11:49 <stellar-slack> <bartek> what node and sdk version are you using? I will try to repro this.

11:51 <stellar-slack> <armed10> stellar-sdk: 0.4.1 node: 0.12.10

11:53 <stellar-slack> <sacarlson> I just noticed another thing in your fee: 1 unless you have your stellar-core set to accept that value I think it needs to be min fee: 100 min, but I don't see how that would effect your present problem

11:57 <stellar-slack> <armed10> I've set the desired base fee of stellar-core to 0

11:57 <stellar-slack> <armed10> @bartek

12:00 <stellar-slack> <bartek> ``` MacBook-Air-Bartek:armed10-repro bartek$ node -v v0.12.10 MacBook-Air-Bartek:armed10-repro bartek$ npm ls --depth=1 armed10-repro@1.0.0 /Users/bartek/armed10-repro └─┬ stellar-sdk@0.4.1 ├── axios@0.7.0 ├── bluebird@2.10.2 ├── es6-promise@3.1.2 ├── event-source-polyfill@0.0.6 ├── eventsource@0.1.6 ├── jsdoc@3.5.0-dev (git://github.com/jsdoc3/jsdoc.git#

12:00 <stellar-slack> stellar-base@0.5.4 ├── superagent@1.7.2 ├── toml@2.3.0 └── URIjs@1.16.1 MacBook-Air-Bartek:armed10-repro bartek$ node index.js create transaction sign transaction ```

12:01 <stellar-slack> <armed10> Could you share your version with me/

12:01 <stellar-slack> <bartek> I just took a builder part from your code: ``` var StellarSdk = require('stellar-sdk'); console.log('create transaction'); var account = new StellarSdk.Account("GCWX5WC53EFB4AXXTTMC7MTOMDU3X3J7TGESDIIX76QJQGWI72KKTUIZ", "10") var transaction = new StellarSdk.TransactionBuilder(account, { fee:1 } ) .addOperation(StellarSdk.Operation.changeTrust({ asset: new Stellar

12:01 <stellar-slack> "GCWX5WC53EFB4AXXTTMC7MTOMDU3X3J7TGESDIIX76QJQGWI72KKTUIZ"), source: "GCWX5WC53EFB4AXXTTMC7MTOMDU3X3J7TGESDIIX76QJQGWI72KKTUIZ" })) .build(); console.log('sign transaction'); ```

12:02 <stellar-slack> <bartek> would be cool if you sent how `account` and `rootKey` variables look like

12:02 <stellar-slack> <bartek> (these are the only variables used in the builder)

12:03 <stellar-slack> <sacarlson> yes I was wondering as I said what was in rootkey at least

12:04 <stellar-slack> <armed10> The error is from the account creation which only gives an object with keys and not a stellarsdk.account

12:06 <stellar-slack> <armed10> ,:(

12:06 <stellar-slack> <armed10> Thanks for all the effort

12:07 <stellar-slack> <bartek> problem solved :heavy_check_mark: no problem :)

13:26 <stellar-slack> <armed10> It worked, I used an asset I created for making a payment

13:28 <stellar-slack> <armed10> The laboratory provided by Stellar has an option for getting a lot of information on a single account. I can't use it because horizon doesn't work for me so does anyone know what query it uses to get that information?

13:29 <stellar-slack> <sacarlson> what info is it your looking for? you can browse the database

13:30 <stellar-slack> <armed10> getting the assets currently in an account

13:31 <stellar-slack> <sacarlson> you can look in the trustlines table

13:31 <stellar-slack> <armed10> yeah, thanks

19:49 <stellar-slack> <jed> any angular or ruby developers that want to help a stellar gateway integrate?