Skip to content

Union types using redis subscription do not send. #8302

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

Open
danCarTrim opened this issue May 22, 2025 · 0 comments
Open

Union types using redis subscription do not send. #8302

danCarTrim opened this issue May 22, 2025 · 0 comments

Comments

@danCarTrim
Copy link

Product

Hot Chocolate

Version

15.1.5

Link to minimal reproduction

https://github.com/danCarTrim/HC-Union-Redis-Issue

Steps to reproduce

When running the sample code above subscription messages will be received in NitroUI.
When redis subscription is used (please un comment line 14 in program.cs) no messages are received.

What is expected?

For InMemorySubscriptions or RedisSubscriptions messages with union types should be sent.

What is actually happening?

When using redis subscriptions union types are not being sent.
(Union type is a field in a parent type)

Relevant log output

Microsoft.AspNetCore.Server.Kestrel.Connections: Debug: Connection id "0HNCOPU3VU98T" accepted.
Microsoft.AspNetCore.Server.Kestrel.Connections: Debug: Connection id "0HNCOPU3VU98T" started.
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 GET http://localhost:5095/graphql - - -
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: 1 candidate(s) found for the request path '/graphql'
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: Endpoint 'Hot Chocolate GraphQL Pipeline' with route pattern '/graphql/{**slug}' is valid for the request path '/graphql'
Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware: Debug: Request matched endpoint 'Hot Chocolate GraphQL Pipeline'
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executing endpoint 'Hot Chocolate GraphQL Pipeline'
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executed endpoint 'Hot Chocolate GraphQL Pipeline'
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished HTTP/1.1 GET http://localhost:5095/graphql - 101 - - 27.1310ms
Microsoft.AspNetCore.Server.Kestrel.Connections: Debug: Connection id "0HNCOPU3VU98U" accepted.
Microsoft.AspNetCore.Server.Kestrel.Connections: Debug: Connection id "0HNCOPU3VU98T" disconnecting.
Microsoft.AspNetCore.Server.Kestrel.Connections: Debug: Connection id "0HNCOPU3VU98U" started.
Microsoft.AspNetCore.Server.Kestrel.Connections: Debug: Connection id "0HNCOPU3VU98T" stopped.
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 GET http://localhost:5095/graphql - - -
Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets: Debug: Connection id "0HNCOPU3VU98T" sending FIN because: "The Socket transport's send loop completed gracefully."
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: 1 candidate(s) found for the request path '/graphql'
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: Endpoint 'Hot Chocolate GraphQL Pipeline' with route pattern '/graphql/{**slug}' is valid for the request path '/graphql'
Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware: Debug: Request matched endpoint 'Hot Chocolate GraphQL Pipeline'
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executing endpoint 'Hot Chocolate GraphQL Pipeline'

Additional context

I am using Azure cache for redis.
When running using inMemory vs redis logs look identical at debug level.
No errors are shown anywhere.

Using redis subscriptions:
Image

Using inMemorySubscriptions:
Image

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

No branches or pull requests

1 participant