ChilliCream / ChilliCream/graphql-platform

Disposed Error StrawberryShake.ObserverSession

Open
#6,171 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🌶️ strawberry shake
Dominant language
C#
Stars
5.8k
Forks
810
Avg merge
15h 39m
Merged PRs (30d)
98

Description

Is there an existing issue for this?
  • I have searched the existing issues
Product

Strawberry Shake

Describe the bug

It's entirely possible I've got something set up wrong here, but in a Blazor WASM project I'm seeing this error crop up quite a lot:

image

Just wondering if there's anything specifically I should be looking out for in trying to narrow this one down?

Thanks!

Steps to reproduce
  1. Add a GraphQL query to a Blazor WASM application
  2. Build the project (so it generates the relevant Blazor Components)
  3. Use the Blazor component

Here's an example, which uses the IGetTaskListResult identified in the log:

<UseGetTaskList Filter="@($"id eq '{Id}'")">
    
    <ChildContent>
        @{
            var taskList = context.QueryTaskListContents.FirstOrDefault();
            var tasks = MapTasks(@taskList.FlatData.Tasks);
        }
        
        @if (taskList != null)
        {
            <TaskList Id="@taskList.Id" Course="practicalblazorcomponents" Title="@taskList.FlatData.Title" Tasks="tasks"/>
        }
    </ChildContent>
    
</UseGetTaskList>
Relevant log output

No response

Additional Context?

No response

Version

13.0.5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in a Blazor WASM application using a generated Strawberry Shake component and the supplied UseGetTaskList example. Inspect when the ObserverSession disposal error appears and use the issue's reproduction steps to narrow it down; the payload names no source file, test, or defined fix, so completion criteria remain unclear.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.