Change Details

The use case for `poll_for_answer` without a `json_req` is limited to polling Fulcrum stats. Extract this use case into its own function to remove one level of indentation. This is a first step in making `poll_for_answer` less convoluted. The next commit will remove more indentation levels and the unnecessary `retry` flag. There is no change in behavior, as `wait_until` uses the same timeout and poll intervall as `poll_for_answer` by default.

The use case for `poll_for_answer` without a `json_req` is limited to polling Fulcrum stats. Extract this use case into its own function to remove one level of indentation. This is a first step in making `poll_for_answer` less convoluted. The next commit will remove more indentation levels and the unnecessary `retry` flag. There is no change in behavior, as `wait_until` uses the same timeout and poll intervall as `poll_for_answer` by default, and Fulcrum should be up and running after bitcoind_rpc_connection so the "Controller.Chain" check should not need more than a single poll .

The use case for `poll_for_answer` without a `json_req` is limited to polling Fulcrum stats. Extract this use case into its own function to remove one level of indentation. This is a first step in making `poll_for_answer` less convoluted. The next commit will remove more indentation levels and the unnecessary `retry` flag. There is no change in behavior, as `wait_until` uses the same timeout and poll intervall as `poll_for_answer` by default, and Fulcrum should be up and running after bitcoind_rpc_connection so the "Controller.Chain" check should not need more than a single poll .