Remove force-enable block production from wrapper script
- Removes AITBC_FORCE_ENABLE_BLOCK_PRODUCTION, ENABLE_BLOCK_PRODUCTION, and enable_block_production environment variable overrides - Block production is now controlled by env file settings (enable_block_production) - Allows follower nodes to properly disable block production via configuration
This commit is contained in:
@@ -21,12 +21,8 @@ os.environ["PYTHONPATH"] = f"{REPO_DIR}/apps/blockchain-node/src"
|
|||||||
os.environ["DATA_DIR"] = str(DATA_DIR)
|
os.environ["DATA_DIR"] = str(DATA_DIR)
|
||||||
os.environ["LOG_DIR"] = str(LOG_DIR)
|
os.environ["LOG_DIR"] = str(LOG_DIR)
|
||||||
|
|
||||||
# Force disable block production in combined_main to prevent event loop blocking
|
# Block production is controlled by env file settings (enable_block_production)
|
||||||
# The combined_main runs both node logic and HTTP RPC server in the same process
|
# The proposer runs in the event loop without blocking - no force-enable needed
|
||||||
# Block production in the RPC process can cause timeouts during transaction submission
|
|
||||||
os.environ["AITBC_FORCE_ENABLE_BLOCK_PRODUCTION"] = "true"
|
|
||||||
os.environ["ENABLE_BLOCK_PRODUCTION"] = "true"
|
|
||||||
os.environ["enable_block_production"] = "true"
|
|
||||||
|
|
||||||
# Execute the actual service
|
# Execute the actual service
|
||||||
# Use combined_main to run both blockchain node and HTTP RPC server
|
# Use combined_main to run both blockchain node and HTTP RPC server
|
||||||
|
|||||||
Reference in New Issue
Block a user