bit2017 has quit [Ping timeout: 250 seconds]
bit2017 has joined #stellar-dev
<stellar-slack> <brian.ebert> Imagine you are raised with a language that is perfectly phonetic. Then someone comes along and says you have to learn this franco germanic mashup with tribal dialect from nature worshipping people dwelling at the edges of geographic hospitality. Oh goody! When does class start? It's just like all browsers only read something that makes it easier to make mistakes with. And that == v. ===? Oh man.
<stellar-slack> in not being able to tell you just how the sky might fall if I use 2.
<stellar-slack> <sacarlson> that must be why only 1/10 of my code works as I only use 2?
<stellar-slack> <brian.ebert> Yes, but you probably understand how the operator works. I don't!
<stellar-slack> <sacarlson> well I guess if I fully understood it then 1/10> of my code would work properly
<stellar-slack> <sacarlson> so just lucky I'm not a perfectionist
de_henne_ has joined #stellar-dev
de_henne has quit [Ping timeout: 248 seconds]
bit2017 has quit [Read error: Connection reset by peer]
bit2017 has joined #stellar-dev
nivah has joined #stellar-dev
bit2017 has quit [Ping timeout: 276 seconds]
[7] has quit [Disconnected by services]
TheSeven has joined #stellar-dev
<stellar-slack> <philbee> I'd like to create an asset and see the constructor in the js-stellar documentation at https://stellar.github.io/js-stellar-sdk/Asset.html . However, when I look for it in the Horizon reference (https://www.stellar.org/developers/reference/) to try it out with curl or directly to the rest API from another language, I don't see the asset object in the reference. Can assets be created directly via the REST
<stellar-slack> put more generally, are all functions available in the js-stellar-sdk available directly via the REST API? Did I miss it in the docs? Thanks.
<stellar-slack> <sacarlson> to be doing anything with the rest api you still need a lib to feed it the crypto magic. the libs to do this are available in js, ruby, go, python...
<stellar-slack> <sacarlson> creating assets can be done from the web tools available https://www.stellar.org/laboratory/# and in other tools available in other apps and sites
<stellar-slack> <philbee> Thanks @sacarlson , though when I look at that web tool URL you sent, it is similar to the horizon api reference in that it seems to be missing the asset resource... there doesn't seem to be an asset endpoint. Nevertheless, if it can't be done directly via REST without a lib, I'll use one of the available libs.
<stellar-slack> <sacarlson> as far as I know all the features available on stellar's stellar-core system can be accessed from laboratory. it's not very user friendly at some points but you should be able to setup most anything on both testnet and Live net
<stellar-slack> <sacarlson> it would be required to setup trust on two accounts that you plan to setup trade with to at least one issuer. that issuer would have to issue each of these accounts funds. these funds can then be traded between the two accounts with setup offer orders to determine price of each
<stellar-slack> <dzham> @philbee: anything interesting you’re going to want to do involves signing transactions, and the easiest way to do that is the js libraries
de_henne_ has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack> <sacarlson> @scott I isolated my error catching problem that was on my side not stellar libs, as usual...
<stellar-slack> <philbee> Thanks @dzham and @sacarlson
<stellar-slack> <jed> philbee: https://www.stellar.org/developers/horizon/reference/accounts-single.html this will list the assets an account holds
<stellar-slack> <bartek> @philippe Asset class in js sdk is used mainly to build operations/transactions. The link above contains js snippet to get list of balances of the account. It will return a simple json response.
<stellar-slack> <bartek> You should also read this document about assets in Stellar https://www.stellar.org/developers/learn/concepts/assets.html
<stellar-slack> <armed10> We're currently running some homebrew stress tests against stellar (using stellar-core SDK). In the test we create 1000 accounts and try to push as many transactions as possible within a pre-defined time period. Our script reports having sent 3781 request and each results in status 'PENDING'. However, after the test there are only 3050 transactions in the ledgers (plus 2000 for creating/deleting the accounts
<stellar-slack> <armed10> Does Stellar reject certain transactions on overload after the response?
<stellar-slack> <armed10> Never mind, it's probably some accounts sending there money faster than they receive it.
<stellar-slack> <armed10> Is there a way for a client to see if his transaction has gone through?
<stellar-slack> <armed10> Even with enough money the transaction don't all come through
<stellar-slack> <bartek> @armed10: are you checking if horizon does not return errors for transactions? it may be a good idea to use Channels: https://www.stellar.org/developers/learn/integration-guides/building-blocks/channels.html
<stellar-slack> <dchrist22> @armed10 I´m doing similar tests right now, also with 'PENDING' responses. Also just about 2/3 of the transactions are included in the database in the end. But I am currently not checking for the balances of the accounts. So that could be the cause of this for me.
<stellar-slack> <armed10> @bartek: We're not using horizon as the importer is giving us issues (mainly pretending to do work but having an empty database)
<stellar-slack> <armed10> I'll look into channels, which would be great for doing a lot of transactions. We tried to mitigate the seqnum errors by using a lot of accounts
<stellar-slack> <armed10> @dchrist22: We thought that would be the problem at first, too. but even with a lot of money in each account the problem persists
<stellar-slack> <bartek> when using stellar-core you'll never get something like `SUCCESS` response: > tx /tx?blob=Base64 > submit a transaction to the network. blob is a base64 encoded XDR serialized 'TransactionEnvelope' returns a JSON object with the following properties status: > "PENDING" - transaction is being considered by consensus > "DUPLICATE" - transaction is already PENDING > "ERROR" - transaction rejected by transaction
<stellar-slack> "ERROR". Base64 encoded, XDR serialized 'TransactionResult'
<stellar-slack> <bartek> but I'd check Channels and ask stellar-core team (they will be up in a few hours)
<stellar-slack> <armed10> I will, thanks @bartek
<stellar-slack> <sacarlson> and these tests, did you say you didn't use horizon? I wonder how fast it could be done if mss-server was to replace horizon in such a test
<stellar-slack> <sacarlson> and you should be able to get results feedback as it was running
<stellar-slack> <bartek> I don't think it makes any difference. horizon is really just a thin layer on top of stellar-core (when it comes to submitting transactions).
<stellar-slack> <sacarlson> I think your right, there is not very much needed other than getting a sequence number
<stellar-slack> <armed10> We will probably go back to Horizon when the new version (with the importer and horizon in 1 package) is released.
<stellar-slack> <armed10> It does simplify things
<stellar-slack> <sacarlson> my guess is that most errors you see are sequence errors @armed10? as if your hitting it from the same user and it starts working on the next sequence instead of the last. but with feedback that should never happen
<stellar-slack> <armed10> Well the problem is I see no errors. We used to have the sequence errors, but we solved them by only doing about 3 transactions per account with 1000 transactions in between
<stellar-slack> <armed10> The system is probably stuffed, not able to see the error of a transaction immediately and than sends PENDING as the status.
<stellar-slack> <armed10> We're running it only pretty old laptops after all
<stellar-slack> <sacarlson> can you release the test jig software for us to see?
<stellar-slack> <armed10> I'm not allowed to release any software I'm afraid
<stellar-slack> <sacarlson> afraid of what?
<stellar-slack> <sacarlson> that we won't like it?
<stellar-slack> <armed10> It's a figure of speach, I actually signed an agreement that does not allow me to share about anything
<stellar-slack> <sacarlson> oh IC
<stellar-slack> <sacarlson> well I can generate a jig the can be released that I can publish to prove speed
<stellar-slack> <armed10> That's actually a much better idea than the current setup I have
<stellar-slack> <armed10> Although our setup mimics a real network better
<stellar-slack> <sacarlson> with multi transaction envelopes I would think your numbers would be about 100X faster
<stellar-slack> <armed10> Yes, but having multiple nodes across the country would not be able to reproduce that speed
<stellar-slack> <armed10> production setup I mean
<stellar-slack> <eno> 1 transaction,100 operations
<stellar-slack> <sacarlson> I would just hit a single standalone core to start just to get some idea, they you could point it at testnet for 60 sec on another test
<stellar-slack> <raymens> 1 transaction currently, by default, supports only 20 operations right?
<stellar-slack> <raymens> Oh, thanks. I thought it was 20 :) Not sure why
<stellar-slack> <bartek> you can add up to 20 signatures
<stellar-slack> <raymens> Ah I see, I mis-remembered because of the 20 signatures allowed probably
<stellar-slack> <raymens> yeah I guess
<stellar-slack> <sacarlson> I think I originally thought that also until I wrote our pool distrubution transaction that allows up to 100
<stellar-slack> <sacarlson> oh ya 20 signers max per account
<stellar-slack> <armed10> Given 100 operations per transaction, I can only let 20 accounts sign it, so I can't have 100 operations from 100 accounts in one transaction?
<stellar-slack> <dzham> exactly
<stellar-slack> <dzham> and you get one account that pays all the fees, and one slot for a memo
nivah has quit [Ping timeout: 240 seconds]
<stellar-slack> <armed10> Would anyone have a suggestion as to checking if a transaction was successful?
<stellar-slack> <bartek> `txresult` is `TransactionResultPair` (simply use http://stellar.github.io/xdr-viewer/ to decode)
<stellar-slack> <bartek> however, I'm not sure if bad sequence number errors are registered there
stellar-slack1 has joined #stellar-dev
<stellar-slack> <armed10> I'm not sure what to use as to finding my transaction, is there some id the transaction has before sending it off or something?
<stellar-slack1> <armed10> I'm not sure what to use as to finding my transaction, is there some id the transaction has before sending it off or something?
<stellar-slack1> <bartek> every tx has a hash: `txid` in DB and `transaction.hash()` in js sdk (https://stellar.github.io/js-stellar-sdk/Transaction.html#hash)
<stellar-slack1> <armed10> thanks
stellar-slack has quit [Ping timeout: 240 seconds]
<stellar-slack1> <jed> Armed10 There are stress tests built into stellar-core now. Graydon ^
<stellar-slack1> <armed10> @jed: I know, but we wanted to test a little closer to a real-life situation as well as learn about the transaction process from a client perspective.
<stellar-slack1> <jed> OK well I think the txs most be failing for some reason other than load. If loaded the ledger would just take longer to close. Nothing should be lost.
<stellar-slack1> <jed> How many nodes are in the test?
<stellar-slack1> <armed10> Does horizon check transaction validation before forwarding it to a node?
<stellar-slack1> <armed10> @jed: currently 4 nodes, all validator, 2 of them full validator
<stellar-slack1> <armed10> meaning those 2 write history accessible to other nodes
<stellar-slack1> <jed> And all the txs are submitted to one of the nodes?
<stellar-slack1> <armed10> Yes
<stellar-slack1> <armed10> Well, it's weekend for me. I'll speak to you all on monday :)
<stellar-slack1> <armed10> Have a nice weekend\
<stellar-slack1> <jed> OK see you
<stellar-slack1> <jed> I think it could be a problem opening too many http requests to one node if you are not waiting for some completion from each submission.
koshii has quit [Ping timeout: 248 seconds]
koshii has joined #stellar-dev
bit2017 has joined #stellar-dev
acetakwas has joined #stellar-dev
dobson has quit [*.net *.split]
dobson has joined #stellar-dev
acetakwas has quit [Ping timeout: 244 seconds]