Return root result without blocking due to sparse trie Drop

[Rjected]

It would be great if we could return the state root result, without blocking it due to dropping the sparse trie. I noticed this in profiles of the main state root task thread:

Maybe we should send task_tx in run_sparse_trie:

reth/crates/engine/tree/src/tree/root.rs

Lines 562 to 573 in b955551

	let (tx, rx) = mpsc::channel();
	thread_pool.spawn(move || {
	debug!(target: "engine::tree", "Starting sparse trie task");
	let result = match run_sparse_trie(config, metrics, rx) {
	Ok((state_root, trie_updates, iterations)) => {
	StateRootMessage::RootCalculated { state_root, trie_updates, iterations }
	}
	Err(error) => StateRootMessage::RootCalculationError(error),
	};
	let _ = task_tx.send(result);
	});
	tx

[VyuduInc]

Yo @shekhirin, let me clean this up. These State Root Task DEBUG logs are giving a whole lot of noise but not enough signal, and that’s a problem. Debugging should accelerate solutions, not slow them down. I’ll go in, trim the clutter, enhance the context, and structure logs so they actually tell you what’s going on.

Been engineering backend systems for 15+ years and deep in blockchain since 2017—I know how to turn logs from a headache into a tool. Let me take this, and you’ll get logs that are clean, clear, and actually useful for debugging.

[ritik4ever]

Would love to tackle this!