The collective Mastercoin-explorer, Mastercoin-ruby and Mastercoin-wallet topic

[Faraday]

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

[1713501414]

1713501414

[1713501414]

1713501414

[1713501414]

1713501414

[1713501414]

1713501414

[1713501414]

1713501414

[Tachikoma]

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

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.

[maxmint]

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

[Tachikoma]

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!

[rbdrbd]

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 ).

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....

[Tachikoma]

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 ).

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

[maxmint]

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!

[Tachikoma]

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.

[rottenchris]

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 `<top (required)>'
   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 `<main>'
   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 `<main>'
-----------------------------------------------------------


Any ideas?

[Tachikoma]

Would you be willing to pm me your address? It's seems to be related to your transactions.

[superfluouso]

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?

[Tachikoma]

Could you give me the full traceback?

[superfluouso]

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?

[Tachikoma]

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

[superfluouso]

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 `<top (required)>'
    from /usr/local/bin/mastercoin-wallet:23:in `load'
    from /usr/local/bin/mastercoin-wallet:23:in `<main>'
/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]

[Tachikoma]

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 `<top (required)>'
    from /usr/local/bin/mastercoin-wallet:23:in `load'
    from /usr/local/bin/mastercoin-wallet:23:in `<main>'
/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?

[superfluouso]

Lack of btc on that address is likely the issue as it only contains 0.00024 I believe- I think I was just surprised by the abrupt crash.

I guess that leads to my next question related to the difference between the btc balances reported in the wallet versus the client.

For instance on one address, I have 0.1 BTC but the client indicates BTC as 0.00197113..why is that?

[Tachikoma]

Yeah the crash should not happen. I already have it on my todo but I'm currently caught up with all the distributed exchange work.

Is it possible that transaction is not confirmed yet?

[superfluouso]

No - its been confirmed for over 24 hours at least..but I think I've been noticing the btc difference for awhile but have just ignored as the amounts in each case were adequate for my testing and I probably thought it had to do with confirmations also.  Anyways, I'll leave you to the DEX..its much more important

[Tachikoma]

Can you pm me the address in question? I will try to figure it out