Fork me on GitHub
#lein-figwheel
<
2017-10-03
>
bhauman00:10:22

@jeaye this probably happens inside the websocket client server implementation, messages are queued up because it is an open "connection" active or not

jeaye02:10:10

@bhauman Ah, so this is likely more a re-natal issue than lein-figwheel, if I understand correctly?

bhauman02:10:48

in a way its an issue of the underlying transport layer

bhauman02:10:43

the websocket server is going to queue the messages until they are recieved

bhauman02:10:31

which is good behavior, even in this case because it ensures that all the files that you have edited are reloaded in the order that you edited them

bhauman02:10:32

the best solution here is really to prevent the device from sleeping via settings, unless of course you are working on a feature that depends on sleeping, etc.

jeaye04:10:27

Oh, I see.

jeaye04:10:52

Well, it's good to know; thanks for the info, @bhauman. I'd like these devices to sleep most of the time, so managing that setting is more likely going to cause some annoyance, so I think I'll continue as I have been.

jeaye04:10:28

Thinking about it at a high level, it seems like it'd be feasible to read all available commands from the socket and dedupe them, so double, triple, etc reloads don't happen. I know almost nothing about the implementation details of figwheel though.