Home
last modified time | relevance | path

Searched refs:message (Results 1 – 25 of 434) sorted by path

12345678910>>...18

/php-src/.github/workflows/
H A Dclose-needs-feedback.yml24 …close-message: "No feedback was provided. The issue is being suspended because we assume that you …
H A Dclose-stale-feature-requests.yml26 stale-issue-message: >-
H A Dclose-stale-prs.yml26 …stale-pr-message: There has not been any recent activity in this PR. It will automatically be clos…
/php-src/
H A D.travis.yml45 …- "%{repository}#%{build_number} (%{branch} - %{commit} : %{author}): %{message} - Change view : …
H A DCONTRIBUTING.md130 should be credited, the `Co-authored-by` tag in the commit message may be used.
394 nice commit message for each one. See example below.
396 4. Do write your commit message in such a way that it makes sense even without
398 know what was modified. Definitely include the function name in the message
422 If you fix some bugs, you should note the bug ID numbers in your commit message.
H A DREADME.md118 the commit message using `GH-NNNNNN`. Use `#NNNNNN` for tickets in the old
/php-src/Zend/tests/
H A D009.phpt26 set_error_handler(function ($severity, $message, $file, $line) {
27 throw new Exception($message);
H A D010.phpt25 set_error_handler(function ($severity, $message, $file, $line) {
26 throw new Exception($message);
H A DErrorException_getSeverity.phpt12 const EXCEPTION_PARAM_MSG = "string message param";
H A Dargument_restriction_001.phpt2 Bug #55719 (Argument restriction should come with a more specific error message)
H A Dargument_restriction_002.phpt2 Bug #55719 (Argument restriction should come with a more specific error message)
H A Dargument_restriction_003.phpt2 Bug #55719 (Argument restriction should come with a more specific error message)
H A Dargument_restriction_004.phpt2 Bug #55719 (Argument restriction should come with a more specific error message)
H A Dargument_restriction_005.phpt2 Bug #55719 (Argument restriction should come with a more specific error message)
H A Darray_offset.phpt2 Ensure "undefined offset" notice formats message correctly when undefined key is negative
H A Dbug39775.phpt2 Bug #39775 ("Indirect modification ..." message is not shown)
H A Dbug43344_1.phpt2 Bug #43344.1 (Wrong error message for undefined namespace constant)
H A Dbug43344_10.phpt2 Bug #43344.10 (Wrong error message for undefined namespace constant)
H A Dbug43344_11.phpt2 Bug #43344.11 (Wrong error message for undefined namespace constant)
H A Dbug43344_12.phpt2 Bug #43344.12 (Wrong error message for undefined namespace constant)
H A Dbug43344_13.phpt2 Bug #43344.13 (Wrong error message for undefined namespace constant)
H A Dbug43344_2.phpt2 Bug #43344.2 (Wrong error message for undefined namespace constant)
/php-src/Zend/tests/assert/
H A Dexpect_008.phpt20 assert(true, "constant message");
21 assert(($variable && $variable) || php_sapi_name(), new OdEar("constant message"));
/php-src/Zend/tests/attributes/
H A D009_doctrine_annotations_example.phpt40 * @Assert\Email(message="The email '{{ value }}' is not a valid email.")
43 #[Assert\Email(array("message" => "The email '{{ value }}' is not a valid email."))]
115 ["message"]=>
H A D029_reflect_internal_symbols.phpt18 $rp = new ReflectionProperty('Exception', 'message');

Completed in 39 milliseconds

12345678910>>...18