fix: do not cancel importer when finished loading all blocks

[dinhani-cw]

No description provided.

[github-actions]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the changes are localized to a specific part of the code and involve a straightforward logic modification. The PR is small and the context of the change is clear, making it easier to review.
🧪 Relevant tests	No
🔍 Possible issues	Possible Bug: The removal of cancellation.cancel(); might lead to unintended behavior if other parts of the system rely on this cancellation signal to stop processing or clean up resources.
🔒 Security concerns	No

Code feedback:

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review which includes several types of feedbacks, such as possible PR issues, security threats and relevant test in the PR. More feedbacks can be added by configuring the tool.

The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.

• When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

• With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

See the review usage page for a comprehensive guide on using this tool.

[github-actions]

PR Code Suggestions

Category

Suggestions

Bug

Correct the pattern matching syntax to prevent compilation errors. The pattern matching syntax used is incorrect and will cause a compilation error. Rust uses if let or match for pattern matching. Here, you should use if let to handle the option returned by tasks.next().await. src/bin/importer_offline.rs [209-211] -let Some(result) = tasks.next().await else { +if let Some(result) = tasks.next().await { + // process result +} else { break "no more blocks to process"; -}; +}

---

✨ Improve tool usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.

• When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

• With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

See the improve usage page for a comprehensive guide on using this tool.