* Documentation for the FPM status page and fpm_get_status()
* FPM status page: Update date/time format documentation
* FPM status page: Add information on openmetrics format (PHP 8.1+)
* Fix fpm_get_status referencing file name
* Update FPM status page documentation
* Move FPM status configuration to section
* Improve FPM Status Page formatting and move it under Observability
* Improve FPM status CS
Co-authored-by: AllenJB <github@allenjb.me.uk>
The definition of `search_value` in "Parameters" is a bit ambiguous. "these values" _could_ be interpreted to mean that if an array is passed as the `$search_value`, keys of elements of `$search_value` that match _any_ of those `$array` elements will be returned.
Note, the "Description" section does not have this ambiguity as it states "that value" instead of "those values".
Closes GH-1429.
Length parameter to substr() behaves differently for PHP8+. It recognizes null as if no value was provided at all. Updated the documentation to reflect this.
Co-authored-by: Christoph M. Becker <cmbecker69@gmx.de>
Closes GH-1219.
* Fix argument type in EventBufferEvent::setCallback() method and make it mixed instead of string.
* Add missed argument to signature of EventBufferEvent::__construct()
Closes GH-1384.
This patch clarifies the usage of the four JIT tunable options -
jit_hot_{loop,func,return,side_exit} - in PHP manual which end users
should be aware of before they start to tune these options.
1. Valid value range
2. Default value will be used in case beyond valid range
3. Special case of zero value
The patch was verified on my machine with phd local website.
Signed-off-by: Su, Tao <tao.su@intel.com>
Closes GH-1350.
As a new bird to PHP interpreter, I tried to set jit_bisect_limit
with jit=tracing in order to debug/probe PHP JIT feature, but
failed to hit my breakpoint and hence got confused.
I found that jit_bisect_limit only works under special JIT trigger
mode like 0: on script load, or 1: on first execution, after heavily
reading source code and trial-and-error experiments.
So, I would like to clarify the usage in PHP manual.
Hopefully, this can save time cost and reduce confusion of new PHP
interpreter developers.
The patch is verified on my local machine with phd build and the
web content and link looks good.
Signed-off-by: Su, Tao <tao.su@intel.com>
Co-authored-by: Christoph M. Becker <cmbecker69@gmx.de>
Closes GH-1337.
These classes are already documented elsewhere. toPHP() is rarely used directly and the types themselves are uncommon, so there is little need to call them out here.
