Searched refs:message (Results 1 – 25 of 434) sorted by path
12345678910>>...18
/php-src/.github/workflows/ |
H A D | close-needs-feedback.yml | 24 …close-message: "No feedback was provided. The issue is being suspended because we assume that you …
|
H A D | close-stale-feature-requests.yml | 26 stale-issue-message: >-
|
H A D | close-stale-prs.yml | 26 …stale-pr-message: There has not been any recent activity in this PR. It will automatically be clos…
|
/php-src/ |
H A D | .travis.yml | 45 …- "%{repository}#%{build_number} (%{branch} - %{commit} : %{author}): %{message} - Change view : …
|
H A D | CONTRIBUTING.md | 130 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 D | README.md | 118 the commit message using `GH-NNNNNN`. Use `#NNNNNN` for tickets in the old
|
/php-src/Zend/tests/ |
H A D | 009.phpt | 26 set_error_handler(function ($severity, $message, $file, $line) { 27 throw new Exception($message);
|
H A D | 010.phpt | 25 set_error_handler(function ($severity, $message, $file, $line) { 26 throw new Exception($message);
|
H A D | ErrorException_getSeverity.phpt | 12 const EXCEPTION_PARAM_MSG = "string message param";
|
H A D | argument_restriction_001.phpt | 2 Bug #55719 (Argument restriction should come with a more specific error message)
|
H A D | argument_restriction_002.phpt | 2 Bug #55719 (Argument restriction should come with a more specific error message)
|
H A D | argument_restriction_003.phpt | 2 Bug #55719 (Argument restriction should come with a more specific error message)
|
H A D | argument_restriction_004.phpt | 2 Bug #55719 (Argument restriction should come with a more specific error message)
|
H A D | argument_restriction_005.phpt | 2 Bug #55719 (Argument restriction should come with a more specific error message)
|
H A D | array_offset.phpt | 2 Ensure "undefined offset" notice formats message correctly when undefined key is negative
|
H A D | bug39775.phpt | 2 Bug #39775 ("Indirect modification ..." message is not shown)
|
H A D | bug43344_1.phpt | 2 Bug #43344.1 (Wrong error message for undefined namespace constant)
|
H A D | bug43344_10.phpt | 2 Bug #43344.10 (Wrong error message for undefined namespace constant)
|
H A D | bug43344_11.phpt | 2 Bug #43344.11 (Wrong error message for undefined namespace constant)
|
H A D | bug43344_12.phpt | 2 Bug #43344.12 (Wrong error message for undefined namespace constant)
|
H A D | bug43344_13.phpt | 2 Bug #43344.13 (Wrong error message for undefined namespace constant)
|
H A D | bug43344_2.phpt | 2 Bug #43344.2 (Wrong error message for undefined namespace constant)
|
/php-src/Zend/tests/assert/ |
H A D | expect_008.phpt | 20 assert(true, "constant message"); 21 assert(($variable && $variable) || php_sapi_name(), new OdEar("constant message"));
|
/php-src/Zend/tests/attributes/ |
H A D | 009_doctrine_annotations_example.phpt | 40 * @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 D | 029_reflect_internal_symbols.phpt | 18 $rp = new ReflectionProperty('Exception', 'message');
|
Completed in 39 milliseconds
12345678910>>...18