Ryan Levick
Ryan Levick
For a second time, I've found myself in a debugging session ultimately due to me confusing component dependencies and target dependencies. I was confused why a local wit package would...
In a wit file I was referring to a dependency wit package but forgot to attach a version to it. Naturally, resolution failed as I don't have an unversioned package...
Currently target dependencies are specified through a map where the key is the `package:name` package id. However, multiple dependencies can have the same id if they are of different versions....
The following is an exploration pre-SIP on testing Spin applications. ## **High-Level Needs** At a high-level any testing mechanism for Spin needs the following: - **Test Definitions**: Users might be...
It's fairly common practice to automatically set the `Content-Length` header on behalf of the user. We should be doing this for outbound requests where the size of the request is...
The following is an attempt to describe what socket support in the Spin runtime would look like both from a user's perspective. This does not touch on guest support for...
## Status Quo Currently DNS resolution through the `wasi:sockets/ip-name-lookup` interface is completely blocked in Spin. Obviously, we want to allow for DNS resolution in a way that aligns well with...
The `outbound_postgres` runtime test often fails with a "Connection reset by peer". I don't believe this is an issue with the test but rather with the implementation.
We're currently only running the full integration test suite (i.e., the test suite that runs test that require more than a Rust and a Python toolchain) on Ubuntu. Running the...
The following is my attempt to understand the testing needs of Spin and sketch a possible path towards improved end to end testing for Spin. ## What needs testing Before...