<stellar-slack>
<irisli> I looked at the Change Trust operation and in the xdr struct, it says that the `limit` to a trust line is a `int64` value. What is the intended meaning of this over using `uint64` here?
<stellar-slack>
<irisli> would you have any insights to this @graydon?
<stellar-slack>
<graydon> you mean why is it signed rather than unsigned?
<stellar-slack>
<graydon> if so, I believe just consistency with other uses of amounts. all amounts (of assets) expressed anywhere in the XDR are signed types. balances, offers, payments, fees, limits, etc.
<stellar-slack>
<graydon> unsigned types are only used for timestamps and identifiers / indexes
<stellar-slack>
<irisli> Ah okay. It makes a lot of sense now because it would be weird to have a limit twice the maximum possible for the value being limited
<stellar-slack>
<graydon> yes, mixing signed and unsigned within the same domain of discourse tends to produce terrible boundary-condition bugs
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Changing host]
koolhead17 has joined #stellar-dev
bit2017 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
de_henne has quit [Ping timeout: 248 seconds]
<moo-_->
If I write a test case which round trips stellar transaction from internal db account to the network and then back to another internal db account what would be best way to do it?
<moo-_->
run against a test network or run my own node?
<stellar-slack>
<bartek> it creates an isolated single-node network with horizon.
<moo-_->
bartek: perfect!
<moo-_->
I would almost say its joy to work with stellar
<moo-_->
compared to some drug dealing cryptocurrency networks
pixelbeat has joined #stellar-dev
pixelbeat has quit [Quit: Leaving]
Kwelstr has quit [Remote host closed the connection]
bit2017 has quit [Ping timeout: 240 seconds]
bit2017 has joined #stellar-dev
Kwelstr has joined #stellar-dev
<stellar-slack>
<sacarlson> so I take it http://stellar.github.io/ repository is hidden on purpose? 12 hours with no response. What are you guys hiding in there?
<stellar-slack>
<bartek> @sacarlson: sorry, I missed you message. check this out: https://pages.github.com/ there are two types of github pages, for project and for organization. we don't have organization pages. and project page source is always in `gh-pages` branch
<stellar-slack>
<sacarlson> ok IC thanks @bartek
edubai__ has quit [Quit: Connection closed for inactivity]
nivah has joined #stellar-dev
bit2017 has quit [Ping timeout: 250 seconds]
<stellar-slack>
<danielpauljones> @jed: @raymens Thanks for the help, much much appreciated. I have created the tx XDR but when I test in the laboratory post transaction it gives error "Unsupported Media Type" - tried url-encoding and then says that "Input is not valid base64" and gives the same error.
<stellar-slack>
<bartek> looks like a bug in laboratory ^ @iris
<stellar-slack>
<bartek> @danielpauljones: you can try to submit it from JS like this: ``` var server = new StellarSdk.Server('https://horizon-testnet.stellar.org'); server.submitTransaction(_transaction) .then(function(transactionResult) { console.log('Success!') console.log(transactionResult); }) .catch(function (err){ console.log('error') console.log(err); }); ```
<stellar-slack>
<danielpauljones> I will try, can I also do it through a direct POST? That is what I would to do (I think).
<stellar-slack>
<fredolafritte> is there a recent config file for prod somewhere ?
<stellar-slack>
<jed> you can use `stellar-core --inferquorum` and that will tell you who has been externalizing
<stellar-slack>
<fredolafritte> that's much better now
<stellar-slack>
<jed> ok cool
<stellar-slack>
<fredolafritte> oops, after a ctrl-c:
<stellar-slack>
<fredolafritte> 2016-01-22T20:45:47.921 GDE6S [Fs DEBUG] deleting: tmp/catchup-complete-001e6500-879f3059792be51c/ledger-0000457f.xdr.gz 2016-01-22T20:45:47.921 GDE6S [Fs DEBUG] deleting: tmp/catchup-complete-001e6500-879f3059792be51c libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: rmdir failed Abort trap: 6
<stellar-slack>
<fredolafritte> is there any doc on `externalizing ` and -`-inferquorum`
<stellar-slack>
<fredolafritte> ?
<stellar-slack>
<jed> inferquorum was just added so we still need to document it in the admin guide
<stellar-slack>
<jed> externalizing is just who has been acting as a validator
<stellar-slack>
<jed> externalizing is the last step in SCP
<stellar-slack>
<jed> saying I attest this value is correct
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<fredolafritte> 2016-01-22T20:46:52.320 GDBZH [default INFO ] Inferred quorum [QUORUM_SET] [ "$lab3", "$lab1", "$nelisky1", "GABMKJM6I25XI4K7U6XWMULOUQIQ27BCTMLS6BYYSOWKTBUXVRJSXHYQ", "$sdf_watcher2", "$sdf_watcher1", "$nelisky2", "$eno" ]
edubai__ has joined #stellar-dev
<stellar-slack>
<fredolafritte> is there any potential issues running prod and testnet on the same machine ? no conflict with tmp dir for instance
<stellar-slack>
<jed> graydon ^
<stellar-slack>
<john> I read that I can run a node on a Mac... But before I Just to get my hands dirty, may I know how much GB the installation and ledger would approximately takes?
<stellar-slack>
<fredolafritte> horizon=# SELECT d.datname AS Name, pg_catalog.pg_get_userbyid(d.datdba) AS Owner, horizon-# CASE WHEN pg_catalog.has_database_privilege(d.datname, 'CONNECT') horizon-# THEN pg_catalog.pg_size_pretty(pg_catalog.pg_database_size(d.datname)) horizon-# ELSE 'No Access' horizon-# END AS SIZE horizon-# FROM pg_catalog.pg_database d horizon-# ORDER BY horizon-# CASE WHEN
<stellar-slack>
pg_catalog.has_database_privilege(d.datname, 'CONNECT') horizon-# THEN pg_catalog.pg_database_size(d.datname) horizon-# ELSE NULL horizon-# END DESC -- nulls first horizon-# LIMIT 20; name | owner | size ----------------+----------+--------- stellar | frederic | 2485 MB horizon | frederic | 1641 MB
<stellar-slack>
<jed> but that is a full node
<stellar-slack>
<jed> you don't need to run a full one
<stellar-slack>
<john> Would you recommend me to install the "archiver" version instead?
<stellar-slack>
<john> @fredolafritte: so that's a total of approx 4GB
<stellar-slack>
<john> Which version do you run
<stellar-slack>
<fredolafritte> it's a version compiled yesterday
<stellar-slack>
<john> which one? I'm just trying to figure out the diff between "watchers" "basic validators" "Archivers" & "Full validators" . The full validators publish into an history archive *which has additional cost.* What does that mean?
<stellar-slack>
<graydon> fredolafritte: you'll want the two different networks to use separate databases (in their connection string) and separate bucket dirs and tmp dirs. also they'll need to use separate ports for their p2p and http connections. otherwise they should be able to coexist.
<stellar-slack>
<graydon> john: the additional cost is that of storage. you're paying to store history (potentially indefinitely) wherever you archive it.
<stellar-slack>
<graydon> john: so for example if you run a watcher or basic validator you'll only be tracking the current ledger, and only paying for the disk space to store the local current state of the ledger as it changes. if you run an archiver / full validator, you're saving checkpoints of all the transactions that occur and all the states that the ledger passes through (delta-compressed) over time. that data set grows withou
<stellar-slack>
even if the ledger isn't growing.
<stellar-slack>
<graydon> (you might be saving history to colder / cheaper storage than the node itself uses, though, like S3. that's what we usually do.)
<stellar-slack>
<john> @graydon: Thanks! Really appreciate your time & explanation. Going to give a try with Google Cloud.
<stellar-slack>
<graydon> np, let me know if you get stuck, happy to help
<stellar-slack>
<fredolafritte> @graydon: running prod and testnet side by side works fine with the parameters mentioned, thanks