Chia-Network / chia-blockchain

Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)
Apache License 2.0
10.82k stars 2.03k forks source link

clawback bad bytes32 initializer [Bug] #15635

Closed danieljperry closed 1 year ago

danieljperry commented 1 year ago

What happened?

To reproduce, run the following CLI command: chia wallet clawback

Result:

Exception from 'wallet' bad bytes32 initializer b'':
Traceback (most recent call last):
  File "chia\cmds\cmds_util.py", line 104, in get_any_service_client
    yield node_client, config
  File "chia\cmds\cmds_util.py", line 224, in execute_with_wallet
    await function(extra_params, wallet_client, new_fp)
  File "chia\cmds\wallet_funcs.py", line 1277, in spend_clawback
    tx_ids.append(bytes32.from_hexstr(tid))
  File "chia\util\byte_types.py", line 53, in from_hexstr
    return cls.fromhex(input_str)
  File "chia\util\byte_types.py", line 35, in __init__
    raise ValueError("bad %s initializer %s" % (type(self).__name__, v))
ValueError: bad bytes32 initializer b''

Note that when given extra arguments, the command succeeds. For example, chia wallet clawback -h works as expected.

Version

1.8.2rc5 installed from binary

What platform are you using?

Windows

What ui mode are you using?

CLI

Relevant log output

No response

github-actions[bot] commented 1 year ago

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

wjblanke commented 1 year ago

dan is this still a problem

danieljperry commented 1 year ago

dan is this still a problem

Not fixed in 2.0.0b5.

github-actions[bot] commented 1 year ago

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

github-actions[bot] commented 1 year ago

This issue was automatically closed because it has been flagged as stale, and subsequently passed 7 days with no further activity from the submitter or watchers.