dirkmc
dirkmc
That makes sense, I wonder why they did that in aegir
Wow you found my [one and only](https://stackoverflow.com/questions/30082255/get-current-stack-trace-of-running-node-js-from-outside/30418818#30418818) stackoverflow question ever :) Fortunately it seems like there are tools to help out with this issue nowadays: https://stackoverflow.com/questions/10167477/how-to-debug-node-js-causing-100-cpu-usage
@pgte do you know if all future discovery transports will repeatedly fire discovery events for the same peer like WebsocketStar does? If so then we can rely on that mechanism...
Ok I guess we can make it configurable. It would be nice if the transport itself could report whether it has a heartbeat.
It sounds like maybe the greenscript plugin would be better for your needs?
I haven't looked at it for a while, you'd need to check the documentation to see if it's possible. Press is designed to be as simple as possible; at present...
Yeah I see what you're saying, let me think about the best solution to that problem
Actually have you tried adding the files using #{press.single-script 'file.js' /}? You may find that it's actually faster than having the files aggregated into groups, because the browser will download...
Ok great. The idea with press was to try to make it as simple as possible, with nothing for the user to really think about, just change the tag name...
Cool, let me know what you find