James Roeder

[BUG] Context .invoke() fails quietly and .forward() fails

6

### Describe the bug When attempting to use the `invoke()` or `forward()` methods on a `typer.Context` object, the results are unpredictable, resulting in either outright failures, or passing of strange...

According to: https://developers.cloudflare.com/workers/runtime-apis/request#requestinitcfproperties `RequestInitCfProperties` has a `webp` field (`webp?: boolean`)

HTTPHeaderMap splitting on commas can lead to unpredictable request headers

1

(Related to #314, but impacts the request side of things) Because of the way HTTPHeaderMap splits header values on commas into multiple ways, servers may have trouble understanding headers with...

Fixes #389

autodiscover does not actually log errors on discovery

3

## Checklist - [x] I have included information about relevant versions - [x] I have verified that the issue persists when using the `master` branch of Faust. ## Steps to...

#148 seems to have introduced a regression of sorts when using a library which has its own definitions of types used by `fetch`. The following code worked fine with earlier...

Support creating an appropriate SSLContext for use with open_connection

1

One can pass a curio.ssl.SSLContext when using multio.open_connection, but this requires using curio.

`Promise will never complete` when instrumenting worker

6

We have a pretty complex cloudflare worker that we recently added instrumentation to with `otel-cf-workers`. The library has worked like a dream, providing extra insight into our requests. However, when...

Using ResolveConfigFn does not reevaluate exporter URL for every request

3

This tripped me up - we are trying to support sending metrics to different URLs based on request criteria. It appears that regardless of what we return from our `ResolveConfigFn`,...