0001533: Add ability to override xdebug.remote_timeout per request

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001533

Xdebug

Feature/Change request

public

2018-03-07 19:47

2018-10-19 01:50

Reporter

dwilks

Assigned To

derick

Priority

normal

Severity

minor

Reproducibility

N/A

Status

assigned

Resolution

open

Platform

OS Version

Product Version

2.6.0

Target Version

Fixed in Version

Summary

0001533: 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

Tags

No tags attached.

Operating System

PHP Version

7.2.0-7.2.4

Attached Files

Relationships

Notes
(0004704) derick (administrator) 2018-10-19 00:45	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?

(0004707) dwilks (reporter) 2018-10-19 01:50	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.

Issue History
Date Modified	Username	Field	Change
2018-03-07 19:47	dwilks	New Issue
2018-10-19 00:45	derick	Note Added: 0004704
2018-10-19 00:45	derick	Assigned To	=> derick
2018-10-19 00:45	derick	Status	new => feedback
2018-10-19 01:50	dwilks	Note Added: 0004707
2018-10-19 01:50	dwilks	Status	feedback => assigned