Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

BUG: Cannot view a specific issue #579

Closed
UltCombo opened this issue Feb 18, 2016 · 1 comment
Closed

BUG: Cannot view a specific issue #579

UltCombo opened this issue Feb 18, 2016 · 1 comment
Labels

Comments

@UltCombo
Copy link

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.

@UltCombo
Copy link
Author

Here's the GitHub staff's reply:

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.

targos referenced this issue in nodejs/node Aug 2, 2016
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 <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants