Skip to content

Conversation

@karthik2804
Copy link
Contributor

Fixes the case where the guest wit states wasi:http/incoming-handler@0.2.0 but the engine exports wasi:http/incoming-handler@0.2.2.

Signed-off-by: karthik2804 <karthik.ganeshram@fermyon.com>
Signed-off-by: karthik2804 <karthik.ganeshram@fermyon.com>
@karthik2804 karthik2804 force-pushed the retain_fetchEvent_wasi_patch_versions branch from ba8c2ff to b87cdb2 Compare January 16, 2025 11:31
@karthik2804
Copy link
Contributor Author

Are we okay bumping this to 4s? I see the last few commits have also failed on it.

// TODO: fix back to half a millisecond when Weval fix is added
if (time > 3) {
throw new Error('took more than half a millisecond - ' + time + ' ms');
}

Copy link

@guybedford guybedford left a comment

Choose a reason for hiding this comment

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

Yes, bumping CI to 4 or 5 seconds would be fine.

Signed-off-by: karthik2804 <karthik.ganeshram@fermyon.com>
@karthik2804 karthik2804 force-pushed the retain_fetchEvent_wasi_patch_versions branch from 0787fb3 to 775899a Compare January 16, 2025 16:39
@guybedford guybedford merged commit 54bbab4 into bytecodealliance:main Jan 16, 2025
11 checks passed
@karthik2804 karthik2804 deleted the retain_fetchEvent_wasi_patch_versions branch January 16, 2025 21:08
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