Pages:
Author

Topic: The collective Mastercoin-explorer, Mastercoin-ruby and Mastercoin-wallet topic - page 3. (Read 19601 times)

hero member
Activity: 938
Merit: 1000
Here you go:

Code:
/var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/builder.rb:114:in `pick_outputs': undefined method `reject!' for nil:NilClass (NoMethodError)
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/builder.rb:151:in `create_transaction_with_keys'
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/simple_send_window.rb:59:in `send_payment'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `qt_metacall'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `method_missing'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `exec'
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:98:in `new_simple_send'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `qt_metacall'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `method_missing'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `exec'
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/bin/mastercoin-wallet:12:in `'
    from /usr/local/bin/mastercoin-wallet:23:in `load'
    from /usr/local/bin/mastercoin-wallet:23:in `
'
/usr/local/bin/mastercoin-wallet: [BUG] Segmentation fault
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]

-- Control frame information -----------------------------------------------
c:0001 p:0000 s:0002 b:0002 l:001f88 d:001f88 TOP   


-- C level backtrace information -------------------------------------------
/usr/lib/libruby-1.9.1.so.1.9(+0x155d99) [0x7f73a278ed99]
/usr/lib/libruby-1.9.1.so.1.9(+0x57d39) [0x7f73a2690d39]
/usr/lib/libruby-1.9.1.so.1.9(rb_bug+0xb3) [0x7f73a2691523]
/usr/lib/libruby-1.9.1.so.1.9(+0xf68ff) [0x7f73a272f8ff]
/lib/x86_64-linux-gnu/libc.so.6(+0x370b0) [0x7f73a22a70b0]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4exitEi+0x1e) [0x7f73a068846e]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QDialog10setVisibleEb+0x166) [0x7f739fee9cc6]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QDialogD1Ev+0x30) [0x7f739fee9e90]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/smoke/qtgui/libsmokeqtgui.so.3(_ZN12__smokeqtgui9x_QDialogD1Ev+0x65) [0x7f739e9957f3]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/smoke/qtgui/libsmokeqtgui.so.3(_ZN12__smokeqtgui9x_QDialogD0Ev+0x18) [0x7f739e995850]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/smoke/qtgui/libsmokeqtgui.so.3(_ZN12__smokeqtgui13xcall_QDialogEsPvPN5Smoke9StackItemE+0x423) [0x7f739e982ee2]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/ruby/qtruby/src/libqtruby4shared.so.2(_Z14smokeruby_freePv+0xa16) [0x7f739d09fac0]
/usr/lib/libruby-1.9.1.so.1.9(+0x6aa0a) [0x7f73a26a3a0a]
/usr/lib/libruby-1.9.1.so.1.9(rb_gc_call_finalizer_at_exit+0x1df) [0x7f73a26a7b3f]
/usr/lib/libruby-1.9.1.so.1.9(ruby_cleanup+0x1e9) [0x7f73a26969d9]
/usr/lib/libruby-1.9.1.so.1.9(ruby_run_node+0x25) [0x7f73a2696bb5]
/usr/bin/ruby1.9.1() [0x40086b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f73a2291ea5]
/usr/bin/ruby1.9.1() [0x400899]

Do you have any outputs large enough to pay for this transaction?
full member
Activity: 201
Merit: 100
Here you go:

Code:
/var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/builder.rb:114:in `pick_outputs': undefined method `reject!' for nil:NilClass (NoMethodError)
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/builder.rb:151:in `create_transaction_with_keys'
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/simple_send_window.rb:59:in `send_payment'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `qt_metacall'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `method_missing'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `exec'
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:98:in `new_simple_send'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `qt_metacall'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `method_missing'
    from /var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/lib/Qt/qtruby4.rb:880:in `exec'
    from /var/lib/gems/1.9.1/gems/mastercoin-wallet-0.0.11/bin/mastercoin-wallet:12:in `'
    from /usr/local/bin/mastercoin-wallet:23:in `load'
    from /usr/local/bin/mastercoin-wallet:23:in `
'
/usr/local/bin/mastercoin-wallet: [BUG] Segmentation fault
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]

-- Control frame information -----------------------------------------------
c:0001 p:0000 s:0002 b:0002 l:001f88 d:001f88 TOP   


-- C level backtrace information -------------------------------------------
/usr/lib/libruby-1.9.1.so.1.9(+0x155d99) [0x7f73a278ed99]
/usr/lib/libruby-1.9.1.so.1.9(+0x57d39) [0x7f73a2690d39]
/usr/lib/libruby-1.9.1.so.1.9(rb_bug+0xb3) [0x7f73a2691523]
/usr/lib/libruby-1.9.1.so.1.9(+0xf68ff) [0x7f73a272f8ff]
/lib/x86_64-linux-gnu/libc.so.6(+0x370b0) [0x7f73a22a70b0]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4exitEi+0x1e) [0x7f73a068846e]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QDialog10setVisibleEb+0x166) [0x7f739fee9cc6]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QDialogD1Ev+0x30) [0x7f739fee9e90]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/smoke/qtgui/libsmokeqtgui.so.3(_ZN12__smokeqtgui9x_QDialogD1Ev+0x65) [0x7f739e9957f3]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/smoke/qtgui/libsmokeqtgui.so.3(_ZN12__smokeqtgui9x_QDialogD0Ev+0x18) [0x7f739e995850]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/smoke/qtgui/libsmokeqtgui.so.3(_ZN12__smokeqtgui13xcall_QDialogEsPvPN5Smoke9StackItemE+0x423) [0x7f739e982ee2]
/var/lib/gems/1.9.1/gems/qtbindings-4.8.3.0/ext/build/ruby/qtruby/src/libqtruby4shared.so.2(_Z14smokeruby_freePv+0xa16) [0x7f739d09fac0]
/usr/lib/libruby-1.9.1.so.1.9(+0x6aa0a) [0x7f73a26a3a0a]
/usr/lib/libruby-1.9.1.so.1.9(rb_gc_call_finalizer_at_exit+0x1df) [0x7f73a26a7b3f]
/usr/lib/libruby-1.9.1.so.1.9(ruby_cleanup+0x1e9) [0x7f73a26969d9]
/usr/lib/libruby-1.9.1.so.1.9(ruby_run_node+0x25) [0x7f73a2696bb5]
/usr/bin/ruby1.9.1() [0x40086b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f73a2291ea5]
/usr/bin/ruby1.9.1() [0x400899]
hero member
Activity: 938
Merit: 1000
Oh no sorry just give me the whole error you see in the console. Usually the top part is the actual error, the rest is just QT crashing. Just pastie it somewhere and pm or link it here Smiley
full member
Activity: 201
Merit: 100
Could you give me the full traceback?
Perhaps if I wasn't an idiot...

let's see...easiest way to do that would be with gdb? Trying to do that but not having luck.  Is there something built into ruby I should use to capture that? or is it automatically going to a log?
hero member
Activity: 938
Merit: 1000
Could you give me the full traceback?
full member
Activity: 201
Merit: 100
Hey Tachikoma - updated my ubuntu box with v0.0.11 (previously ran v0.0.7 without issue).  When I attempt a simple send, it crashes with a core dump and references a possible issue with the ruby interpreter or extension libraries.  Any thoughts?

Edit: Also unrelated but thought I'd mention - the BTC balances in both my OS X wallet and Ubuntu wallets linked to 2 different BTC addresses is not accurate - is there a reason for the discrepancy?
hero member
Activity: 938
Merit: 1000
Would you be willing to pm me your address? It's seems to be related to your transactions.
newbie
Activity: 46
Merit: 0
Hi,

it seems something is broken with mastercoin-wallet-0.0.11. I am not able to get it working. I used mastercoin-wallet since version 0.0.7. I tried to update 0.0.10 to 0.0.11 with "gem install mastercoin-wallet". Now I get the following error when trying to start :

