<stellar-slack>
<lab> with pr #751 ... now i need hot patch #752. exciting.
<stellar-slack>
<lab> @monsieurnicolas, is that feasible for hot patch?
de_henne_ has joined #stellar-dev
de_henne has quit [Ping timeout: 264 seconds]
sv-logger has quit [Remote host closed the connection]
sv-logger has joined #stellar-dev
<stellar-slack>
<sacarlson> @lab forked network on your standalone network or on testnet?
<stellar-slack>
<lab> a network with peers
<stellar-slack>
<sacarlson> how many peers?
<stellar-slack>
<lab> four
<stellar-slack>
<lab> to be least "safe" :)
<stellar-slack>
<sacarlson> so with 3 being bad the forth split?
TheSeven has quit [Disconnected by services]
[7] has joined #stellar-dev
<stellar-slack>
<sacarlson> 66% is the number I think so that would be 75%
<stellar-slack>
<lab> forth will follow if the bad three are same
<stellar-slack>
<sacarlson> ya that's what I was thinking so with IP count you win
<stellar-slack>
<lab> and i keep native asset :)
<stellar-slack>
<lab> stellar-core is awesome. I repaired my engines without halt
<stellar-slack>
<lab> upgraded to pr#752
<stellar-slack>
<sacarlson> halt you mean halt linux system? or you just didn't have to do a full db reset
<stellar-slack>
<lab> system halt or db reset doesn't matter
<stellar-slack>
<lab> i mean the ledger keep advancing without halt while upgrading validators
ultrashag has quit [Ping timeout: 246 seconds]
Kwelstr has quit [Ping timeout: 246 seconds]
Kwelstr has joined #stellar-dev
<stellar-slack>
<sacarlson> oh IC so you can upgrade one at a time and keep all the assets intact on all
<stellar-slack>
<sacarlson> I'm trying to run all my stuf through horizon now so as long as that works I'm good to go
<stellar-slack>
<lab> because four nodes can support 1 failure_safty
Kwelstr has quit [Ping timeout: 246 seconds]
Kwelstr has joined #stellar-dev
ultrashag has joined #stellar-dev
<stellar-slack>
<sacarlson> seems my stellar-core is not coming up today. might they have reset testnet ahead of schedual?
<stellar-slack>
<sacarlson> another brainfart on my side with my present code branch I failed to bring in the updated -core cfg with NETWORK_PASSPHRASE="Test SDF Network ; September 2015" added ha ha
de_henne_ has quit [Ping timeout: 260 seconds]
de_henne has joined #stellar-dev
<stellar-slack>
<buhrmi> the manageoffer tx is still buggy
<stellar-slack>
<buhrmi> Offer Id 7 has been created... with the amount of 0.0000083 YEN (??). Payload used:
<stellar-slack>
<sacarlson> not sure where that number could come from
<stellar-slack>
<sacarlson> oh I guess your price is an int, did you try it as a string?
<stellar-slack>
<buhrmi> it doesnt matter what i do since it's being split into an xdr price with price_n and price_d by the js lib before submission
<stellar-slack>
<sacarlson> is there such a function to allow deleting an already activated stellar account?
<stellar-slack>
<sacarlson> I mean other than reseting all the db of the entire system. I mean on testnet
<stellar-slack>
<dzham> mergeAccounts?
<stellar-slack>
<sacarlson> oh maybe that's what merge accounts does ya
<stellar-slack>
<sacarlson> I've never tried that function
<stellar-slack>
<buhrmi> @jed: testnet already running with the manageoffer fixes? initiating a manageoffer on my node causes it to lose sync
<stellar-slack>
<jed> no it isn't on testnet yet
<stellar-slack>
<buhrmi> ah ok that explains it
<stellar-slack>
<sacarlson> I can't seem to delete a signer from an account on testnet. can someone try add and delete a signer to show me it can be done?
<stellar-slack>
<sacarlson> or maybe the web interface can do this?
<stellar-slack>
<sacarlson> very strange one of the federations I did before has now apeared but I try to change it again and it won't change. tried from firefox and chrome
<stellar-slack>
<sacarlson> oh I just found my stellar-core has lost sync so it's probly on my side
<stellar-slack>
<bartek> @sacarlson: I'm working on fixes in js-stellar-base. you can add your issue to github so I will pick it after finishing current tasks. also, I'm not sure if client tool has been updated on our server - until new network launches, you should use it locally: https://github.com/stellar/stellar-tutorials
<stellar-slack>
<sacarlson> my code is in ruby so I'm not even sure where to post it
<stellar-slack>
<sacarlson> @scott I could provide a small ruby script that just creates and trys to delete a signer if you want. but it should be verifiable by just going to the dev site https://www.stellar.org/developers/tools/client/#/accountmanager and fill in the Set Options section with Address: and Secret: Add signer: Signer Address: Weight (0-255, 0 for delete) set to 1 then change to 0
<stellar-slack>
<scott> I’m actually referring to the issue you created over the weekend
<stellar-slack>
<scott> Regarding signers, I’ve just confirmed it’s a stellar-core bug
<stellar-slack>
<sacarlson> oh ok then you can just close that one and move it
<stellar-slack>
<buhrmi> haha sacarlson ... high five to us for doing free QA work
<stellar-slack>
<scott> will do
<stellar-slack>
<sacarlson> oh sorry scott that was an older issuer 15, I'll provide more details on that one for you
de_henne has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
<stellar-slack>
<sacarlson> @scott it seems even if I pull my older code I can't recreate the problem I saw with issue/15 so my best guess is that I might have been running the older ruby-stellar-base 0.3.0 instead of 0.4.0. maybe that might cause the problem I saw. so I would go ahead and close that one
<stellar-slack>
<scott> :+1: thanks for looking into it
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
de_henne has quit [Remote host closed the connection]
sv-logger has quit [Remote host closed the connection]