Author Topic: scan failure? Bad address  (Read 5204 times)

0 Members and 1 Guest are viewing this topic.

Offline matt608

  • Hero Member
  • *****
  • Posts: 878
    • View Profile
Cusknee has a problem which sounds related to this - can anyone help? He voted and his funds never came back.
https://bitsharestalk.org/index.php?topic=11847.msg159613#msg159613

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)

Very interesting.  Looks like something that was already fixed for our next release.  We will get a new release out today that addresses this issue among several others.

Thanks , need it ASAP ,  because it's the PLAY snapshot time .

https://github.com/BitShares/bitshares/releases/tag/v0.4.24.1
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline cn-members

  • Sr. Member
  • ****
  • Posts: 365
    • View Profile
As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)

Very interesting.  Looks like something that was already fixed for our next release.  We will get a new release out today that addresses this issue among several others.

Thanks , need it ASAP ,  because it's the PLAY snapshot time .
BTS中文区发言人公共账号,帮助社区有效沟通与交流。
Chinese Community Spokesman Account,to help the effective communication between Chinese and other members of the community.We're not translators to do regular translations , but will help with vital ones as we see fit and available at that time.

Offline bytemaster

As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)

Very interesting.  Looks like something that was already fixed for our next release.  We will get a new release out today that addresses this issue among several others.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline monsterer

As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
As long as delegates continue signing block it is a minor issue .. imho

Offline monsterer

It was a minor bug with the wallet.

I like your definition of 'minor' :p
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline CLains

  • Hero Member
  • *****
  • Posts: 2606
    • View Profile
  • BitShares: clains
It was a minor bug with the wallet.

Devs already handled it, so exchanges just needs to update and we are good.  ;)

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
the problem is because somebody try a escrow transaction, but still not support by client
Code: [Select]
btsbots (unlocked) >>> blockchain_get_block 1209399
{
  "previous": "006648b96af11d06e3b6c55c8cf295d571148c51",
  "block_num": 1209399,
  "timestamp": "20141208T003100",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "b4864ba1493f38fa226b9d49e404c329a73419ff",
  "previous_secret": "690d2d987911bed1ef2283a683045de12a3cdf2f",
  "delegate_signature": "206be773a62d0005d750a45dfd16a71b1a8bbb5c3b087582603c6b6f4df93acbd3bb55c0e3112e9ce02a99723088e78b8168f79f781212dd47a2a95faa701d0112",
  "user_transaction_ids": [
    "4a7efe44c91909c1214762c186b8c57ae12a16f3",
    "d307c1e97d427428f1d5859d2be608ff1b2ccc6f"
  ]
}
btsbots (unlocked) >>> blockchain_get_transaction 4a7efe44c91909c1214762c186b8c57ae12a16f3
{
  "trx": {
    "expiration": "20141208T013055",
    "delegate_slate_id": null,
    "operations": [{
        "type": "deposit_op_type",
        "data": {
          "amount": 1000000,
          "condition": {
            "asset_id": 0,
            "delegate_slate_id": 9473675977916939725,
            "type": "withdraw_escrow_type",
            "data": {
              "owner": "BTSX111111111111111111113MQ7LD",
              "start_time": "20240917T192947",
              "duration": 3845107543,
              "original_balance": -4376472804032454471
            }
          }
        }
      },{
with me the problems started when trying to email somebody via the BTS wallet before it is officially supported...  I suggest they must somehow block commands for the client  as long as they are still  on BETA stage ...  at least for the gui...

Sent from my ALCATEL ONE TOUCH 997D


Offline cn-members

  • Sr. Member
  • ****
  • Posts: 365
    • View Profile
BTS中文区发言人公共账号,帮助社区有效沟通与交流。
Chinese Community Spokesman Account,to help the effective communication between Chinese and other members of the community.We're not translators to do regular translations , but will help with vital ones as we see fit and available at that time.

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
the problem is because somebody try a escrow transaction, but still not support by client
Code: [Select]
btsbots (unlocked) >>> blockchain_get_block 1209399
{
  "previous": "006648b96af11d06e3b6c55c8cf295d571148c51",
  "block_num": 1209399,
  "timestamp": "20141208T003100",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "b4864ba1493f38fa226b9d49e404c329a73419ff",
  "previous_secret": "690d2d987911bed1ef2283a683045de12a3cdf2f",
  "delegate_signature": "206be773a62d0005d750a45dfd16a71b1a8bbb5c3b087582603c6b6f4df93acbd3bb55c0e3112e9ce02a99723088e78b8168f79f781212dd47a2a95faa701d0112",
  "user_transaction_ids": [
    "4a7efe44c91909c1214762c186b8c57ae12a16f3",
    "d307c1e97d427428f1d5859d2be608ff1b2ccc6f"
  ]
}
btsbots (unlocked) >>> blockchain_get_transaction 4a7efe44c91909c1214762c186b8c57ae12a16f3
{
  "trx": {
    "expiration": "20141208T013055",
    "delegate_slate_id": null,
    "operations": [{
        "type": "deposit_op_type",
        "data": {
          "amount": 1000000,
          "condition": {
            "asset_id": 0,
            "delegate_slate_id": 9473675977916939725,
            "type": "withdraw_escrow_type",
            "data": {
              "owner": "BTSX111111111111111111113MQ7LD",
              "start_time": "20240917T192947",
              "duration": 3845107543,
              "original_balance": -4376472804032454471
            }
          }
        }
      },{

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
here is the patch for client, delegate don't need to upgrade.
Code: [Select]
diff --git a/libraries/wallet/transaction_ledger.cpp b/libraries/wallet/transaction_ledger.cpp
index 0623a6c..0d6e98a 100644
--- a/libraries/wallet/transaction_ledger.cpp
+++ b/libraries/wallet/transaction_ledger.cpp
@@ -1178,6 +1178,11 @@ bool wallet_impl::scan_deposit( const deposit_operation& op, const vector<privat
           // TODO: FC_THROW( "withdraw_option_type not implemented!" );
           break;
        }
+       case withdraw_escrow_type:
+       {
+          // TODO: FC_THROW( "withdraw_option_type not implemented!" );
+          break;
+       }
        default:
        {
           FC_THROW( "unknown withdraw condition type!" );

Offline svk

Same here:

Code: [Select]
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Worker: dev.bitsharesblocks

merockstar

  • Guest
Anyone try to delete mail folder?

yes. works for the segmentation fault im experiencing in a different thread. still getting the scanning error though.

zerosum

  • Guest
Anyone try to delete mail folder?

If I would expect somebody to come with the most illogical solution that works, that will be *Dani the Lion* ...so just try it, I say.