I forgot to mention something!

In the first script pressing a key (any key) causes PHP to shut down properly. 
Here's what it looks like:

My console | strace console
           | (....)
           | rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
           | read(0, 0x8b825f8, 8192)      = ? ERESTARTSYS (To be restarted)
  ^C ---------------^
           | --- SIGINT (Interrupt) @ 0 (0) ---
     I     | sigreturn()                   = ? (mask now [])
  pressed  | read(0, "d", 8192)            = 1
    "d" -------------^
           | rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
   ! -->   | write(1, "X\n", 2)            = 2
           | rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], ~[KILL STOP RTMIN RT_1], 
8) = 0
           | rt_sigprocmask(SIG_SETMASK, ~[KILL STOP RTMIN RT_1], NULL, 8) = 0
           | close(2)                      = 0
My console | strace console
           | (....)

=======
 NOTE:
=======
If fgetc(STDIN) does not return immediately after a single character - it 
doesn't on my system, it waits for a newline - you might need to run "stty 
cbreak". When you're done run "stty -cbreak" if you want to switch whatever 
cbreak does back off, or just close the terminal.

i336

Is this still an issue with any of the actively supported PHP
versions[1]?

[1] <https://www.php.net/supported-versions.php>

Wow, I completely forgot about posting this. Thanks for following up.

Unfortunately it does still seem to be hanging around.

$ php --version
PHP 8.0.7 (cli) (built: Jun  4 2021 23:17:30) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.7, Copyright (c) Zend Technologies
    with Zend OPcache v8.0.7, Copyright (c), by Zend Technologies

(This is from deb.sury.org. I'm on Debian now.)

$ php -r "declare(ticks = 1); function quit() { print \"X\\n\"; die; } pcntl_signal(SIGINT, \"quit\"); fgetc(STDIN);"
^C^C^C^C^C^C^\Quit
$ _

Continuous ^C^C^C still simply retries forever:

 PHP tty  | strace tty
          |  ...
          |  rt_sigprocmask(SIG_UNBLOCK, [INT], NULL, 8) = 0
          |  read(0, 0x7fd24947f000, 8192)           = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
  ^C ---------------^
          |  --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
          |  rt_sigreturn({mask=[]})                 = 0
          |  read(0, 0x7fd24947f000, 8192)           = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
  ^C ---------------^
          |  --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
          |  rt_sigreturn({mask=[]})                 = 0
          |  read(0, 0x7fd24947f000, 8192)           = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
  ^C ---------------^
          |  --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
          |  rt_sigreturn({mask=[]})                 = 0
          |  read(0, "x\n", 8192)                    = 2
  'x' + ------------^
 <Return> | rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
 Exit->   | write(1, "X\n", 2)                      = 2
          | rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], ~[KILL STOP RTMIN RT_1], 8) = 0
          | rt_sigprocmask(SIG_SETMASK, ~[KILL STOP RTMIN RT_1], NULL, 8) = 0
          | rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
          | close(2)                                = 0
          | close(1)                                = 0
          | close(0)                                = 0
          | munmap(..., ...)                        = 0
          | ...

(NB, the note about `stty cbreak` at the end of the 2nd comment is somewhat orthogonal to this bug; inputting any text then pressing Return IMO suffices to demonstrate that normal input is consumed correctly.)

Setting restart_signals to false still consumes one ^C before responding correctly to the second:

$ strace -o /dev/pts/26 php -r "declare(ticks = 1); function quit() { print \"X\\n\"; die; } pcntl_signal(SIGINT, \"quit\", 0); fgetc(STDIN);"
^C^CX

 PHP tty  | strace tty
          | rt_sigprocmask(SIG_UNBLOCK, [INT], NULL, 8) = 0
          | read(0, 0x7f66fb47e000, 8192)           = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
 ^C 1 -------------^
          | --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
          | rt_sigreturn({mask=[]})                 = -1 EINTR (Interrupted system call)
          | read(0, 0x7f66fb47e000, 8192)           = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
 ^C 2 -------------^
          | --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
          | rt_sigreturn({mask=[]})                 = -1 EINTR (Interrupted system call)
          | rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
 Exit->   | write(1, "X\n", 2)                      = 2
          | rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], ~[KILL STOP RTMIN RT_1], 8) = 0
          | rt_sigprocmask(SIG_SETMASK, ~[KILL STOP RTMIN RT_1], NULL, 8) = 0
          | rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
          | close(2)                                = 0
          | close(1)                                = 0
          | close(0)                                = 0
          | munmap(0x7f66f7cb7000, 29808)           = 0
          | munmap(0x7f66f7cbf000, 16592)           = 0

Yeah, sorry, very long time to respond.

Anyhow, this can't work, because you're using ticks as signal
handler, and there is no tick executed while fgets() waits for
input.  Did you try with

    pcntl_async_signals(true)

That may work, but according to a comment on bug #49340, it does
not.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.

Yep... adding pcntl_async_signals(true) sadly doesn't do anything.

And wow, that other bug is from 2009 :)

I can only concur with the comment from sjoerd@ 12 years ago, "It would certainly be desirable to be able to interrupt a blocking read by doing Ctrl-C."

This is a bit of a sad language design oversight. Getting huffy about it won't do anything, but maybe empathizing with the complexity of the situation will make it feel less impossible to fix :) (...eventually™.)

Thanks again for following up. I look forward to the day PHP has a sane/simple set of APIs for making CLIs that get of the user's (and developer's) way.

Testing 1 2 3...

I got the error "You aren't allowed to change a bug to that state." while trying to submit the previous comment and a state change to "Re-Opened". I'd like to leave it at "Open", but I can only set it to "Assigned". That at least changes it from "Closed", which isn't what I want.