Viceroy
Viceroy copied to clipboard
fastly
Viceroy provides local testing for developers working with Compute.
We have a couple of configs where we first deserialize to a `Raw` config type and then call `try_into` to convert to the validated and massaged final config type. This...
Customer reported issue while running code on local machine I'm trying to run the code locally via: fastly compute serve and I keep getting this error: ERROR: error during execution...
Fastly's UI provides stats on the RAM usage of a Compute@Edge program running in production. Viceroy should emit information about the memory usage of a single instance execution, so that...
Fastly's UI provides stats on the CPU time of a Compute@Edge program running in production. Viceroy should emit information about the duration of CPU time used for a single instance...
The Fastly CLI supports some platforms that Viceroy releases don't currently cover, such as arm64. We should add these platforms to both CI and release automation, and make sure the...
A number of Viceroy's error variants are automatic conversions from external library errors -- things like `http`'s errors for invalid headers or URIs, etc. Most of those underlying errors don't...
👋 Have we considered serving `fastly compute serve` over HTTPS instead of HTTP? My application isn’t working because I set HTTPS-only cookies, and I don’t want to make too many...
Currently if you don't provide `-C`, Viceroy will simply not load any configuration. Normally `-C` is automatically provided by the Fastly CLI, but when invoking Viceroy directly it probably makes...
We should make a pass through the C@E test suite and bring over as many as we can, to deepen our checks for fidelity.
Viceroy currently reports the final wasm heap size each time it completes a request. For greater fidelity to C@E, we should report the host heap usage as well, since both...