Logged Conversation (all times UTC)
[00:36] <stellar-slack> @matschaffer: is there any node run on testnet using sqlite?
[00:37] <stellar-slack> no all are using postgres
[00:39] <stellar-slack> I started a stellar-core and the WAL file exceed 4GB in catching up.
[00:41] <stellar-slack> are you using full history with sqlite?
[00:42] <stellar-slack> i didn't see it in former deployments.
[00:42] <stellar-slack> yes
[00:42] <stellar-slack> yeah not sure if that will work
[00:43] <stellar-slack> CATCHUP_COMPLETE=true
[00:43] <stellar-slack> in memory?
[00:44] <stellar-slack> how many txs from genesis?
[00:44] <stellar-slack> maybe a bug. can you make an issue?
[00:44] <stellar-slack> i saw master account seq is only 11
[00:46] <stellar-slack> yes. i'm collecting more clues for the issue
[00:50] <stellar-slack> lab yes I run stellar-core node in sqlite
[00:51] <stellar-slack> sacarlson: is you node synced with testnet?
[00:51] <stellar-slack> it was yestarday, I'll check
[00:51] <stellar-slack> no it's now "state" : "Joining SCP"
[00:52] <stellar-slack> it ran for over 24 hours with no problems
[00:52] <stellar-slack> what's the size of ".db" and ".db-wal" file?
[00:52] <stellar-slack> I'll check
[00:55] <stellar-slack> 2015-08-25T19:54:03.850 743e66 [140025850402688] [Herder] INFO Lost track of consensus
[00:58] <stellar-slack> I only show 11 transactions from the master account
[01:02] <stellar-slack> thank you sacarlson
[01:03] <stellar-slack> I see a file /buckets/stellar-core.lock I think about the time we lost it
[01:05] <stellar-slack> I'll try restart it to see if it comes back
[01:12] <stellar-slack> try reset all
[01:12] <stellar-slack> maybe you will see db-wal explosion too.
[01:12] <stellar-slack> oh that stellar-core.lock file was aug 24th 6:58pm maybe when I started it
[01:13] <stellar-slack> db-wal is very big at like 300mb+
[01:13] <stellar-slack> looks like it failed almost exactly 24 hours after I started it
[01:14] <stellar-slack> 300mb is normal. mime is increasing in 30MB/s ..
[01:15] <stellar-slack> -rw-r--r-- 1 35840 Aug 26 00:53 stellar.db -rw-r--r-- 1 24641536 Aug 26 01:20 stellar.db-shm -rw-r--r-- 1 3227733136 Aug 26 01:20 stellar.db-wal
[01:16] <stellar-slack> so did you reset your to get it running again?
[01:16] <stellar-slack> every time
[01:17] <stellar-slack> it's the same in my node
[01:17] <stellar-slack> reset all you mean delete all db files I assume
[01:17] <stellar-slack> it look like the ledger replaying is not throttled well
[01:18] <stellar-slack> wow my support software is all writen around sqlite, hope if it's just the sqlite that causes it that it can be fixed
[01:19] <stellar-slack> I'll do a simple shutdown restart to see if it changes before a complete reset
[01:43] <stellar-slack> simple reset without db distruction seems to get my stellar-core back to "state" : "Synced!"
[01:44] <stellar-slack> not sure for how long. I'll let it run for 48 hours or more to see if this happens again
[01:45] <stellar-slack> if it only happens every 24 hours maybe have to write a work around with a task that detects it's lost sync for more than 1 hour to restart it
[01:50] <stellar-slack> synced too. :)
[01:56] <stellar-slack> :+1:
[02:16] <stellar-slack> jed: i filed a issue about this. https://github.com/stellar/stellar-core/issues/717
[02:19] <stellar-slack> I note in your 717 that it didn't mension the freeze or failure to sync. you think that's another issue?
[02:20] <stellar-slack> @lab
[02:21] <stellar-slack> they are seperated
[02:21] <stellar-slack> ok
[04:32] <stellar-slack> can we get a safe quorum on testnet? ^^
[04:33] <stellar-slack> no idea what that means, but i think safe is better than unsafe
[04:34] <stellar-slack> I don't know I guess change the value and find out?
[04:34] <stellar-slack> maybe with such a small number of nodes not so easy?
[05:54] <stellar-slack> Wheeee https://github.com/buhrmi/open-core
[05:55] <stellar-slack> here we goooo :)
[05:55] <stellar-slack> I'll take a look at it
[05:58] <stellar-slack> cool :)
[05:59] <stellar-slack> not enuf documentation for me to run it
[06:03] <stellar-slack> but someone that knew java probly could
[06:07] <stellar-slack> updated the readme a little bit. u don't need Java
[06:07] <stellar-slack> just meteor and a running stellar-core that writes to postgres
[08:53] <stellar-slack> ok I'll look again
[08:54] <stellar-slack> also I seem to be the first gateway on testnet with GBPJR44JZVXBGRXRQ7PN34IUERQOJ64OG44UIF7ICOIUWLN7H5MALVIU
[08:54] <stellar-slack> ready to issue you BEER
[09:41] <stellar-slack> @buhrmi: and with your new docs I think I could even run it, very good
[10:16] <stellar-slack> isn't there a stellar-base.js that i just can include in my project......
[10:16] <stellar-slack> without bower, without npm
[10:16] <stellar-slack> just plain old js?
[10:31] <stellar-slack> (one that works in node *as well as* in the browser)
[10:52] <stellar-slack> @bartek: say i have a base64 encoded xdr in javascript, how to i decode it to inspect the contents?
[10:53] <stellar-slack> i'm trying StellarBase.xdr.TransactionEnvelope.fromXDR(atob(base64)) , but that gives me XDR Read Error: Got 1062733056 when trying to read a bool
[11:01] <stellar-slack> best I have is in ruby and it won't decode everything
[11:03] <stellar-slack> I think at this point I was trying to decode other stuf, only the top will decode if I recall
[11:05] <stellar-slack> but I think it would be cool if we could look at a base64 encoded transaction and put it back to human readable like json
[11:05] <stellar-slack> if that's even posible
[11:29] <stellar-slack> > isn't there a stellar-base.js that i just can include in my project...... @buhrmi: for browser usage you can 1) use bower, 2) copy a `stellar-base.js`/`stellar-base.min.js` file from https://github.com/stellar/bower-js-stellar-base or (-lib) 3) _not ready yet but in the works_ use CDN > say i have a base64 encoded xdr in javascript, how to i decode it to inspect the contents? does `var transaction = new St
[11:29] <stellar-slack> work?
[11:34] <stellar-slack> yes
[11:34] <stellar-slack> lol ... thanks
[11:34] <stellar-slack> easier than expected :)
[11:34] <stellar-slack> :)
[11:53] <stellar-slack> haha... somebody traded BEER http://open-core.meteor.com
[11:53] <stellar-slack> looks at @sacarlson
[11:54] <stellar-slack> ya I stocked up on BEER prepared to trade for sausages
[11:55] <stellar-slack> oh ya that's perfect now you can read the transactions in english
[13:07] <stellar-slack> anyone else still on old the testnet? sequence numbers are acting weird today, all my tx’s have the same seq. all are valid.
[13:08] <stellar-slack> I don't run stellard but I still have code that should work on old stellar
[13:09] <stellar-slack> if only stellarcore was a bit more stable, I’d migrate
[13:10] <stellar-slack> you want me to look at an account balance or something on old stellar?
[13:13] <stellar-slack> not sure if it would help.. individually they all make sense
[13:13] <stellar-slack> currency balances gets updated
[13:13] <stellar-slack> sequence numbers get updated, from 16 to 17
[13:14] <stellar-slack> but then all tx’s have seq# 16
[13:14] <stellar-slack> :)
[13:14] <stellar-slack> I just checked balance of my old account and it's still there
[13:15] <stellar-slack> I never looked at seq# so I'm not sure. it didn't seem important on stellard
[13:15] <stellar-slack> well, they are supposed to be increasing
[13:15] <stellar-slack> and if you send a tx with an old seq# you should get an error
[13:16] <stellar-slack> right now it’s the other way around :S
[13:16] <stellar-slack> ya that would make sence but I'm not sure seq# is even visible from api
[13:16] <stellar-slack> are you running stellard?
[13:17] <stellar-slack> no, just connecting to http://test.stellar.org|test.stellar.org
[13:17] <stellar-slack> it has to be visible, otherwise you can’t sign your own tx's
[13:18] <stellar-slack> ok well none of my code even looks for it. I never signed my tx I did it direct low security
[13:18] <stellar-slack> :)
[13:33] <stellar-slack> developing with stellar core is what taking the red pill must feel like
[13:33] <stellar-slack> matrix ya
[13:34] <stellar-slack> haven't watched it in aaages
[13:36] <stellar-slack> trying to build stellar-core on ubuntu 13.04. the configure step fails with this message : './configure: line 16441: syntax error near unexpected token `sqlite3,'' even if sqlite3 and libsqlite3-dev are installed :(
[13:37] <stellar-slack> @regisg: no clue, I only ever built it on 14.04
[13:40] <stellar-slack> I'll try on 14.04
[13:42] <stellar-slack> see buhrmi with your site running people are now getting more confident that it might work
[13:45] <stellar-slack> and they can see we trade in BEER
[13:46] <stellar-slack> the only real currency
[13:46] <stellar-slack> hehe yeah i, i wanna work on the UI tomorrow if i find time
[13:46] <stellar-slack> some CSS
[13:48] <stellar-slack> @regisg: good luck ^^ as long as the number of nodes is not that big you can confirm that the network sees your node here: http://open-core.meteor.com (at the bottom)
[13:50] <stellar-slack> I saw my IP listed twice I guess at some point when my ip changed
[13:50] <stellar-slack> I saw my old and new
[13:51] <stellar-slack> cool, yeah takes some time to notice that a node is gone..
[13:51] <stellar-slack> oh and mine is stuck again "state" : "Joining SCP"
[13:52] <stellar-slack> hope they gonna add IPv6 support for stellar-core
[13:53] <stellar-slack> I see mines been stuck now for 10 minutes so I guess it needs a restart
[13:53] <stellar-slack> buhrmi: so yours has run for more than 24 hours without this problem?
[13:54] <stellar-slack> yeah
[13:54] <stellar-slack> now that I have postgres figured out I can migrate to that to see if it improves things.
[13:55] <stellar-slack> looks like sqlite version might be broken or just unstable
[13:57] <stellar-slack> sqlite3 was never meant as a production database anyway
[13:58] <stellar-slack> according to the developer
[13:58] <stellar-slack> well I should have 24 hours to fix it so I'll do that tomaro
[13:59] <stellar-slack> time for some BEER
[13:59] <stellar-slack> haha
[13:59] <stellar-slack> i wonder ...
[13:59] <stellar-slack> if you issue BEER, and somebody else also issues BEER
[13:59] <stellar-slack> and I accept the BEER as payment
[14:00] <stellar-slack> will it become the same BEER?
[14:02] <stellar-slack> a asset/currency is defined by its name + its issuer
[14:04] <stellar-slack> k so sacarlson has to make sure that his beer is the best beer
[14:07] <stellar-slack> man, minified stellar-base.js is over 250kb
[14:15] <stellar-slack> xdr encoder decoder ...
[15:21] <stellar-slack> buhrmi: no my BEER is not the best beer but it is my favorite beer Leo Beer that is a Thai brand in 330ml can container per unit of trade
[15:23] <stellar-slack> cool
[15:24] <stellar-slack> hope i can get some time sponsored by my company to put into stellar
[15:24] <stellar-slack> trade does not include shiping. pick up at Soi 13 and beach road in Pattaya
[15:25] <stellar-slack> okay
[15:25] <stellar-slack> no idea how to get there but oka
[15:25] <stellar-slack> I'll throw in one of my girls if you buy 20 cases
[15:25] <stellar-slack> I'll publish the GPS lat long later
[15:26] <stellar-slack> loool
[16:55] <stellar-slack> wee just saw a "setoptions" tx on the network
[16:57] <stellar-slack> wierd doesn't it need an account?
[17:01] <stellar-slack> and I thought the code for native was native not "code":"XLMu0000"
[17:17] <stellar-slack> @sacarlson: it’s only an internal js-stellar-base representation. it’s native in a ledger: https://horizon-testnet.stellar.org/operations/1708705494077440
[17:18] <stellar-slack> i think a valid definintion of "native currency" is simply "asset that does not have an issuer"
[17:18] <stellar-slack> correct me if i'm wrong
[17:20] <stellar-slack> I just put up the first manageOffer, asset: , dest: that is 24 beers for 1.25 usd each
[17:20] <stellar-slack> @sacarlson: lol awesome... should add "latest offers" section to open core
[17:21] <stellar-slack> @buhrmi: well, it depends, in js-stellar-base it's a correct definition, however in XDR there is a special type for native currency: `AssetType.assetTypeNative`. js-stellar-base will set correct type during transformation of `Asset` object to XDR.
[17:21] <stellar-slack> I can see it on you open-core already
[17:21] <stellar-slack> but not the price
[17:22] <stellar-slack> it works that way for developers’ convinience so you don’t have to think which internal type you need, you just create an asset by calling `Asset.native()` or `new Asset(code, issuer)`.
[17:22] <stellar-slack> yeah, need to put more work into it to show all the data and have a nicer UI
[17:22] <stellar-slack> @bartek: yeah I guess that's cool
[17:24] <stellar-slack> my initial idea was to kinda "fork" the network without XLM/lumens ... only assets
[17:25] <stellar-slack> you can do with just a small change in configs
[17:25] <stellar-slack> yet untested
[17:25] <stellar-slack> yeah as long as an account can be used without having received native currency
[17:26] <stellar-slack> ya it has min ballance you can set to zero
[17:26] <stellar-slack> k... but i gonna wait a bit more and do some UI work before doing that
[17:26] <stellar-slack> min trans cost and min balance not sure I have the config name correct
[17:27] <stellar-slack> ya and we also see some of the bugs now with more nodes connected
[17:28] <stellar-slack> ok its my nap time
[17:28] <stellar-slack> mine too haha
[17:29] <stellar-slack> cya
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of