Logged Conversation (all times UTC)
[02:33] <stellar-slack> kwelstr: did it sync with testnet?
[02:35] <stellar-slack> I have several connected peers, most are 54. and one 104.
[02:36] <stellar-slack> i am using the configuration file from the example
[02:37] <stellar-slack> the 54 are from amazon, and the 104 is mountain view
[02:37] <stellar-slack> right?
[02:39] <stellar-slack> the top gives me very little resources usage, I could run this on my on desktop
[02:42] <stellar-slack> ok, looks like the 104 IP is my machine, so I am connected to all the 54 IPs
[02:53] <stellar-slack> kwelstr: lovely. Yeah, it’s pretty lightweight from what I’ve seen as well
[02:54] <stellar-slack> kwelstr: peers are good. /info should report synced if all is well
[02:54] <stellar-slack> heh… might not though
[02:54] <stellar-slack> just looked and testnet isn’t making progress at the moment
[02:55] <stellar-slack> so you might just get `"state" : "Joining SCP”`
[02:55] <stellar-slack> uhm, my info says things like: INFO New connected peer 54.161.230.185:39133
[02:55] <stellar-slack> what’s `curl localhost:39132/info` show you?
[02:56] <stellar-slack> assuming it’s on your desktop and with a default http port setting anyway
[02:56] <stellar-slack> {
[02:56] <stellar-slack> "info" : {
[02:56] <stellar-slack> "ledger" : {
[02:56] <stellar-slack> "age" : 2955,
[02:56] <stellar-slack> "closeTime" : 0,
[02:56] <stellar-slack> "hash" : "41310a0181a3a82ff13c049369504e978734cf17da1baf02f7e4d881e8608371",
[02:56] <stellar-slack> "num" : 2
[02:56] <stellar-slack> },
[02:56] <stellar-slack> "numPeers" : 3,
[02:56] <stellar-slack> "state" : "Joining SCP"
[02:56] <stellar-slack> }
[02:56] <stellar-slack> }
[02:56] <stellar-slack> yep
[02:56] <stellar-slack> so if it’s really all working, that state line will say “Synced!” or something to that effect
[02:56] <stellar-slack> jed: monsieurnicolas: testnet stopped again, want me to kick it?
[02:56] <stellar-slack> ok, so when it says Synced then we're there
[02:57] <stellar-slack> yep
[02:57] <stellar-slack> but good that it’s running at least
[02:58] <stellar-slack> yeah, it built pretty fast too, once I got all the right packages installed
[02:58] <stellar-slack> nice!
[02:58] <stellar-slack> running some version of Ubuntu on google cloud
[04:01] <stellar-slack> @modernity: you can try to run the xdrc command manually.
[04:01] <stellar-slack> open a cmd window in the BuildsVisualStudio2015 folder
[04:01] <stellar-slack> then run
[04:01] <stellar-slack> x64Debugxdrc.exe -hh -o ....srcgeneratedStellar-ledger.h ....srcxdr/Stellar-ledger.x
[04:01] <stellar-slack> and see what happens
[04:05] <stellar-slack> @matschaffer: I kicked Testnet myself. Probably still the same bug. I imagine it's the next thing we're going to look into this week as we've addressed most API related issues at this point.
[04:08] <stellar-slack> :thumbsup:
[06:37] <stellar-slack> ok, figured out that i didn't install flex and bison properly. that is now done.
[06:38] <stellar-slack> however, i looked in the generated dir and i don't see the Stellar-ledger.x that's supposed to be input for xdrc.exe
[06:39] <stellar-slack> when i try compiling Stellar-ledger.x directly in VC++, i get the following errors
[07:03] <stellar-slack> scott: rfr https://github.com/stellar/stellar_core_commander/pull/1 - looks like I should be able to use this for the delivery pipeline. Hopefully this is still in use despite the work on go-horizon
[10:45] <stellar-slack> "info" : {
[10:45] <stellar-slack> "ledger" : {
[10:45] <stellar-slack> "age" : 31125,
[10:45] <stellar-slack> "closeTime" : 0,
[10:45] <stellar-slack> "hash" : "41310a0181a3a82ff13c049369504e978734cf17da1baf02f7e4d881e8608371",
[10:45] <stellar-slack> "num" : 2
[10:45] <stellar-slack> },
[10:45] <stellar-slack> "numPeers" : 3,
[10:45] <stellar-slack> "state" : "Catching up"
[12:09] <stellar-slack> also was considering something like this for generalizing process-specific options. Not sure I wanna PR until I’m sure it’ll actually fit the use case. Also need to figure out what’s a good way to make assertions on the results of these recipes.
[12:10] <stellar-slack> wondering if it might be best to separate the assertions into their own space. Something the slurps in the postgres results and works from there
[12:10] <stellar-slack> like outside of the commander
[12:12] <stellar-slack> so commander will only be concerned with start up, run transactions, shut down. Then an analyzer checks the resulting artifacts
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of