You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
I've noticed that this issue is no longer accessible: floatdrop/gulp-watch#206
It is giving a 404, although I'm sure this issue exists (or, used to exist).
You can see that this issue is referenced from floatdrop/gulp-watch#209. If you hover the link to #206 you will get an "Issue title is private" tooltip. If you start writing a comment in that thread (or any other thread in the floatdrop/gulp-watch repository) and type "#206" the issue name is correctly displayed.
As far as I can tell, private issues are not yet implemented so I'm filing this as a bug.
The text was updated successfully, but these errors were encountered:
Thanks for reaching out! Unfortunately, the account responsible for opening the issue in question has been flagged for violating GitHub's Terms of Service. As a result, their work has been hidden from public view.
I'm sorry for any confusion this might have caused and please do let us know if you have any questions.
Set the `SIGUSR2` handler before spawning the child process to make sure
the signal is always handled.
Fixes: #7767
PR-URL: #7854
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
I've noticed that this issue is no longer accessible: floatdrop/gulp-watch#206
It is giving a 404, although I'm sure this issue exists (or, used to exist).
You can see that this issue is referenced from floatdrop/gulp-watch#209. If you hover the link to
#206
you will get an "Issue title is private" tooltip. If you start writing a comment in that thread (or any other thread in the floatdrop/gulp-watch repository) and type "#206
" the issue name is correctly displayed.As far as I can tell, private issues are not yet implemented so I'm filing this as a bug.
The text was updated successfully, but these errors were encountered: