I had gulp.watch setup to run a task, but it was not running, despite the change being picked up by the watcher. After tracing my way down through gulp, I found line 213 in orchestrator/index.js and realized my task (which runs at startup and on change) was still running.
gulp's output can be fairly noisy, and it was easy for me to miss the lack of a "[task] finished" line. The silent failure was a bit frustrating, and I think it might be helpful to print a warning on that line that the task being attempted is already running.
Happy to submit a PR, but I didn't spend too long digging through the source, so I wasn't sure if my fix would be a good approach. Figured I'd get feedback first.
I had gulp.watch setup to run a task, but it was not running, despite the change being picked up by the watcher. After tracing my way down through gulp, I found line 213 in
orchestrator/index.jsand realized my task (which runs at startup and on change) was still running.gulp's output can be fairly noisy, and it was easy for me to miss the lack of a "[task] finished" line. The silent failure was a bit frustrating, and I think it might be helpful to print a warning on that line that the task being attempted is already running.
Happy to submit a PR, but I didn't spend too long digging through the source, so I wasn't sure if my fix would be a good approach. Figured I'd get feedback first.