Skip to content

Async storage#2170

Open
Tehforsch wants to merge 7 commits intomainfrom
async-storage
Open

Async storage#2170
Tehforsch wants to merge 7 commits intomainfrom
async-storage

Conversation

@Tehforsch
Copy link
Contributor

@Tehforsch Tehforsch commented Mar 17, 2026

Sorry for the massive PR, but this PR is basically the minimum set of changes that are demanded by putting async in front of retrieve, dispatch and remove.

To make my life easier, I removed all unnecessary trait bounds that we demanded of various types using the storage traits (ContextStorage in particular), so I could keep the trait bounds that needed to be added to a minimum.

Jira: SC-1511

@github-actions
Copy link

github-actions bot commented Mar 17, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA b25a2aa.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None

Comment on lines 650 to +655
if let Some(nvt) = nvt.take() {
self.dispatch_nvt(nvt);
// TODO: This might very well not work.
// Do we really need this Drop impl anyways?
futures::executor::block_on(async {
self.dispatch_nvt(nvt).await;
});
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a complicated issue, I would have liked to remove this drop impl but that requires rethinking the entire logic about setting the nvt fields in the ScanCtx (which arguably should be done in the ScriptCtx instead?) and it got too big for this already big PR. The current solution works, although it is ugly.

Tehforsch

This comment was marked as outdated.

@Tehforsch Tehforsch marked this pull request as ready for review March 18, 2026 12:51
@Tehforsch Tehforsch requested a review from a team as a code owner March 18, 2026 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants