Skip to content

Conversation

@dondonz
Copy link
Member

@dondonz dondonz commented Mar 21, 2025

We have just released 4.0.0 of DataLoader. This pulls it in

@dondonz dondonz added this to the 23.x breaking changes milestone Mar 21, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Mar 21, 2025

Test Results

  313 files  ±0    313 suites  ±0   55s ⏱️ ±0s
3 588 tests ±0  3 583 ✅ ±0  5 💤 ±0  0 ❌ ±0 
3 677 runs  ±0  3 672 ✅ ±0  5 💤 ±0  0 ❌ ±0 

Results for commit 35562f1. ± Comparison against base commit 154bb89.

This pull request removes 150 and adds 128 tests. Note that renamed tests count towards both.
	?
                __schema { types { fields { args { type { name fields { name }}}}}}
                __schema { types { fields { type { name fields { name }}}}}
                __schema { types { inputFields { type { inputFields { name }}}}}
                __schema { types { interfaces { fields { type { interfaces { name } } } } } }
                __schema { types { name} }
                __type(name : "t") { name }
                a1: __schema { types { name} }
                a1: __type(name : "t") { name }
                a2 :  __type(name : "t1") { name }
…
graphql.ScalarsBooleanTest ‑ parseValue throws exception for invalid input <java.lang.Object@601c686>
graphql.ScalarsBooleanTest ‑ serialize throws exception for invalid input <java.lang.Object@7af5dc85>
graphql.ScalarsIDTest ‑ parseValue allows any object via String.valueOf <java.lang.Object@7042cd1f>
graphql.ScalarsIDTest ‑ serialize allows any object via String.valueOf <java.lang.Object@1c283acb>
graphql.ScalarsIntTest ‑ parseValue throws exception for invalid input <java.lang.Object@facd2dd>
graphql.ScalarsIntTest ‑ serialize throws exception for invalid input <java.lang.Object@27b35e5e>
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@7345211 fieldCollector=graphql.execution.FieldCollector@11358f2f executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@3886a966 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@33d6a48a resolvedType=graphql.execution.ResolveType@1657dc3b>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@26e624a2 fieldCollector=graphql.execution.FieldCollector@20922600 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@88c802d dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@109b2338 resolvedType=graphql.execution.ResolveType@74fc6bd>, #1]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@2729d862 fieldCollector=graphql.execution.FieldCollector@3a6ae2e executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@78403121 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@6dfc2a44 resolvedType=graphql.execution.ResolveType@47f1551>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@439c4c3c fieldCollector=graphql.execution.FieldCollector@2947a0b6 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@1ac4abcc dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@43873045 resolvedType=graphql.execution.ResolveType@625b69a5>, #1]
…

♻️ This comment has been updated with latest results.

@dondonz dondonz marked this pull request as ready for review April 7, 2025 01:01
@dondonz dondonz merged commit 27b9def into master Apr 7, 2025
2 checks passed
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