Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bridge: log svix client errors as error, not trace #1368

Merged
merged 1 commit into from
Jul 12, 2024

Conversation

svix-onelson
Copy link
Contributor

We've got 3 places where we log errors in the poller loop and this one somehow wound up logging as trace! instead of error! like the rest.

Follow-on from #1363

We've got 3 places where we log errors in the poller loop and this one
somehow wound up logging as `trace!` instead of `error!` like the rest.
@svix-onelson svix-onelson requested a review from a team as a code owner July 11, 2024 23:27
@svix-onelson svix-onelson merged commit a99a542 into main Jul 12, 2024
5 checks passed
@svix-onelson svix-onelson deleted the onelson/poller-logging branch July 12, 2024 14:33
svix-lucho added a commit that referenced this pull request Jul 31, 2024
## What's Changed
* Bridge: add `/events` poller by @svix-onelson in
#1363
* server: Optimize all external host dependencies for faster rebuilds by
@svix-jplatte in #1365
* Bridge: log svix client errors as error, not trace by @svix-onelson in
#1368
* Bump Cargo lockfiles by @svix-jplatte in
#1370
* server: add configuration to for changing service name on
OpenTelemetry by @LeoZ100 in
#1371
* build(deps): bump openssl from 0.10.64 to 0.10.66 in /bridge by
@dependabot in #1372
* bridge: Require type field for kafka input, output by @svix-jplatte in
#1374
* Bump OpenAPI spec and regenerate libs by @svix-lucho in
#1375

## New Contributors
* @LeoZ100 made their first contribution in
#1371

**Full Changelog**:
v1.25.0...v1.26.0
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.

2 participants