Closed pitosalas closed 3 years ago
@pitosalas Much of the listen
code has been restructured in v3.3, so this may be fixed. Although I can't tell which part of the above involved the listen
gem, if any.
Any chance you can try listen v3.3.0.pre.2
and let us know if the problem persists?
I'm going to assume this has been fixed at least by v3.3.0. If the issue reappears, we can open a fresh ticket.
At least I think it's caused by listen: