So, long story short, I have a Dash app inside of a bigger Flash app. On one point, I define a function that would be called by init routines and define callbacks. Smth like this (in an abridged form): def make_callbacks(dashapp): @dashapp.callback( Output('graph_impl', 'elements'), …

Having the same problem, no idea on solution but what I think is going on to answer your question #2 is that something about the deployment is creating anonymized callbacks in an attempt to distinguish between multiple instances, but the left hand doesn’t know what the right is doing for some reason…

Hey, thank for stopping by and welcome to the community! It turns out that you gave almost a Schrodinger’s answer! Weirdly enough, everything works as it supposed to when the app is run containerized via gunicon with a single worker or with a plain interpreter. But the odd part of that revelation i…

Yep, also Docker and Gunicorn – but unfortunately I inherited that setup, so there are decisions made in the config that I don’t yet fully understand. I’ve been playing around with the PYTHONHASHSEED param in Docker because I thought that callback name hash salting could have been the problem, but …

Well, I inherited my thing from myself only, haha) Were you able to reproduce the problem in a testing setup? Just a plain Dash app with a couple of callbacks inside docker? Weirdly enough I’m failing to reproduce this gunicorn problem with trivial layouts – treacherously it performs well with mult…

No, I’ve not been able to reproduce anywhere except the targeted end deployment (which is the place I’d most like it to work…) yet.

Ok, I did solve it. The problem was PYTHONHASHSEED, should be set to 0 (a constant might work too, but random [the default] causes the problem). The reason I didn’t find this at first is because I was setting that value too early in my Dockerfile. Moving PYTHONHASHSEED=0 after a couple of pip ope…

Hey. I was facing a similar problem when deploying a Dash application to Elastic Beanstalk with NGINX and gunicorn. The solution for me was upgrading to Dash 2.13.0. I’m placing my investigation and solution here to help anyone in a similar situation. My original problem was with Dash 2.9.1 and wa…

Hi, I’m facing the same type of Issue: I get the same error despite my application working locally even when launched with several gunicron workers but once deployed it logs these errors. Yet my application operates smoothly. I’m also using several callbacks with the same output. I’m on Dash 2.13…

Try logging out the app.callback_map.keys() and include the process IDs to see what callbacks does each gunicorn worker have. Note that I also was using dash_extensions so for me the setup to log the keys was: app = DashProxy() server = app.server app.register_callbacks() logger.info(app.callback…

[dash 2.9.2] KeyError: "Callback function not found for output does not make any sence in Docker

Dash Python

tntnkn April 12, 2023, 1:25pm 8

Hey, great that you managed to solve your issue! Doesn’t seem to fix my problem though, but other people might find it useful, so thanks for sharing!

Topic		Replies	Views
Duplicate callback outputs when restarting the dash app Dash Python question	6	1027	June 12, 2024
Duplicate Callback error - again Dash Python	5	1836	September 9, 2021
Dash callbacks triggering twice on Home page when running in Docker container Dash Python	3	433	October 25, 2023
Adding callback output Dash Python question	2	505	September 18, 2023
Multiple applications interfering with each other Dash Python question	0	380	August 22, 2022

[dash 2.9.2] KeyError: "Callback function not found for output does not make any sence in Docker

Related topics