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

[BUG] Duplicate callback outputs not working when deployed with gunicorn #2480

Closed
hannahker opened this issue Mar 28, 2023 · 0 comments · Fixed by #2479
Closed

[BUG] Duplicate callback outputs not working when deployed with gunicorn #2480

hannahker opened this issue Mar 28, 2023 · 0 comments · Fixed by #2479

Comments

@hannahker
Copy link

hannahker commented Mar 28, 2023

Describe your context

Bug only present when app is deployed via Dash Enterprise.

dash                          2.9.1
dash-ag-grid                  2.0.0a4
dash-core-components          2.0.0
dash-design-kit               1.6.8
dash-extensions               0.0.65
dash-html-components          2.0.0
dash-leaflet                  0.1.23
dash-mantine-components       0.12.0
dash-table                    5.0.0

Describe the bug

Callbacks with duplicate outputs don't work reliably when my app is deployed with gunicorn (ie. DE), giving errors like this:

KeyError: "Callback function not found for output '..image-options.rowData...geojson.data...satellite-img.children@e635ba05b4e74958834c65e29d0a3207...classified-img.children@b954a7e5a88643d29e99412073ede694...image-options.selectedRows...delete-notify.children..', perhaps you forgot to prepend the '@'?"

There is definitely the appropriate decorator on my function. The callbacks behave as expected when I run the app locally, both with Python and with gunicorn. About 10% of the time the callback will run fine.

Expected behavior

I'd expect this KeyError not to occur when the app is deployed.

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 a pull request may close this issue.

1 participant