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

Experimental @defer support does not work with AutoPersistedQueryInterceptor #5667

Closed
rohandhruva opened this issue Feb 29, 2024 · 1 comment · Fixed by #5677
Closed

Experimental @defer support does not work with AutoPersistedQueryInterceptor #5667

rohandhruva opened this issue Feb 29, 2024 · 1 comment · Fixed by #5677

Comments

@rohandhruva
Copy link
Contributor

Version

4.0.0-beta.4

Summary

When using @defer, a response will have multiple parts. However, AutoPersistedQueryInterceptor uses var response = chain.proceed(request).single(), which will lead to an immediate IllegalArgumentException, because: Flow has more than one element.

Steps to reproduce the behavior

Enable the AutoPersistedQueryInterceptor and use any operation that has @defer. The failure should reproduce even if you use client.query().toFlow().

Logs

No response

@BoD
Copy link
Contributor

BoD commented Mar 5, 2024

Thanks a lot for reporting! A fix will be in the next release and in the meantime it can be tried out with the snapshots.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants