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

fix(query-engine-wasm): add response_json_serialization span #5089

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

aqrln
Copy link
Member

@aqrln aqrln commented Dec 16, 2024

Add missing prisma:engine:response_json_serialization span in the WASM query engine. After this we can enable running the tracing tests with WASM in the client repo.

Add missing `prisma:engine:response_json_serialization` span in the WASM
query engine. After this we can enable running the tracing tests with
WASM in the client repo.
@aqrln aqrln requested a review from a team as a code owner December 16, 2024 15:26
@aqrln aqrln requested review from wmadden and removed request for a team December 16, 2024 15:26
@aqrln aqrln added this to the 6.1.0 milestone Dec 16, 2024
@aqrln aqrln requested review from jkomyno and removed request for wmadden December 16, 2024 15:26
Copy link

codspeed-hq bot commented Dec 16, 2024

CodSpeed Performance Report

Merging #5089 will not alter performance

Comparing wasm-missing-span (8620770) with main (79c7f7d)

Summary

✅ 11 untouched benchmarks

Copy link
Contributor

WASM Query Engine file Size

Engine This PR Base branch Diff
Postgres 2.079MiB 2.078MiB 672.000B
Postgres (gzip) 835.334KiB 835.121KiB 219.000B
Mysql 2.044MiB 2.044MiB 673.000B
Mysql (gzip) 821.726KiB 821.668KiB 59.000B
Sqlite 1.942MiB 1.942MiB 672.000B
Sqlite (gzip) 781.094KiB 780.993KiB 104.000B

@aqrln aqrln merged commit a5ab6a9 into main Dec 16, 2024
342 checks passed
@aqrln aqrln deleted the wasm-missing-span branch December 16, 2024 16:00
aqrln added a commit that referenced this pull request Dec 16, 2024
Expand the scope of the `prisma:engine:query` span to contain both the
request handler and the response serialization, identical to the
Node-API engine, preventing `prisma:engine:response_json_serialization`
from being orphaned outside the trace.

This is a follow up to #5089.
jkomyno pushed a commit that referenced this pull request Dec 17, 2024
* fix(query-engine-wasm): expand scope of `prisma:engine:query` span

Expand the scope of the `prisma:engine:query` span to contain both the
request handler and the response serialization, identical to the
Node-API engine, preventing `prisma:engine:response_json_serialization`
from being orphaned outside the trace.

This is a follow up to #5089.

* [integration]

* Add missing bits for transactions

* [integration]

* strip traceparents in attributes with driver adapters

* [integration]
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