masenf/full-rehydrate - Branch - reflex-dev/reflex

Do a full re-hydrate on reconnect

#5980

Comparing

masenf/full-rehydrate

(

f30cfbc

) with

main

(

3617ee4

)

Untouched: 8

Benchmarks

Passed

test_get_all_imports[_stateful_page]

tests/benchmarks/test_compilation.py

+1%

3.1 ms3 ms

test_compile_page[_stateful_page]

tests/benchmarks/test_compilation.py

+1%

10.5 ms10.4 ms

test_compile_stateful[_stateful_page]

tests/benchmarks/test_compilation.py

147.8 µs147.2 µs

test_evaluate_page[_complicated_page]

tests/benchmarks/test_evaluate.py

46.3 ms46.2 ms

test_evaluate_page[_stateful_page]

tests/benchmarks/test_evaluate.py

6.5 ms6.5 ms

test_compile_stateful[_complicated_page]

tests/benchmarks/test_compilation.py

595.4 µs595.3 µs

test_compile_page[_complicated_page]

tests/benchmarks/test_compilation.py

88.3 ms88.3 ms

test_get_all_imports[_complicated_page]

tests/benchmarks/test_compilation.py

-1%

22.5 ms22.6 ms

Commits

Click on a commit to change the comparison range

Base

main

3617ee4

-1.02%

Do a full re-hydrate on reconnect It turns out that just rehydrating and not also re-running the on_load handlers can leave applications in a bad state; particularly when their background tasks exiting are predicated on the `sid`, that will change on reconnect, but without an on_load, no mechanism is there to restart the tasks.

ef179a4

1 day ago

by masenf

+1.2%

Merge remote-tracking branch 'origin/main' into masenf/full-rehydrate

f30cfbc

1 day ago

by masenf

Home Terms Privacy Docs