<stellar-slack>
<monsieurnicolas> @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.
<stellar-slack>
<matschaffer> :thumbsup:
koolhead17 has quit [Remote host closed the connection]
<stellar-slack>
<modernity> ok, figured out that i didn't install flex and bison properly. that is now done.
<stellar-slack>
<modernity> 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
<stellar-slack>
<modernity> when i try compiling Stellar-ledger.x directly in VC++, i get the following errors
<stellar-slack>
<matschaffer> 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
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<matschaffer> 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.
<stellar-slack>
<matschaffer> 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
<stellar-slack>
<matschaffer> like outside of the commander
<stellar-slack>
<matschaffer> so commander will only be concerned with start up, run transactions, shut down. Then an analyzer checks the resulting artifacts
Kwelstr has quit [Ping timeout: 265 seconds]
Kwelstr has joined #stellar-dev
HostFat has joined #stellar-dev
<stellar-slack>
<monsieurnicolas> @modernity: can you share detail on what you mean by "flex/bison" not installed properly? Did you take the mingw or the cygwin route?
<stellar-slack>
<monsieurnicolas> @modernity: the input files are in the src/xdr folder, src/generated is the output. Did you try to run the command manually like I asked before to see if you get any more clues?
nelisky has joined #stellar-dev
<stellar-slack>
<donovan> Just reading though some of the SCP code and have noticed the pattern of nested callbacks in processEnvelope:
<stellar-slack>
Was wondering if this code has its heritage in a prototype in a more functional language and this explains that pattern?
<stellar-slack>
<donovan> Also trying to ascertain what the intended threading model of SCP is. Using async callbacks with copying seems to suggest it may run on multiple threads, but previously it was mentioned that stellar-core was intended to be single-threaded:
<stellar-slack>
<monsieurnicolas> We're in the middle of rewriting this, so a bunch of this is going to change.
<stellar-slack>
Yes, it was prototyped in Javascript
<stellar-slack>
<monsieurnicolas> as far as async: yes for the most part it's a single thread that is running. The copy is not because it runs on multiple threads, more that the execution is postponed due to an async call (therefore the current stack gets destroyed)
<stellar-slack>
<monsieurnicolas> single threaded != synchronous in this case
<stellar-slack>
<donovan> Thanks for the answers :simple_smile: Was just spending some time trying to understand the various states of Slot, Ballot, Node and the SCP instance itself, and found myself a bit confused when trying to decode the lambda captures. I guess the aim is to be able to flow through the different classes and come to various conclusions, it just can make the C++ a bit harder to read than perhaps the JS might have
<stellar-slack>
<donovan> Also, Go has channels and trying to map the SCP dataflow into that model is a fun challenge!
TheSeven has quit [Ping timeout: 256 seconds]
TheSeven has joined #stellar-dev
<stellar-slack>
<monsieurnicolas> Don't spend time on SCP just yet. Well, you can but be aware that David made a bunch of changes to the paper following feedback, there are some simplifications and there are some steps that were not really specified before (like the initial ballot selection)
<stellar-slack>
<donovan> Ok, might have another look at the XDR encoding for now. Is there a public branch where the new SCP implementation can be tracked? Also is there some way a changelog could be published for the paper? Would help keeping track of what’s happening :simple_smile:
<stellar-slack>
<monsieurnicolas> re: changelog, I'll ask David about that.
<stellar-slack>
SCP branch, I'll get it out there as soon as possible. I started to make changes but postponed it to this week as there was further iterations
<stellar-slack>
<donovan> Great, will keep my eyes peeled for commits :simple_smile: Thanks again.
nelisky has quit [Quit: nelisky]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
nelisky has joined #stellar-dev
<stellar-slack>
<dzham> What’s the status on js-stellar-lib? I’m getting "ReferenceError: err is not defined” every time I try to submit a tx
<stellar-slack>
<andrew> on master?
<stellar-slack>
<dzham> from npm
<stellar-slack>
<andrew> let me publish the latest master to npm
<stellar-slack>
<dzham> That’s be awesome, Andrew!
<stellar-slack>
<andrew> try version 0.0.7
<stellar-slack>
<dzham> ok, just did my first set of transactions… multi-sig token payment