Is suppress_callback_exceptions no longer supported in Dash v1.11.0

[flyingcujo]

I upgraded my multi-page app from v1.10 to v1.11 and is appears that the suppress_callback_exceptions=True setting no longer works.

Has this been depreciated and we now need to rewrite our callbacks in the pattern-matching format?

[flyingcujo]

A nonexistent object was used in an `Output` of a Dash callback. The id of this object is `delete-bulk` and the property is `style`. The string ids in the current layout are: [chart-options-store, TimeZonePicker, DatumPicker, hilo-data-store, station-gps-store, session-data-store, highlight-store, url-sources-store, auth-user, reset-layout, slider-marks, aws-data, yearly-aws-data, user-data, delete-status, email-list, data-conditional, url, page-content]

(This error originated from the built-in JavaScript code that runs Dash apps. Click to see the full stack trace or open your browser's console.)
ReferenceError: A nonexistent object was used in an `Output` of a Dash callback. The id of this object is `delete-bulk` and the property is `style`. The string ids in the current layout are: [chart-options-store, TimeZonePicker, DatumPicker, hilo-data-store, station-gps-store, session-data-store, highlight-store, url-sources-store, auth-user, reset-layout, slider-marks, aws-data, yearly-aws-data, user-data, delete-status, email-list, data-conditional, url, page-content]```

    at unwrapIfNotMulti (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34632:15)

    at http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34750:26

    at Array.map (<anonymous>)

    at http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34749:42

    at Array.map (<anonymous>)

    at _callee3$ (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34735:40)

    at tryCatch (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/polyfill@7.v1_3_0m1586525360.8.7.min.js:1:93205)

    at Generator.invoke [as _invoke] (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/polyfill@7.v1_3_0m1586525360.8.7.min.js:1:92979)

    at Generator.t.<computed> [as next] (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/polyfill@7.v1_3_0m1586525360.8.7.min.js:1:93737)

    at asyncGeneratorStep (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34512:103)

[Emil]

What you are experiencing is known behavior. There are ongoing discussions on how to handle the issue,

Dash v1.11.0 Release - Introducing Pattern-Matching Callbacks

Update: version 1.16 has been released since this was posted. Dash v1.11.0 is a minor release introducing the new Pattern-Matching Callbacks feature and providing multiple bug fixes improving the performance, robustness and behavior of Dash callbacks. Official Changelog Dash v1.11.0 Highlights New Pattern-Matching Callbacks feature that allows you to write callbacks that respond to or update an arbitrary or dynamic number of components (PR #1103) Multiple bug fixes for callbacks, includi…

For now, a possible solution/workaround is,

ReferenceError in multipage application

While not a real solution to the problem (which i have not yet understood fully; it seems to happen only in some cases), i have come up with a workaround using the new Dash pattern matching callbacks in Dash v1.11.0 Release - Introducing Pattern-Matching Callbacks. Let’s say that the problematic callback looks like this, @app.callback(Output(SITE_HEIGHT_CACHE, 'data'), [Input(SITE_HEIGHT_SLIDER, 'value')]) def update_site_height(value): return value with th…

[flyingcujo]

Thanks @Emil! I’ll wait for the next version before upgrading.