<stellar-slack>
<buhrmi> Unfortunately the domain name http://core.jp|core.jp is not available to register. Occasionally our registration system does not correctly detect if a domain name already exists. In some circumstances, the domain name may appear on a non-published reserved/banned list, and for this reason, it may appear that the domain name is technically available to register.
<stellar-slack>
<buhrmi> f**k x)
<stellar-slack>
<buhrmi> need new domain!
<stellar-slack>
<buhrmi> mhhh so what would be the easiest way to externalize changes on the stellar network in real-time to a nodejs process?
<stellar-slack>
<buhrmi> triggers on the postgres db?
sv-logger has quit [Remote host closed the connection]
sv-logger has joined #stellar-dev
<stellar-slack>
<sacarlson> well I use sqlite but if you setup with postgres that should work
<stellar-slack>
<sacarlson> my local steller-core still shows as "state" : "Synced!" so that sounds good
<stellar-slack>
<buhrmi> is that you? 171.97.138.209 ^^
<stellar-slack>
<sacarlson> yup that checks out 171.97.138.209
<stellar-slack>
<sacarlson> oh you see me as a node?
<stellar-slack>
<buhrmi> yeah
<stellar-slack>
<sacarlson> ok how do I setup postgresql with rake? as this psql postgres -c "\l" shows it's working with no password
<stellar-slack>
<sacarlson> some step I must have missed here
<stellar-slack>
<sacarlson> this is to install horizon on my local system
<stellar-slack>
<sacarlson> Couldn't create database for {"adapter"=>"postgresql", "database"=>"horizon_development", "host"=>"localhost"}
<stellar-slack>
<buhrmi> @matschaffer: so you'll be in at the meetup today? :)
<stellar-slack>
<buhrmi> @sacarlson: seeing horizon is just a rails app, did you try rake db:create ?
<stellar-slack>
<sacarlson> even after changing my postgresql password and editing config/database.yml file with my username and password still get that error
<stellar-slack>
<sacarlson> yes that's what that error comes from above
<stellar-slack>
<sacarlson> so it's some rake setup problem I have I guess
<stellar-slack>
<buhrmi> rake db:create --verbose
<stellar-slack>
<sacarlson> it already spits out alot
<stellar-slack>
<buhrmi> i don't think there is a problem with rake
<stellar-slack>
<buhrmi> what happens when you attempt to start the server
<stellar-slack>
<sacarlson> says no password but I set it in that config file
<stellar-slack>
<buhrmi> post your config file
<stellar-slack>
<matschaffer> @buhrmi: nah, I'm headed to Takayama tomorrow & Nagoya friday so gonna hunker down and get some work done today
<stellar-slack>
<buhrmi> @sacarlson: that's a weird config file. is that in the horizon repo?
<stellar-slack>
<sacarlson> yes it's the same repo now running on horizon per matschaffer
<stellar-slack>
<buhrmi> try this config
TheSeven has quit [Disconnected by services]
[7] has joined #stellar-dev
de_henne has joined #stellar-dev
Kwelstr has quit [Ping timeout: 244 seconds]
stellar-slack has quit [Remote host closed the connection]
Kwelstr has joined #stellar-dev
stellar-slack has joined #stellar-dev
<stellar-slack>
<buhrmi> gonna compile again, maybe they updated the nodes
<stellar-slack>
<matschaffer> looks like b179493
<stellar-slack>
<matschaffer> master is af2e1db so might want to see if b179493 works better. I haven't seen any alerts about testnet losing sync with itself
<stellar-slack>
<matschaffer> so in theory b179493 should be able to hold sync, granted there could be some cross-internet thing at play here too
<stellar-slack>
<matschaffer> not really - that's a massive commit
<stellar-slack>
<buhrmi> k, synced again ... seems like a db reset did the job
<stellar-slack>
<buhrmi> ha ... found the reason
<stellar-slack>
<buhrmi> having a trigger function on the ledgerheader table causes stellar-core to go out of sync and "reboot" when trying to close the ledger
<stellar-slack>
<buhrmi> don't know why, tho
<stellar-slack>
<matschaffer> interesting
<stellar-slack>
<matschaffer> what's the function doing? stellar-core expects to have pretty fast access to the database
<stellar-slack>
<matschaffer> in production psql is on the same instance and (I believe) connected via unix socket
<stellar-slack>
<matschaffer> at least I'm pretty sure the delivery pipeline does it that way. Not sure about testnet
<stellar-slack>
<buhrmi> it notifies connected clients who listen for trigger ... yeah i think this might introduce a lot of delay
<stellar-slack>
<matschaffer> that'd probably do it
<stellar-slack>
<matschaffer> I think that's sort of what gave rise to go-horizon btw
<stellar-slack>
<matschaffer> since golang made it easier than ruby to stream events out
<stellar-slack>
<sacarlson> after I fill in some of the values in the .rbenv-vars file I now see this
<stellar-slack>
<sacarlson> so is this the error NoMethodError: undefined method `tr' for nil:NilClass
gst has quit [Quit: leaving]
<stellar-slack>
<sacarlson> ?
<stellar-slack>
<buhrmi> i dunno, maybe try a new database.yml file
<stellar-slack>
<sacarlson> I tried many
<stellar-slack>
<sacarlson> I'm more used to mysql and sqlite never used postgresqrl stuf before
<stellar-slack>
<sacarlson> I guess what I have to do is create a new test app that sets up a simple rake db and see if that works first
<stellar-slack>
<sacarlson> at least then I will better understand how it operates
<stellar-slack>
<sacarlson> oh I forgot to ask the #rake guys also
<stellar-slack>
<buhrmi> live updates via Meteor DDP :)
<stellar-slack>
<sacarlson> all I can tell you is that it works
<stellar-slack>
<buhrmi> only thing that currently updates tho are the ledger close times
<stellar-slack>
<buhrmi> with websockets ^^
<stellar-slack>
<sacarlson> I don't even know what a websocket is but...
<stellar-slack>
<sacarlson> I would just set the header to update every 2 secounds
gst has joined #stellar-dev
gst has joined #stellar-dev
<stellar-slack>
<buhrmi> i'm not in control of that :S
<stellar-slack>
<buhrmi> the SCP is..
<stellar-slack>
<sacarlson> so that's what was making your stellar-core crash ?
<stellar-slack>
<buhrmi> i had a faulty trigger on a postgres table
<stellar-slack>
<sacarlson> and this triger sends events to js?
<stellar-slack>
<buhrmi> so what i did was
<stellar-slack>
<buhrmi> 1. add a trigger to the ledgerheaders table that notifies a channel when there are update, 2. listen to that channel with nodejs, 3. when there are changes, send the changes via DDP to clients viewing http://open-core.meteor.com
<stellar-slack>
<buhrmi> now it works
<stellar-slack>
<sacarlson> cool so what can we use that for?
<stellar-slack>
<buhrmi> wanna continue to work on it tomorrow
<stellar-slack>
<sacarlson> I guess if looking at the correct table you could see changes in a price of an asset in more real time
<stellar-slack>
<sacarlson> would that also work on sqlite these events?
<stellar-slack>
<buhrmi> no
<stellar-slack>
<sacarlson> on mysql?
<stellar-slack>
<buhrmi> i don't know :P
<stellar-slack>
<sacarlson> well bummer it don't work on sqlite as now I have to poll the database for changes and I only do that every 2 sec
<stellar-slack>
<sacarlson> near real time for me but better if event driven
<stellar-slack>
<buhrmi> yeah if u use postgres u can do event driven
<stellar-slack>
<sacarlson> well that's good to know, when the time comes I may put that to use
<stellar-slack>
<buhrmi> so back to the question: "what can we use it for"
<stellar-slack>
<buhrmi> for example
<stellar-slack>
<sacarlson> I already gave you an example
<stellar-slack>
<buhrmi> your pokerchip transactions could show up on that site
<stellar-slack>
<buhrmi> filter by "10 recent pokerchips"
<stellar-slack>
<sacarlson> not sure we need that in realtime but a market moves in realtime so price changes is what it would be best for in trading
<stellar-slack>
<sacarlson> I'm still trying to think of a multi sign contract method for poker
<stellar-slack>
<sacarlson> it starts with 10 people in a game so a contract with even wait for each signs an account with the pot
<stellar-slack>
<buhrmi> this is awesome
<stellar-slack>
<sacarlson> when someone drops out from loss of all his chips then a new contract is auto created with the nine left in the game that create a new contract and send the funds that they now control to the new account
<stellar-slack>
<sacarlson> the problem is when you get down to the last 2 people in the game
<stellar-slack>
<buhrmi> yeah i don't know much about poker
<stellar-slack>
<sacarlson> it not poke it a contract thing
<stellar-slack>
<sacarlson> like stock holders in a corporation have votes to control events in the corporation
<stellar-slack>
<sacarlson> you have more wait if you hold more assets in the corporation
<stellar-slack>
<sacarlson> if a majority don't like someone on the board they can vote him out
<stellar-slack>
<sacarlson> that's how the multi sign contracts also work
<stellar-slack>
<sacarlson> but I'm a bit stuck when there are only 2 people left in the game or left on the board
<stellar-slack>
<sacarlson> maybe when down to the last 2 people in the game the last 3rd person that was last to loose becomes the third party that acts as the witness
<stellar-slack>
<sacarlson> only 1 transaction is shown
<stellar-slack>
<buhrmi> yeah it only shows the transactions that my node has seen since db reset
<stellar-slack>
<sacarlson> but I guess that's all your core has seen from start?
<stellar-slack>
<sacarlson> ok
<stellar-slack>
<buhrmi> gonna send u another tx
<stellar-slack>
<buhrmi> lets see
<stellar-slack>
<sacarlson> hay wonder if it will also see my errors from attempted transactions?
<stellar-slack>
<sacarlson> ok
<stellar-slack>
<sacarlson> I don't think the database shows failed transactions, I think only seen maybe in the logs
<stellar-slack>
<sacarlson> hay I can see me Address: 171.97.138.209:11625
<stellar-slack>
<sacarlson> I only show 6 peers on my core
<stellar-slack>
<dzham> @buhrmi: coolio!
<stellar-slack>
<sacarlson> so who's the gateway for the sausages and BEER
<stellar-slack>
<sacarlson> then you can start looking at trading
<stellar-slack>
<sacarlson> yes I read that fredolafritte but stuck at this point rake db:create && RAILS_ENV=test rake db:create
<stellar-slack>
<sacarlson> I filled in those values in .rbenv-var
<stellar-slack>
<sacarlson> oh but not like that I didn't cool
<stellar-slack>
<fredolafritte> try to add them in *.bashrc*
<stellar-slack>
<sacarlson> ya I could have them set in a script maybe
<stellar-slack>
<sacarlson> but it looks like the values are passed from .rbenv-var I think I just didn't know what to put in the values
<stellar-slack>
<sacarlson> I checked and I do have postgres server 9.3 installed
<stellar-slack>
<sacarlson> so I need 9.4
<stellar-slack>
<sacarlson> with your added values I now get: URI::InvalidURIError: bad URI(is not URI?): "postgres://sacarlson:scottc@localhost:5432/horizon?sslmode=disable"
<stellar-slack>
<sacarlson> so I guess I'll see what's needed to upgrade to 9.4
<stellar-slack>
<fredolafritte> it's not related to 9.3 or 9.4
<stellar-slack>
<sacarlson> something else I did?
<stellar-slack>
<fredolafritte> horizon gives you this error ?
<stellar-slack>
<sacarlson> I get it from this rake db:create
<stellar-slack>
<sacarlson> maybe on the command line that's incomplete? should be rake db:create && rake db:migrate
<stellar-slack>
<sacarlson> ?
<stellar-slack>
<sacarlson> this from the root of horizon with all setup as told to do in developing.md
<stellar-slack>
<fredolafritte> have you tried *./bin/setup* ?
<stellar-slack>
<sacarlson> yes
<stellar-slack>
<sacarlson> I'm running the present commit that is now running on stellar
<stellar-slack>
<sacarlson> maybe just a bad install
<stellar-slack>
<fredolafritte> can you try with *export DATABASE_URL="postgres://postgres:password@localhost:5432/horizon?sslmode=disable"*
<stellar-slack>
<fredolafritte> ?
<stellar-slack>
<sacarlson> sure I can try but I assume I would have to rename .rbenv-var that assume would superceed it
<stellar-slack>
<sacarlson> ok I renamed .rbenv-var and ran again without your export to see what it would do now I see this
<stellar-slack>
<sacarlson> so this must be good!! no?
<stellar-slack>
<sacarlson> so went ahead and ran ./bin/setup and it looks like it might have ran ok
<stellar-slack>
<sacarlson> so I wrote a source_me.sh that I would assume I would have to source ./source_me.sh ; every time I ran horizon
<stellar-slack>
<sacarlson> that has your exports above in it
<stellar-slack>
<fredolafritte> I did the same
<stellar-slack>
<sacarlson> cool you are again the man
<stellar-slack>
<fredolafritte> you're ready for the next hurdle
<stellar-slack>
<fredolafritte> :)
<stellar-slack>
<sacarlson> ya more errors to come I'm sure ha ha
<stellar-slack>
<fredolafritte> it's part of the game
<stellar-slack>
<sacarlson> yup
<stellar-slack>
<fredolafritte> bear in mind you would also need go-horizon ...
<stellar-slack>
<sacarlson> can't I run without go-horizon?
<stellar-slack>
<fredolafritte> some of the functionalities are in horizon, some others in go-horizon
<stellar-slack>
<fredolafritte> go-horizon will forward its unimplemented requests to horizon
<stellar-slack>
<fredolafritte> still wondering why they rewrite ruby-horizon in go-horizon ...
<stellar-slack>
<sacarlson> it's also not passing bundle exec rspec lots of errors one being StandardError: An error has occurred, this and all later migrations canceled: PG::UndefinedFile: ERROR: could not open extension control file "/usr/share/postgresql/9.3/extension/hstore.control": No such file or directory : CREATE EXTENSION IF NOT EXISTS "hstore"/home/sacarlson/.bundle/gems/activerecord-4.2.1/lib/active_record/connection_ada
<stellar-slack>
`async_exec'
<stellar-slack>
<sacarlson> might be easier to write my own horizon. it seems it does almost nothing anyway
<stellar-slack>
<fredolafritte> that's the 9.3/9.4 version postgres issue
<stellar-slack>
<fredolafritte> beware to remove first the 9.3
<stellar-slack>
<sacarlson> ok thanks I'll try upgrade it then
sacarlson has quit [Ping timeout: 244 seconds]
sacarlson has joined #stellar-dev
DomKM has quit [Quit: Connection closed for inactivity]
de_henne has quit [Remote host closed the connection]
de_henne has quit [Remote host closed the connection]
<stellar-slack>
<buhrmi> is it just me or is the number of participating testnet nodes suddenly increasing a lot?
<stellar-slack>
<buhrmi> To the moooon
sacarlson has quit [Ping timeout: 244 seconds]
sacarlson has joined #stellar-dev
<stellar-slack>
<mason> @scott gave what feedback I could :). I've been working on getting go-horizon running. Hopefully I will be able to be helpful soon :bowtie:
<stellar-slack>
<scott> @mason: I just saw that. Thanks!
<stellar-slack>
<scott> If you’ve got any questions along the way, please feel free to ask; Things are still definitely rough around the corners.
<stellar-slack>
<mason> Cool will do!
<stellar-slack>
<eva> @mason: would love to hear more about what you're working on :)
Vinnie_win has quit [Ping timeout: 240 seconds]
Vinnie_win has joined #stellar-dev
<stellar-slack>
<mason> Just interested in helping wherever I can
anon2 has joined #stellar-dev
anon2 has quit [Client Quit]
<stellar-slack>
<mason> I’ll probably look through the issue tracker on go-horizon once I get it up and running. Let me know if something else would be more valuable!
<stellar-slack>
<mason> I should probably get back to work now though haha :S
<stellar-slack>
<scott> :) cheers
<stellar-slack>
<eva> awesome, that's so great to hear @mason! We could certainly use the help
<stellar-slack>
<eva> have a great day at work :)
<stellar-slack>
<mason> thanks! Yeah looking forward to it!