Daniel Neal

@Koura How far did you get with this?

I'm seeing this same problem. Specifically for me, I had some irrelevant dispatch-laters which were starting to bleed in to subsequent tests. I'm working around it with the following horror...

@mike-thompson-day8 definitely something like that. Would clearing re-frame's queue clear up the `dispatch-laters` though? https://github.com/Day8/re-frame/blob/cac2c7a02e6680f4bf43d9b3d3cf72a2a39a3209/src/re_frame/fx.cljc#L88-L94 Looks like it boils down to`js/setTimeout`, I couldn't make out if there is a reframe...

@mike-thompson-day8 Yes that sounds right! A stub of dispatch later (and any user defined fx that might leak via timeouts) would handle the slow bleed, and clearing the event queue...

@mike-thompson-day8 I'll go and do (2) right now - what should I do for (1) to call to clear the reframe event queue? Is that a change to re-frame-test or...

Thanks for the tip! It also comes up when I use a debugger - the debugger highlights the face, but the prism-chosen face wins I tried to get ChatGPT to...

> a separate feature called `mindstream-load-recent-session` which simply lists all recent sessions by name, and maps them under the hood to their absolute paths before loading them. Would this mean...

Thanks for the tip - I had been wondering about whether there was something in the settings that could help and this might do just the trick, thank you!