<stellar-slack>
<ericwheeler> says it can't find flex but it's installed
<stellar-slack>
<ericwheeler> did I need to add the no postgres thing again?
<stellar-slack>
<graydon> hm
<stellar-slack>
<ericwheeler> Almost wish I was running Ubuntu on this unit but only have it installed vis crouton on my Chromebook
<stellar-slack>
<graydon> `flex --version` ?
<stellar-slack>
<graydon> it's ok, this is ... painful but also educational, shows us what we've documented badly or where we've baked-in assumptions that aren't as portable as we want
<stellar-slack>
<graydon> I mean, I'm sorry you're going through it!
<stellar-slack>
<ericwheeler> flex 2.5.37
<stellar-slack>
<ericwheeler> I am learning so I am totally fine
<stellar-slack>
<graydon> where do you see it say it doesn't have flex?
<stellar-slack>
<ericwheeler> I would consider myself a GUI Linux user in that I am not a programmer
<stellar-slack>
<graydon> mm. so 'missing' is actually a program that's part of automake, it's not telling you that you're missing flex, it's just an invocation wrapper for certain potentially-missing features
<stellar-slack>
<graydon> I wonder if you're on a version of automake that's problematic, hmm.
<stellar-slack>
<graydon> (or autoconf? I can never remember which one 'missing' is a part of)
<stellar-slack>
<ericwheeler> automake --version?
<stellar-slack>
<graydon> yeah
<stellar-slack>
<graydon> and autoconf --version
<stellar-slack>
<graydon> *sigh* autotools
<stellar-slack>
<ericwheeler> I'm seeing a pattern
<stellar-slack>
<ericwheeler> utomake (GNU automake) 1.15 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later http://gnu.org/licenses/gpl-2.0.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by Tom Tromey tromey@redhat.com and Alexandre Duret-Lutz adl@gnu.org.
<stellar-slack>
<graydon> autotools is not .. my favourite set of software.
<stellar-slack>
<graydon> (though I am friends with many of its maintainers!)
<stellar-slack>
<graydon> that's quite a recent automake, yeah
<stellar-slack>
<graydon> ok
<stellar-slack>
<ericwheeler> autoconf (GNU Autoconf) 2.69 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+/Autoconf: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html, http://gnu.org/licenses/exceptions.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by David J. MacKenzie and Akim Demaille.
<stellar-slack>
<graydon> hmm I've seen the bug you're hitting before. I'm just trying to remember what on earth caused it.
<stellar-slack>
<ericwheeler> the wordpress guy puts all that kind of stuff in his blog so he can find it again lol
<stellar-slack>
<graydon> I know this is obnoxious to ask, but can I ask you to basically restart configuration from a clean checkout?
<stellar-slack>
<graydon> that is, go into stellar-core and type `git clean -dxf` and have it delete everything
<stellar-slack>
<ericwheeler> sure np
<stellar-slack>
<graydon> then, given that you've got the submodules checked out now, do the `./autogen.sh && ./configure.sh && make` thing
<stellar-slack>
<graydon> it's possible there was some confusion cached in the configuration script that initially ran on the partial checkout (before you had the submodules checked out)
<stellar-slack>
<graydon> (or like maybe it got itself convinced it had to compensate for missing flex before you installed flex, or something)
<stellar-slack>
<ericwheeler> so ./configure gripes about not having libpq and make gives: make make: *** No targets specified and no makefile found. Stop.
<stellar-slack>
<ericwheeler> on the ./configure do I need to add the no postgres thing?
<stellar-slack>
<graydon> oh, yes
<stellar-slack>
<graydon> I forgot you decided to forgo postgres, sorry
<stellar-slack>
<ericwheeler> so it would be ./configure --no postgres?
<stellar-slack>
<ericwheeler> looks like it might be in a loop
<stellar-slack>
<ericwheeler> wno-unused command line argument
<stellar-slack>
<graydon> that's compiling!
<stellar-slack>
<graydon> I mean assuming it's saying things in between those :)
<stellar-slack>
<ericwheeler> ok
<stellar-slack>
<ericwheeler> yes
<stellar-slack>
<graydon> I keep meaning to figure out how to get rid of that warning
<stellar-slack>
<ericwheeler> on that ever growing list of things to do eh?
<stellar-slack>
<graydon> it's a bit of a muddle. clang will warn if you pass it unused command line options. which you can disable sometimes. but only in certain versions.
<stellar-slack>
<graydon> and so if you try to turn _off_ that behavior, in other versions you get a different warning (about not understanding the turning-off)
<stellar-slack>
<graydon> *sigh* compilers
<stellar-slack>
<ericwheeler> not many other options?
<stellar-slack>
<ericwheeler> do you think it would run well on a Chromebook running Kubuntu in crouton?
<stellar-slack>
<ericwheeler> does 'make' generate an error log?
<stellar-slack>
<graydon> hm. did you get anything a little before that?
<stellar-slack>
<graydon> like an error from the compiler?
<stellar-slack>
<graydon> there's no specific log from make, no
<stellar-slack>
<graydon> I don't know what crouton is
<stellar-slack>
<ericwheeler> crouton allows you to install an OS in chroot on chromebooks
<stellar-slack>
<ericwheeler> In file included from ../lib/soci/src/core/soci.h:34:0, from ./database/Database.h:9, from ./overlay/Peer.h:11, from ./overlay/LoopbackPeer.h:7, from overlay/OverlayTests.cpp:6: ../lib/soci/src/core/session.h:43:41: warning: ‘templateclass class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] void
<stellar-slack>
set_query_transformation_(std::auto_ptrdetails::query_transformation_function qtf); ^ In file included from /usr/include/c++/5.1.1/memory:81:0, from ./main/Application.h:7, from overlay/OverlayTests.cpp:5: /usr/include/c++/5.1.1/bits/unique_ptr.h:49:28: note: declared here templatetypename class auto_ptr; ^ In f
<stellar-slack>
../lib/soci/src/core/soci.h:34:0, from ./database/Database.h:9, from ./overlay/Peer.h:11, from ./overlay/LoopbackPeer.h:7, from overlay/OverlayTests.cpp:6: ../lib/soci/src/core/session.h: In member function ‘void soci::session::set_query_transformation(T)’: ../lib/soci/src/core/session.h:80:14: warning: ‘templateclass class std::auto_ptr’ is
<stellar-slack>
std::auto_ptrdetails::query_transformation_function qtf(new details::query_transformationT(callback)); ^ In file included from /usr/include/c++/5.1.1/memory:81:0, from ./main/Application.h:7, from overlay/OverlayTests.cpp:5: /usr/include/c++/5.1.1/bits/unique_ptr.h:49:28: note: declared here templatetypename class auto_ptr; ^
<stellar-slack>
<graydon> so far those are all warnings. annoying but just warnings
<stellar-slack>
<graydon> what comes next?
<stellar-slack>
<ericwheeler> it looks like that was repeated for quite a while
<stellar-slack>
<ericwheeler> this seems to repeat In file included from /usr/include/c++/5.1.1/memory:81:0, from ../lib/soci/src/core/rowset.h:14, from ../lib/soci/src/core/soci.h:33, from ./database/Database.h:9, from overlay/LoadManager.cpp:5: /usr/include/c++/5.1.1/bits/unique_ptr.h:49:28: note: declared here templatetypename class auto_ptr;
<stellar-slack>
../lib/soci/src/core/soci.h:34:0, from ./database/Database.h:9, from overlay/LoadManager.cpp:5: ../lib/soci/src/core/session.h:43:41: warning: ‘templateclass class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] void set_query_transformation_(std::auto_ptr<details::query_tr ^ In file included from /usr/include/c++/5.1.1/memo
<stellar-slack>
../lib/soci/src/core/rowset.h:14, from ../lib/soci/src/core/soci.h:33, from ./database/Database.h:9, from overlay/LoadManager.cpp:5: /usr/include/c++/5.1.1/bits/unique_ptr.h:49:28: note: declared here templatetypename class auto_ptr;
<stellar-slack>
<graydon> no doubt. it looks like they deprecated a lot of stuff in 5.x. yuck.
<stellar-slack>
<ericwheeler> wish I was more help
<stellar-slack>
<graydon> anyway those are all still warnings
<stellar-slack>
<graydon> need something that begins with "error:"
<stellar-slack>
<ericwheeler> ok brb
<stellar-slack>
<ericwheeler> from ../lib/asio/include/asio/basic_datagram_socket.hpp:20, from ../lib/asio/include/asio.hpp:19, from ./util/asio.h:65, from main/main.cpp:4: ../lib/asio/include/asio/error.hpp: At global scope: ../lib/asio/include/asio/error.hpp:256:36: warning: ‘asio::error::system_category’ defined but not used [-Wunused-variable] static const asio::error_cate
<stellar-slack>
^ ../lib/asio/include/asio/error.hpp:258:36: warning: ‘asio::error::netdb_category’ defined but not used [-Wunused-variable] static const asio::error_category& netdb_category ^ ../lib/asio/include/asio/error.hpp:260:36: warning: ‘asio::error::addrinfo_category’ defined but not used [-Wunused-variable] static const asio::error_category& addrinfo_category
<stellar-slack>
../lib/asio/include/asio/error.hpp:262:36: warning: ‘asio::error::misc_category’ defined but not used [-Wunused-variable] static const asio::error_category& misc_category ^ cc1plus: warning: unrecognized command line option ‘-Wno-unused-local-typedef’ cc1plus: warning: unrecognized command line option ‘-Wno-unused-command-line-argument’
<stellar-slack>
<ericwheeler> seems that's as far back as it goes
<stellar-slack>
<ericwheeler> unless there's a way to go further back
<stellar-slack>
<graydon> try typing 'make >make.log 2>&1' and uploading the results (here or on gist or pastebin or something)
<stellar-slack>
<ericwheeler> sounds like it's crunching numbers for Seti
rejon has joined #stellar-dev
<stellar-slack>
<graydon> C++ is challenging on computers, yes
<stellar-slack>
<ericwheeler> no output yet
<stellar-slack>
<ericwheeler> nothing yet-guess it has a lot to say
<stellar-slack>
<graydon> there should not be output. it should be writing all output to make.log
<stellar-slack>
<ericwheeler> I don't see an output or a file called make.log in the directory
<stellar-slack>
<graydon> uh oh
<stellar-slack>
<sacarlson> I'm not sure but I see this line mv: cannot move ‘http://tmp-scan.cc|tmp-scan.cc’ to ‘../lex.yyxdrc/scan.cc’: No such file or directory. might that mean he doesn't have permision to create files? not likly
<stellar-slack>
<graydon> no, that's a bug from a while back when the configury got confused about the presence of flex
<stellar-slack>
<ericwheeler> when it was 'making' it looked like it looped
<stellar-slack>
<graydon> it ... really should never loop. I would be very surprised. can you hit ctrl-C?
<stellar-slack>
<ericwheeler> it's not running
<stellar-slack>
<ericwheeler> I have 3 files
<stellar-slack>
<graydon> hm?
<stellar-slack>
<graydon> you are in the stellar-core directory, yes?
<stellar-slack>
<graydon> there should be quite a lot of files!
<stellar-slack>
<ericwheeler> yes there are other files those are just the files named make
<stellar-slack>
<graydon> ok, sorry. I'm .. not sure what happened or why you wouldn't get a log file
<stellar-slack>
<graydon> what happens when you run 'make' on its own?
<stellar-slack>
<graydon> the file make.log is there
<stellar-slack>
<ericwheeler> make all-recursive make[1]: Entering directory '/home/ewheeler/stellar-core' Making all in lib make[2]: Entering directory '/home/ewheeler/stellar-core/lib' Making all in ../lib/libsodium make[3]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium' Making all in dist-build make[4]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/dist-build' make[4]: Nothing to be done for 'all
<stellar-slack>
'/home/ewheeler/stellar-core/lib/libsodium/dist-build' Making all in msvc-scripts make[4]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/msvc-scripts' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium/msvc-scripts' Making all in src make[4]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/src' Making all in libsodium make[5]: En
<stellar-slack>
'/home/ewheeler/stellar-core/lib/libsodium/src/libsodium' Making all in include make[6]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/src/libsodium/include' make[6]: Nothing to be done for 'all'. make[6]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium/src/libsodium/include' make[6]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/src/libsodium' make[6]: Nothing to be done
<stellar-slack>
directory '/home/ewheeler/stellar-core/lib/libsodium/src/libsodium' make[5]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium/src/libsodium' make[5]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/src' make[5]: Nothing to be done for 'all-am'. make[5]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium/src' make[4]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium/src
<stellar-slack>
directory '/home/ewheeler/stellar-core/lib/libsodium/test' Making all in default make[5]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/test/default' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium/test/default' make[5]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium/test' make[5]: Nothing to be done for 'all-am'. make[5]: Le
<stellar-slack>
'/home/ewheeler/stellar-core/lib/libsodium/test' make[4]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium/test' make[4]: Entering directory '/home/ewheeler/stellar-core/lib/libsodium' make[4]: Nothing to be done for 'all-am'. make[4]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium' make[3]: Leaving directory '/home/ewheeler/stellar-core/lib/libsodium' Making all in ../lib/xdrpp make[3]: En
<stellar-slack>
'/home/ewheeler/stellar-core/lib/xdrpp' make all-am make[4]: Entering directory '/home/ewheeler/stellar-core/lib/xdrpp' pandoc -s -w man ./doc/xdrc.1.md -o ./doc/xdrc.1 make[4]: pandoc: Command not found Makefile:1766: recipe for target 'doc/xdrc.1' failed make[4]: [doc/xdrc.1] Error 127 (ignored) make[4]: Leaving directory '/home/ewheeler/stellar-core/lib/xdrpp' make[3]: Leaving directory '/home/ewheeler/stellar-c
<stellar-slack>
directory '/home/ewheeler/stellar-core/lib' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/home/ewheeler/stellar-core/lib' make[2]: Leaving directory '/home/ewheeler/stellar-core/lib' Making all in src make[2]: Entering directory '/home/ewheeler/stellar-core/src' make all-am make[3]: Entering directory '/home/ewheeler/stellar-core/src' make[3]: Leaving directory '/home/ewheeler/stellar-core/
<stellar-slack>
<graydon> I believe `docs/stellar-core_testnet.cfg` also contains a nearly-correct testnet config
<stellar-slack>
<ericwheeler> back up to what commands I would run
<stellar-slack>
<sacarlson> mine might be a bit old but still works at the moment
<stellar-slack>
<graydon> at that point you follow the setup instructions, like `stellar-core --conf docs/stellar-core_testnet.cfg --newdb` to initialize a database, then `stellar-core --conf docs/stellar-core_testnet.cfg` to connect
<stellar-slack>
<ericwheeler> ok
<stellar-slack>
<sacarlson> what graydon provided also looks good
<stellar-slack>
<graydon> or I guess `src/stellar-core ...` in those commands
<stellar-slack>
<sacarlson> I have a bad memory so I create scripts to do that stuf
<stellar-slack>
<graydon> at that point it should connect and attempt a minimal catchup. there'll be a pause of up to 5 minutes while it waits for a checkpoint to read from the public history, then it should be in sync
<stellar-slack>
<graydon> yes
<stellar-slack>
<sacarlson> ya that's a good one
<stellar-slack>
<ericwheeler> so I would type those commands in the bash shell?
<stellar-slack>
<ericwheeler> bash: src/stellar-core: No such file or directory
<stellar-slack>
<graydon> are you in the stellar-core directory?
<stellar-slack>
<ericwheeler> ls: bucket database history main http://Makefile.am|Makefile.am overlay scp http://src.mk|src.mk StellarCoreVersion.h transactions xdr crypto herder ledger Makefile http://Makefile.in|Makefile.in process simulation stellar-core test util
<stellar-slack>
<ericwheeler> src
<stellar-slack>
<graydon> you're in stellar-core/src
<stellar-slack>
<graydon> go up a directory
<stellar-slack>
<ericwheeler> 2015-10-06T18:36:40.401 5712c2 [140443028215616] [default] INFO Application constructing (worker threads: 4) 2015-10-06T18:36:40.402 5712c2 [140443028215616] [Database] INFO Connecting to: sqlite3://stellar.db 2015-10-06T18:36:42.146 5712c2 [140443028215616] [default] INFO * 2015-10-06T18:36:42.146 5712c2 [140443028215616] [default] INFO * The database has been initialized 2015-10-06T18:36:42.146
<stellar-slack>
* 2015-10-06T18:36:42.147 5712c2 [140443028215616] [SCP] INFO LocalNode::LocalNode@5712c2 qSet: 87d6c4 2015-10-06T18:36:42.214 5712c2 [140443028215616] [Ledger] INFO Established genesis ledger, closing 2015-10-06T18:36:42.214 5712c2 [140443028215616] [Ledger] INFO Root account seed: SDHOAMBNLGCE2MV5ZKIVZAQD3VCLGP53P3OBSBI6UN5L5XZI5TKHFQL4 2015-10-06T18:36:42.359 5712c2 [140443028215616] [default] INFO Applicati
<stellar-slack>
5712c2 [140443028215616] [default] INFO * 2015-10-06T18:36:42.359 5712c2 [140443028215616] [default] INFO * The next launch will catchup from the network afresh. 2015-10-06T18:36:42.359 5712c2 [140443028215616] [default] INFO * 2015-10-06T18:36:42.359 5712c2 [140443028215616] [default] INFO Application destructing 2015-10-06T18:36:42.360 5712c2 [140443028215616] [default] INFO Application destroyed
<stellar-slack>
<ericwheeler> it's updating
<stellar-slack>
<graydon> great!
<stellar-slack>
<ericwheeler> when I see stuff like 'Application destroyed' it makes me think maybe that's an issue
<stellar-slack>
<graydon> nope, that's just it exiting
<stellar-slack>
<ericwheeler> got it
<stellar-slack>
<graydon> maybe I should rephrase those messages
<stellar-slack>
<ericwheeler> not a high priority methinks
<stellar-slack>
<ericwheeler> I'm just new to this whole thing
<stellar-slack>
<graydon> :)
<stellar-slack>
<graydon> everyone is at some point!
<stellar-slack>
<graydon> so is it trying to catch up to the network now?
<stellar-slack>
<ericwheeler> indeed
<stellar-slack>
<graydon> should be saying something like
<stellar-slack>
<graydon> 2015-10-06T18:30:40.593 29c2b3 [] [Ledger] INFO Catchup awaiting checkpoint (ETA: 112 seconds), buffering close of ledger 157112 2015-10-06T18:30:43.352 29c2b3 [] [Ledger] INFO Got consensus: [seq=157113, prev=42a490, tx_count=0, sv: [ txH: 329d85, ct: 1444181441, upgrades: [ ]
<stellar-slack>
<ericwheeler> buffering close of ledger
<stellar-slack>
<graydon> so when that ETA thing goes to 0 (more or less, within a little while of it going to zero) it should find a checkpoint and sync up
<stellar-slack>
<graydon> then you'll be digesting live ledger-closes out of the test network
<stellar-slack>
<ericwheeler> closed ledger
<stellar-slack>
<ericwheeler> seq-- hash
<stellar-slack>
<graydon> great! you're in sync then
<stellar-slack>
<ericwheeler> those would be the transactions then
<stellar-slack>
<graydon> those are ledgers closing
<stellar-slack>
<graydon> there aren't any transactions floating around the test network presently
<stellar-slack>
<graydon> you could inject some if you wanted
<stellar-slack>
<ericwheeler> like checks between nodes?
<stellar-slack>
<graydon> ledgers are ... points-in-time that the nodes come to consensus on
<stellar-slack>
<graydon> you can think of the ledgers like batches in a possibly-infinite sequence of transactions
<stellar-slack>
<graydon> the system groups the possible transactions it's working on into bunches once every 5 seconds and then comes to a consensus about the transactions to include in the batch, and applies them / writes them out locally
<stellar-slack>
<buhrmi> when was the last transaction on live net?
<stellar-slack>
<graydon> this is testnet
<stellar-slack>
<buhrmi> i see the last transaction 5 days ago
<stellar-slack>
<ericwheeler> so this is testnet?
<stellar-slack>
<graydon> I'm not sure, I don't have a livenet peer here and I'm just about done for the day (actually finished work officially almost 2h ago)
<stellar-slack>
<graydon> ericwheeler: yeah you connected to testnet, which has no traffic on it except when people are debugging stuff. live net has a little more traffic, though I think basically none yet either since it's very young and no users have upgraded to it yet.
<stellar-slack>
<graydon> so you're just likely to see empty ledgers close, like a clock ticking marking out time but no transactions in each close.
<stellar-slack>
<graydon> (for now!)
<stellar-slack>
<ericwheeler> what would be a good place to start learning
<stellar-slack>
<buhrmi> you're already in the right place :)
<stellar-slack>
<ericwheeler> is running testnet helpful in any way to the network?
<stellar-slack>
<buhrmi> nah
<stellar-slack>
<ericwheeler> is this mostly python based?
<stellar-slack>
<buhrmi> the nodes are in C++, and there are libs for javascript and ruby and python
<stellar-slack>
<buhrmi> i'm not touching python
<stellar-slack>
<graydon> stellar-core is written in C++. horizon (the web-facing API server) is written in Go. clients can be written in various languages.
<stellar-slack>
<graydon> most SDF work on the client side is done in js or ruby
<stellar-slack>
<ericwheeler> seeing that I know exactly zero languages lol where would be a good place to start for Stellar?
<stellar-slack>
<ericwheeler> I like the concept and don't see anything that would inherently be as exclusionary as say bitcoin
<stellar-slack>
<ericwheeler> and Stellar is nice on the energy required front for scalabilty
<stellar-slack>
<graydon> it's a different sort of system to bitcoin. I'm not sure I'd call either of them more or less exclusionary. they have different strengths.
<stellar-slack>
<graydon> I think it depends what you feel like doing, though!
<stellar-slack>
<ericwheeler> from a resource to benefit to the average person who is already excluded from the planet's resources
<stellar-slack>
<eva> imo it’s one quick way to get started playing around with the (test) network - you can even issue your own credits :)
<stellar-slack>
<ericwheeler> thanks @eva
<stellar-slack>
<ericwheeler> I will be looking into it later tonight for sure
<stellar-slack>
<graydon> stellar-core itself is, unfortunately, a bit of a low-level component. and C++ is a pretty tricky language for learning to program. so I doubt it'll be a lot of fun to pick bugs out of it unless you're really in the mood for a challenge. the client-side stuff might be more immediately rewarding, yeah. and/or experimenting with API calls to horizon, if you want. you can, to some extent, interact with all th
<stellar-slack>
<graydon> for example if you want to visit http://localhost:11626/ on your machine while it's talking to testnet
<stellar-slack>
<graydon> you can see some diagnostic commands
<stellar-slack>
<eva> Yeah, I personally think interacting with the client-side is more fun, and it’s vitally important for the ecosystem - the services/apps built on top of Stellar are what will make it great
<stellar-slack>
<ericwheeler> is JSON a file format?
<stellar-slack>
<bartek> ^ response for your transaction
<stellar-slack>
<sacarlson> that decodes to decode_error.rb Stellar::TransactionResultCode.tx_success(0)
<stellar-slack>
<scott> Will be fixing horizon on testnet momentarily. This was the first instance of someone merging an account and then recreating it, which triggered a crash in the history importer
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<sacarlson> merging an account funny I meant to try that and never did
pixelbeat has quit [Ping timeout: 264 seconds]
pixelbeat has joined #stellar-dev
pixelbeat has quit [Ping timeout: 264 seconds]
<stellar-slack>
<jed> starting a stress test of the testnet. let me know if you see anything unusual
pixelbeat has joined #stellar-dev
dobson` has quit [Ping timeout: 240 seconds]
dobson has joined #stellar-dev
pixelbeat has quit [Ping timeout: 240 seconds]
pixelbeat has joined #stellar-dev
``rawr has joined #stellar-dev
<stellar-slack>
<scott> deploying horizon and horizon-importer to testnet… there will be a little hiccup in availability