Skip to content

make dataloader work inside defer blocks #3980

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

Merged
merged 15 commits into from
May 26, 2025
Merged

make dataloader work inside defer blocks #3980

merged 15 commits into from
May 26, 2025

Conversation

andimarek
Copy link
Member

No description provided.

Copy link
Contributor

github-actions bot commented May 22, 2025

Test Results

  316 files  ±    0    316 suites  ±0   2m 26s ⏱️ ±0s
4 656 tests +1 002  4 647 ✅ +998  9 💤 +4  0 ❌ ±0 
4 745 runs  +1 002  4 736 ✅ +998  9 💤 +4  0 ❌ ±0 

Results for commit a7cc794. ± Comparison against base commit 9ac3e63.

This pull request removes 192 and adds 1172 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.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure23@6f3f0fae delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure24@63fdffcd delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure25@7428de63 delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure20@655523dd delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure21@6f7e336b delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure22@3a2b2322 delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure3@60e21209 delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure4@35835fa delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure5@4dafba3e delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertNotNull with different number of error args with non null does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_6prov0_closure6@15bc339 delegate=graphql.AssertTest@7a2e0858 owner=graphql.AssertTest@7a2e0858 thisObject=graphql.AssertTest@7a2e0858 resolveStrategy=0 directive=0 parameterTypes=[class java.lang.Object] maximumNumberOfParameters=1 bcw=null>, expectedMessage: error arg1, #0]
…
This pull request skips 4 tests.
graphql.GraphqlErrorHelperTest ‑ can handle custom extensions and custom error classification
graphql.GraphqlErrorHelperTest ‑ can handle custom extensions with classification
graphql.GraphqlErrorHelperTest ‑ can parse out a map and make an error
graphql.GraphqlErrorHelperTest ‑ can turn error classifications into extensions

♻️ This comment has been updated with latest results.

* The expected field fetch count is accurate when all execute object calls happened
* The expected execute object count is accurate when all sub selections fetched
* are done in the previous level
* A general overview of teh tracked data:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: "the"

@andimarek andimarek merged commit 6e9e023 into master May 26, 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.

3 participants