View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002092 | Xdebug | Step Debugging | public | 2022-05-11 16:36 | 2022-05-25 14:31 |
| Reporter | rkaiser | Assigned To | derick | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Platform | PHP 8.0.15 | OS | CentOS | OS Version | 7.7 |
| Product Version | 3.1.2 | ||||
| Summary | 0002092: Not able to suppress [Config] warnings regarding outdated settings | ||||
| Description | I have reviewed the comments in https://stackoverflow.com/questions/65162856/xdebug-step-debug-could-not-connect-to-debugging-client-tried-localhost900/65264131#65264131 but it appears that some of the comments may be inaccurate, so I am trying to understand how in practice to suppress these messages. Contrary to what @RyanNerd reported in that link, I confirmed that setting In our case, our workflow is similar to that described by @mxr576 in https://stackoverflow.com/a/65725090/1282424, where we have a shared XDebug configuration, where the 3.x configuration is loaded after the 2.x configuration. So we do want to suppress these warnings. Is this behavior expected? Shouldn't setting the xdebug.log_level=0 work to suppress these? | ||||
| Steps To Reproduce | Do any PHP CLI command, e.g.,
| ||||
| Tags | cli, php8.0 | ||||
| Operating System | CentOS | ||||
| PHP Version | 8.0.10-8.0.19 | ||||
|
|
This is indeed what I expected it to do. The |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-05-11 16:36 | rkaiser | New Issue | |
| 2022-05-11 16:36 | rkaiser | Tag Attached: cli | |
| 2022-05-11 16:36 | rkaiser | Tag Attached: php8.0 | |
| 2022-05-25 14:31 | derick | Assigned To | => derick |
| 2022-05-25 14:31 | derick | Status | new => resolved |
| 2022-05-25 14:31 | derick | Resolution | open => no change required |
| 2022-05-25 14:31 | derick | Note Added: 0006316 |