Closed vincentjames501 closed 11 months ago
I am also facing the same issue. Also seems to prevent my integration tests (which integrant/halt the system when done) from finishing
Thanks for the report, I will try to find time to look.
What version of re-frame are you using, by the way?
In my project I am not specifying the re-frame version so I guess its whatever is used by re-graph by default. for 0.2.0
re-graph that seems to be 1.2.0
I am using re-graph 0.2.0
@rhishikeshj are you experiencing this while using run-test-sync? Or does it also happen in other places?
@oliyh no. this is a JVM test using a simple deftest
and the re-graph/destroy
comes from an ig/halt
which is called from the :once
fixture of the test once the test is completed
Pushed 0.2.1-SNAPSHOT
to clojars with an improvement to destroy, but as discussed it doesn't solve the problem, which I believe exists in the jvm implementation of re-frame.
When I call
(re-graph/destroy {})
after making a subscription on a websocket or if the websocket is closed due to external factors I get the following:In the case where the connection closed on the server it does not attempt to reconnect and resume the subscription.