<stellar-slack>
<eva> let me know if you have any trouble hearing
sv-logger has quit [Remote host closed the connection]
sv-logger has joined #stellar-dev
<stellar-slack>
<lab> it's clear and fluent, even in china. :)
<stellar-slack>
<lab> we have big problem in connecting outside recently.
<stellar-slack>
<eva> wow, that's really fantastic! Might be worth the cpu it takes up if it's so clear...
<stellar-slack>
<lab> You have been disconnected because of network connectivity issues. We are trying to reconnect you.
<stellar-slack>
<lab> :(
<stellar-slack>
<jes> in
<stellar-slack>
<eva> noooo :(
<stellar-slack>
<eva> is it connecting for you again?
<stellar-slack>
<eva> looks like it's still up...
<stellar-slack>
<dzham> good Q about sequence numbers
<stellar-slack>
<lab> i appreciate the optional source account in operation very much. brilliant designg.
<stellar-slack>
<lab> what's the question?
<stellar-slack>
<dzham> same thing with the fee, only the source account of the tx envelope pays for the transaction. Even if you have multiple source accounts in the operations
<stellar-slack>
<eva> for real, it's really cool
<stellar-slack>
<lab> what's the q about seqn?
<stellar-slack>
<lab> i was disconnect from video... :punch: GFW
<stellar-slack>
<dzham> @lab: as far as I remember it, it was: Do you still have sequence numbers? And Nico explained that they do, but it’s only incremented for the source account in a transaction envelope
<stellar-slack>
<eva> :thumbsup:
<stellar-slack>
<eva> also lab, he answered your question about flags - Nicolas says we do have them
<stellar-slack>
<dzham> freeze flag, right?
<stellar-slack>
<monsieurnicolas> yes
<stellar-slack>
<lab> thanks. the frozen flag is useful for postpay scenario.
<stellar-slack>
<lab> @dzham, it means we need not seqn acturely?
<stellar-slack>
<dzham> @lab: well, you’ll still need to track it for the source account for the transaction
<stellar-slack>
<lab> oh yes. i was thinking about a pure offline wallet
<stellar-slack>
<lab> we cann't turn around the seq query step.
<stellar-slack>
<monsieurnicolas> offline wallet you would have to create a key that you would only use for that wallet but to control a specific account. of course at some point, you need to get online to submit the tx, but you would never get out of sync from a sequence number point of view
<stellar-slack>
<monsieurnicolas> (or txs)
<stellar-slack>
<monsieurnicolas> the worker node example is kinda dealing with a similar problem, where the sequence number is managed locally by the worker node
<stellar-slack>
<lab> if same secure key deploy in different offline computers..
<stellar-slack>
<monsieurnicolas> yeah don't do that :)
<stellar-slack>
<monsieurnicolas> it's very cheap to add signers to accounts
de_henne_ has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
[7] has quit [Remote host closed the connection]
TheSeven has joined #stellar-dev
<stellar-slack>
<sacarlson> well I'm going to have to regress back to an older version of stellar-core to proceed to debug my multi-sign-server. as there seems to be a bug in ruby-stellar-base I guess due to problems asset amount changes in last upgrade
<stellar-slack>
<sacarlson> the same problem is also seen in buhrmi's open-core that also has those changes incorportated
<stellar-slack>
<buhrmi> which problem exactly
<stellar-slack>
<buhrmi> which changes
<stellar-slack>
<sacarlson> the details should be seen above but I'll capture them and put them in a google drive with all the files and details
<stellar-slack>
<sacarlson> there are two problems on the stellar-core stoped syncing the other before that was an error in int value: /home/sacarlson/.bundle/gems/xdr-0.1.0/lib/xdr/hyper.rb:6:in `write': val is not Integer (XDR::WriteError) from /home/sacarlson/.bundle/gems/xdr-0.1.0/lib/xdr/struct.rb:31:in `block in write'
<stellar-slack>
<sacarlson> the xdr problem is also seen on open-core
<stellar-slack>
<buhrmi> i don't know what you're trying to do that produces the xdr error
<stellar-slack>
<sacarlson> this was seen from createing an account
<stellar-slack>
<buhrmi> what line of code produces that error
<stellar-slack>
<sacarlson> more details can be seen back at 9:52 yestarday here on slack
<stellar-slack>
<sacarlson> that tx=
<stellar-slack>
<buhrmi> looks like you're passing a keypair into destination instead of an address...
<stellar-slack>
<sacarlson> this always wanted keypairs, I convert from one or the other in this to suit that fuction
<stellar-slack>
<buhrmi> what if you remove the starting balance option
<stellar-slack>
<sacarlson> it is set to zero when we run it from your network
<stellar-slack>
<sacarlson> but you must provide that on stellar
<stellar-slack>
<sacarlson> the fee: is optional and is defaulted on stellar to 10
<stellar-slack>
<sacarlson> 25 is default if no starting balance is added to the function call
<stellar-slack>
<buhrmi> i've added the "new trustline" popup
<stellar-slack>
<dzham> +1 on the BAD_AUTH thing, btw. js-stellar-sdk, latest version.
<stellar-slack>
<dzham> ok. have to set network. bad API
<stellar-slack>
<dzham> yo! Network isn’t exposed in js-stellar-sdk
<stellar-slack>
<dzham> oh god… "npm install stellar-sdk —dev” has downloaded 800Mb of crap so far, and isn’t finished yet
<stellar-slack>
<dzham> all so I can expose Network, and ‘gulp build'
<stellar-slack>
<dzham> 1,12 GB
<stellar-slack>
<dzham> This is just insane. And some people actually think npm is good.
<stellar-slack>
<buhrmi> i think it's good :P
<stellar-slack>
<buhrmi> if you're careful what u depend on it's cool
<stellar-slack>
<buhrmi> over 1 GB of dependencies is weird
<stellar-slack>
<dzham> it’s shitty
<stellar-slack>
<dzham> ```There are two ways to install npm packages: locally or globally. You choose which kind of installation to use based on how you want to use the package. If you want to depend on the package from your own module using something like Node's require, then you want to install locally. On the other hand, if you want to use it as a command line tool, something like the grunt CLI, then you want to install it glob
<stellar-slack>
<dzham> why do I want to install everything locally? Isn’t that *my* decision?
<stellar-slack>
<dzham> it’s retarded
<stellar-slack>
<buhrmi> mhh i think it's just a weirdly phrased suggestion
<stellar-slack>
<buhrmi> "you want to..." ...
<stellar-slack>
<dzham> is it a suggesiton if everyone does it that way? I mean, try using angularjs with yeoman, without downloading 120+ MB of crap everytime you start a new project. It’s the same bloody files.
<stellar-slack>
<buhrmi> haha i'm not using these tools ...
<stellar-slack>
<buhrmi> yeoman, bower, gulp, ...
<stellar-slack>
<dzham> Doens’t even work if you put the modules globally. Unless you symlink the node_modules directory
<stellar-slack>
<dzham> Sorry for the ranting, but I just wanted fix a bug, but the toolchain got in the way
<stellar-slack>
<dzham> Anyways.. stellar-sdk doesn’t expose the Network object, so it’s impossible to set the network.
<stellar-slack>
<buhrmi> dont u set it thru stellar base?
<stellar-slack>
<dzham> Yep, but I can’t get to stellar base. I can npm install that separately, but thank to npm, it’s a completely separate stellar base that gets called, and not the one that stellar-sdk is using
<stellar-slack>
<buhrmi> BUAHAHA
<stellar-slack>
<buhrmi> sorry
_whitelogger has joined #stellar-dev
<stellar-slack>
<eno> ,:(
<stellar-slack>
<buhrmi> when i send the js library to send an order, the "amount" always is saved as 1 ... is that a known bug?
pixelbeat has joined #stellar-dev
<stellar-slack>
<sacarlson> seems I found that my error is not related to the stellar-core version as regressed back to older stellar-core still gives me this same error
<stellar-slack>
<sacarlson> and this is after I reloaded all my gem to pristine so I'm not sure were my problem even starts
moo-_- has quit [Ping timeout: 244 seconds]
<stellar-slack>
<buhrmi> lol so i say offer amount: 50000000 in the tx but the database stores "197" O_o
<stellar-slack>
<sacarlson> close enuf?
<stellar-slack>
<buhrmi> looks like stellar core is limiting the amount i can offer but i dont know by what
<stellar-slack>
<sacarlson> 64 bit interger?
<stellar-slack>
<sacarlson> 32bit is like 4Billion
<stellar-slack>
<sacarlson> slide 7 dec less than that maybe
<stellar-slack>
<sacarlson> the value that the error is erroring on is 25.0 that is suposed to be an integer
<stellar-slack>
<sacarlson> I'm not sure where this value came from but I could force it back into intiger state
<stellar-slack>
<buhrmi> is offer amount and price also supposed to be sent in 10-million?
<stellar-slack>
<buhrmi> lol
<stellar-slack>
<sacarlson> yes all amounts
<stellar-slack>
<buhrmi> weird .... i'm trying to make sense of their algorythm that uses sheeps and wheat ...
<stellar-slack>
<fredolafritte> That's why using a fixed 7 decimal place for all assets is a terrible design flaw
<stellar-slack>
<buhrmi> i'm close to making a call that the "offer engine" (or whatever to call it) is buggy
<stellar-slack>
<buhrmi> *checks testcases*
<stellar-slack>
<buhrmi> can't locate the testcases for it :(
<stellar-slack>
<sacarlson> I seem to have found my problem, it is due to the starting balance of an account can't be a floating number it must be an integer and I had forced default value as 25.0 that was considered a float
<stellar-slack>
<sacarlson> so even in the new version of stellar you can't start any accounts with fractions of lumens
<stellar-slack>
<sacarlson> so my workaround in my stellar_utilities I now force starting_balance.to_i so it can't happen again
<stellar-slack>
<sacarlson> seems to send anything but float so maybe we will see the problem again
<stellar-slack>
<sacarlson> another strange this is now today the new stellar-core is LM_SYNCED_STATE again
<stellar-slack>
<sacarlson> I did nothing to it just didn't run it for 10 hours or so
<stellar-slack>
<bartek> @dzham: stellar-sdk@0.2.1 is now exposing `Network`
<stellar-slack>
<bartek> to use testnet: `StellarSdk.Network.useTestnet();`
<stellar-slack>
<buhrmi> when i make a manageoffer tx for an existing offer to update price and amount, the amount gets updated (sometimes) but the price stays the same ...
<stellar-slack>
<buhrmi> also the amount seems to have a maximum value depending on the price but i can't figure out how it is derived at all
<stellar-slack>
<buhrmi> i don't know, but it kinda "feels buggy"
<stellar-slack>
<sacarlson> it's a feature ha ha
<stellar-slack>
<sacarlson> the buggy feeling feature that stellar is blessed with
<stellar-slack>
<buhrmi> but it's okay it's a not-for-profit!
<stellar-slack>
<buhrmi> scnr :P
<stellar-slack>
<sacarlson> a nice new error today: Stellar::TransactionResultCode.tx_no_account(-8)
<stellar-slack>
<sacarlson> seems my account disapeared since yestarday GCEZWKCA5VLDNRLN3RPRJMRZOX3Z6G5CHCGSNFHEYVXM3XOJMDS674JZ
<stellar-slack>
<sacarlson> they must have reset again?
<stellar-slack>
<sacarlson> maybe that's why my system is working again also
<stellar-slack>
<sacarlson> opps it's me I'm using the old master seed
<stellar-slack>
<sacarlson> everything is still in integer in ruby-stellar-base not float as I had originaly expected
<stellar-slack>
<sacarlson> or at least native is
<stellar-slack>
<sacarlson> first transaction on the this stellar-core that worked
<stellar-slack>
<jed> fredolafritte: "That's why using a fixed 7 decimal place for all assets is a terrible design flaw" why is that?
<stellar-slack>
<jed> buhrmi: the offer tests are in src/transactions/OfferTests.cpp
<stellar-slack>
<jed> If you can repro manage offer not working please make an issue
<stellar-slack>
<buhrmi> is it expected that amount is a string but price is an int?
<stellar-slack>
<buhrmi> i don't wanna make a ticket if it's user error .... because it's actually really basic stuff that doesn't work so i might come out stupid at the end lol
<stellar-slack>
<buhrmi> it's two issues... the simpler one being that when submitting a manageOffer tx with an ID and a changed price, the price does not update in the ledger DB
<stellar-slack>
<buhrmi> i can repro it easily, but i might be doing something wrong
<stellar-slack>
<bartek> can you share your code?
<stellar-slack>
<buhrmi> sec
<stellar-slack>
<bartek> and you address? are you submitting it to stellar-core or your fork?
<stellar-slack>
<buhrmi> it's my fork. gonna try to repro it on testnet
<stellar-slack>
<buhrmi> aaahhh... bad auth... bad auth...
<stellar-slack>
<buhrmi> can anyone confirm that updating offer price of an existing offer through manageOffer tx is working on testnet?
<stellar-slack>
<monsieurnicolas> re: amount in offers, it's actually computed based on what you can sell and how much you can get. What you can sell is: for non native it's the balance ; for lumens it's what you have above the reserve. What you can buy: non native it's (limit-balance) ; native has no restriction.
<stellar-slack>
<buhrmi> re "what you can sell": I'm offering an asset that i issue myself
<stellar-slack>
<monsieurnicolas> then you're only limited by you can buy
<stellar-slack>
<monsieurnicolas> by what you can buy if it's not native
<stellar-slack>
<buhrmi> mmhh that doesnt seem to work accurately
<stellar-slack>
<buhrmi> i'm currently setting up my app to run on testnet... will try there in a bit