-----------------------------------------------------------
chris@ubuntu:~$ mastercoin-wallet
/home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:144:in `add_purchase_row': undefined method `[]' for nil:NilClass (NoMethodError)
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:164:in `block in load_transactions'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:163:in `each'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:163:in `load_transactions'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:112:in `update'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/lib/mastercoin-wallet/gui/main_window.rb:75:in `initialize'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/bin/mastercoin-wallet:10:in `new'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/gems/mastercoin-wallet-0.0.11/bin/mastercoin-wallet:10:in `'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/bin/mastercoin-wallet:19:in `load'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/bin/mastercoin-wallet:19:in `
'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in `eval'
   from /home/chris/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in `
'
-----------------------------------------------------------


Any ideas?
hero member
Activity: 938
Merit: 1000
No problem. If there is anything else please let me know. I'm working so much on the internals of everything that I become blind for the externals. Smiley
hero member
Activity: 700
Merit: 500
Just a small suggestion: the "Send transactions" section for an address currently shows the source address for each transaction. To me it would make much more sense to show the destination address instead.

Annotated screenshot: https://i.imgur.com/BGq4vtL.png
This should now be the default for addresses pages, please let me know if this works for you.

Works perfect – thanks for the quick implementation!
hero member
Activity: 938
Merit: 1000
Just a small suggestion: the "Send transactions" section for an address currently shows the source address for each transaction. To me it would make much more sense to show the destination address instead.

Annotated screenshot: https://i.imgur.com/BGq4vtL.png


This should now be the default for addresses pages, please let me know if this works for you.

Just a small suggestion: the "Send transactions" section for an address currently shows the source address for each transaction. To me it would make much more sense to show the destination address instead.

Annotated screenshot: https://i.imgur.com/BGq4vtL.png


Yeah, I agree. And possibly show them both on that main page itself (maybe not the address page), and truncate, using tooltips on hover. ...I find myself pulling up a bunch of tabs for each transaction just to look at the destination addresses...the transaction ID (currently truncated) could be a tooltip as well.

Easy with twitter bootstrap (good choice Smiley).

http://getbootstrap.com/javascript/#tooltips

I thought it had a css-only way to do this as well...but I guess that might have been taken out in v3....

Yeah I originally had that on the main page but because not all messages had recipient addresses I changed it. I brought it back now by condensing the table and replacing the tx id with an icon to make space. Let me know what you think. Your tooltip idea is in there Smiley
sr. member
Activity: 462
Merit: 250
Just a small suggestion: the "Send transactions" section for an address currently shows the source address for each transaction. To me it would make much more sense to show the destination address instead.

Annotated screenshot: https://i.imgur.com/BGq4vtL.png


Yeah, I agree. And possibly show them both on that main page itself (maybe not the address page), and truncate, using tooltips on hover. ...I find myself pulling up a bunch of tabs for each transaction just to look at the destination addresses...the transaction ID (currently truncated) could be a tooltip as well.

Easy with twitter bootstrap (good choice Smiley).

http://getbootstrap.com/javascript/#tooltips

I thought it had a css-only way to do this as well...but I guess that might have been taken out in v3....
hero member
Activity: 938
Merit: 1000
Yeah good suggestion. I think currently I share a partial that can be used everywhere. I will fix that up next time I have a spare moment.

Keep it coming!
hero member
Activity: 700
Merit: 500
Just a small suggestion: the "Send transactions" section for an address currently shows the source address for each transaction. To me it would make much more sense to show the destination address instead.

Annotated screenshot: https://i.imgur.com/BGq4vtL.png
hero member
Activity: 938
Merit: 1000
I'm 99% sure it's a bug. As you know I'm constantly updating the code and sometimes this introduces new issues. I will check it out when I have the time.

Cheers. Here is example transaction: http://mastercoin-explorer.com/transactions/d31d3ef47d0b450343d0e3df8759f01e258fbd32277bcd758531b94896944f75

Fixed this transaction.

I think the best thing to do at the moment is re-parsing all Exodus transactions with the new code. This will be time costly but at least it will hopefully fix all transactions Smiley

Edit:

Re-import running. I will check out if this fixes the issues. FYI these type of things is why I wrote this addition to the spec. Myself and Bitboy already implemented the API but I just need time to finish the verification site itself.
sr. member
Activity: 240
Merit: 250
I'm 99% sure it's a bug. As you know I'm constantly updating the code and sometimes this introduces new issues. I will check it out when I have the time.

Cheers. Here is example transaction: http://mastercoin-explorer.com/transactions/d31d3ef47d0b450343d0e3df8759f01e258fbd32277bcd758531b94896944f75
hero member
Activity: 938
Merit: 1000
I'm 99% sure it's a bug. As you know I'm constantly updating the code and sometimes this introduces new issues. I will check it out when I have the time.
sr. member
Activity: 240
Merit: 250
A whole lot of transactions have suddenly been changed to invalid. I am hoping that this is a bug?
LOL
member
Activity: 71
Merit: 10

I tried to create another purchase offer using Mastercoin wallet:
https://blockchain.info/tx/bf56a1ec213fdfcff0f26c8a9ab7eb7588ed5c0ddb202a225e12b35a0617c06e

However, it does not show up in Mastercoin wallet and Mastercoin-explorer. Am I doing something wrong here?

EDIT: I created another purchase offer:
https://blockchain.info/tx/025d9ed3f1dd620c84f7e5418fdf5635b7d9ca08350fac51a22b39389228fe01

This time it shows up on ME and Mastercoin wallet – but I'm not able to pay because it says "Not enough received".

Same thing happened to me earlier.

On that same note, I placed a purchase offer for 1.0 test mastercoin and even though I never broadcast a payment transaction ME and the wallet say that I have a balance of 1.0 test mastercoin. My assumption is that it's challenging to differentiate between a purchase offer and the payment transaction. If the purchase offer transaction exceeds the amount of bitcoin to finalize the exchange, will it finalize the exchange?

Could you give me the transaction ids of the purchase offers in question. I think there is still a bug in my code where it will accept the Purchase Offer as payment if it was enough to satisfy the offer. It is not in the spec yet but I think the payment should always come one block _after_ the purchase offer.

Transactions following:

694ca7bff4fccf27bf348b6433dd2d32f1c4194e8c20b11aee370ded47641863
972fa24d0833fd431c7f69b77958c5ac5fb6287b9437fe8c756d9af44f5bc33e
hero member
Activity: 938
Merit: 1000
I just discovered there is a part of the spec that we (developers) haven't discussed yet that's very open to interpretation. I just created a post to discuss the consequences of this part in the spec and closed my Selling Order until we can update the spec on how to parse these transactions.
Pages:
Jump to: