`before_first_request` is deprecated and is to be removed about webviz-ert

[valentin-krasontovitsch]

perfect, thanks! then i guess this issue can be closed?

[DanSava]

I looked a bit into it and the warning seems to be coming from the dash testing framework.

Even when using the most basic dash test from dash testing

# 1. imports of your dash app
import dash
from dash import html
# 2. give each testcase a test case ID, and pass the fixture
# dash_duo as a function argument
def test_001_child_with_0(dash_duo):
    # 3. define your app inside the test function
    app = dash.Dash(__name__)
    app.layout = html.Div(id="nully-wrapper", children=0)
    # 4. host the app locally in a thread, all dash server configs could be
    # passed after the first app argument
    dash_duo.start_server(app)
    # 5. use wait_for_* if your target element is the result of a callback,
    # keep in mind even the initial rendering can trigger callbacks
    dash_duo.wait_for_text_to_equal("#nully-wrapper", "0", timeout=4)
    # 6. use this form if its present is expected at the action point
    assert dash_duo.find_element("#nully-wrapper").text == "0"
    # 7. to make the checkpoint more readable, you can describe the
    # acceptance criterion as an assert message after the comma.
    assert dash_duo.get_logs() == [], "browser console should contain no error"
    # 8. visual testing with percy snapshot
    dash_duo.percy_snapshot("test_001_child_with_0-layout")

We can reproduce the warning.

Not sure why when running all tests it seems the warning is coming from specific tests, it is not. it comes from all tests if they are ran individually

I think it is a good idea to keep this issue open to just track that this is patched in time or if not to just pin the dash version once Flask 2.3 hits us.

[oysteoh]

@valentin-krasontovitsch could you as our next release manager just verify / check if this is now solved in dash? I guess it is not very far into the future before we go to flask 2.3 and this will break if not fixed.

[valentin-krasontovitsch]

fixed in dash 2.7.0 according to changelog

[valentin-krasontovitsch]

should i specify the min version in webviz-ert's requirements? or should i just make sure that bleeding / my current beta komodo build have a higher version? where do we fix this stuff, locally on the project level or globally in komodo or both, and it depends?

[valentin-krasontovitsch]

( fyi bleeding has dash 2.7.0 but please still answer the question above if you will ^^ )

[oysteoh]

I think just bumping in bleeding and your release is sufficient! Usually we try to have as little pinning / restrictions on the project level as possible.