-
When sending a `float` like 5.99, the transport and client used with `connect-es` show a value in the response like 5.986273959362626
Hitting the http endpoint does not produce this result.
**pleas…
-
**Describe the bug**
We are seeing in our auto error reporting from the browser application:
```
ConnectError: [unknown] network error
at Function.value (/workspace/gitpod/node_modules/@bu…
-
It appears that `@bufbuild` has moved over to a different organization and that new work is happening there. We would need to upgrade to that new version somehow.
Message I get when trying to insta…
-
Per Otel spec for gRPC only errors indicating server fault (like `INTERNAL`) must result in the span being marked as errors.
https://opentelemetry.io/docs/specs/semconv/rpc/grpc/#grpc-status
Error…
-
Hey team 👋
We're working on adopting `connect-swift` and are running into some issues compiling `connect-swift` for our watchOS app.
For context, we are attempting to perform unary requests fro…
-
**Describe the bug**
`createConnectTransport` replacing `user-agent` header on Safari and Firefox, but not chrome.
Chrome has a normal looking user agent, but Safari and Firefox are getting: `user…
-
https://github.com/open-telemetry/opentelemetry-specification/pull/3333 introduced a breaking change to the OpenTelemetry semantic conventions for gRPC so this should be implemented
-
The user for facing API today looks like:
```ts
import { useQuery } from '@tanstack/react-query';
import { example } from 'your-generated-code/example-ExampleService_connectquery';
export const …
-
0.5.1 works fine.
After upgrading to 0.5.2 webpack fails to build with these errors:
```ERROR in ../../node_modules/@connectrpc/connect-query/dist/esm/index.js 14:0-60
Module not found: Error: Ca…
-
**Is your feature request related to a problem? Please describe.**
I already use errors of type connect.Error throughout my handler code, but I also have some bulk endpoints that may return partial…
weeco updated
8 months ago