View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001533XdebugStep Debuggingpublic2018-03-07 19:472021-04-14 16:05
Reporterdwilks Assigned Toderick  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionwon't fix 
Product Version2.6.0 
Summary0001533: Add ability to override xdebug.remote_timeout per request
Description

We'd like to use xdebug.remote_autostart=1 and xdebug.remote_connect_back=1 to simplify life for our developers. Unfortunately sometimes our overseas developers with high latency need to debug against US servers which would require a high xdebug.remote_timeout setting. This, unfortunately, would negatively impact non-debugging users like QA and PM.

What would be greats is the ability to override for xdebug.remote_timeout per request using something like the xdebug cookie in the request payload. Then the only time the cookie would be necessary is for those few times when we specifically need to support high latency.

  • Debugging locally wouldn't need a cookie anymore
  • Non-debugging requests wouldn't be severely impacted
  • Remote debuggers could override the timeout with their cookie

Thanks for your consideration

TagsNo tags attached.
Operating System
PHP Version7.2.0-7.2.4

Activities

derick

2018-10-18 23:45

administrator   ~0004704

I can change this, but I am wondering why you think it would negatively
impact non-debugger users to have a high latency. A well configured TCP/IP stack
should normally instantly return if there is no bound socket to listen. Are you
actively seeing this problem with high latency configured?

dwilks

2018-10-19 00:50

reporter   ~0004707

Yes. Our (US) remote teams (India/Romania) have been forced to continue to use the debug proxy configuration due to the latency of the network. We can't set remote_timeout too much higher or remote QA (which will never have debuggers) end up complaining about performance.

derick

2019-01-23 20:39

administrator   ~0004848

OK. I need to have a good think about this, because I think it would be wise if there would be a way to specify a maximum timeout in order to prevent resource starvation (we don't want people on the internet to be able to set a timeout of 900000000 ms for example).

derick

2021-03-17 09:29

administrator   ~0005751

Is this issue still relevant to you?

derick

2021-04-14 16:05

administrator   ~0005833

Closing this, as it is missing requested feedback.

Issue History

Date Modified Username Field Change
2018-03-07 19:47 dwilks New Issue
2018-10-18 23:45 derick Note Added: 0004704
2018-10-18 23:45 derick Assigned To => derick
2018-10-18 23:45 derick Status new => feedback
2018-10-19 00:50 dwilks Note Added: 0004707
2018-10-19 00:50 dwilks Status feedback => assigned
2019-01-23 20:39 derick Note Added: 0004848
2019-01-23 20:39 derick Status assigned => acknowledged
2020-03-12 16:23 derick Severity minor => feature
2020-03-12 16:27 derick Category Feature/Change request => Remote Debugging
2020-03-12 16:33 derick Category Remote Debugging => Step Debugging
2021-03-17 09:29 derick Status acknowledged => feedback
2021-03-17 09:29 derick Note Added: 0005751
2021-04-14 16:05 derick Status feedback => closed
2021-04-14 16:05 derick Resolution open => won't fix
2021-04-14 16:05 derick Note Added: 0005833