Repository navigation
[BUG] Dev Tools: Callback map error: Not possible to find intersection inside of the rectangle #3943
Description
Activity
@ghaarsma thanks for reporting this. Based on the error this is coming up in the actual graph rendering library we use.
Since the reproduction is fairly clear, it might be an interesting first issue if anyone wants to track it down!
I’d like to investigate this issue. The reproducible callback map and the fact that removing specific callbacks changes the rendering error provide a good starting point.
I’ll trace the Dev Tools callback-map rendering flow into the underlying graph rendering/layout library, identify where the rectangle intersection calculation fails, and compare the generated graph structure/layout for the working and failing cases. If the issue is in the graph library integration or in the graph data passed by Dash, I’ll narrow it down to a minimal reproducible case and look into a regression test and fix.
Please do! Let us know what you find out.
Fun fact: you can comment out line # 241
Input("open_template", "n_clicks"),in the attached example and the map will generate ok at that point in time. If you then change the layout toforceorforce-looseand then uncomment line #241 and wait for the auto-reload, the callback map at that point does get generated.If you then go back to
top-downorleft-rightlayout, the callback map crashes again. Hope that helps troubleshooting.Reacted by Robert Claus
When trying to show the Callbacks on the Dash Dev Tools, the attached example generates an error and the callback map does not show up.
Tested with Dash 4.4.1 and both Firefox and Chrome. Also tried older versions of Dash (3.4.0 and 4.x with the same results). To reproduce, run the attached example.
callback_map.py
Note: Comment out callback
toggle_template_modalon lines 239-246 and the callback map will get generated. Removal of some other callbacks likesave_proposed_mappedcan result on other errors like:can't access property "order", g.node(...) is undefined