Problem/Motivation

When using direnv to load the devShell, and used by multiple user accounts, you get warnings about being unable to write to /tmp/xdebug.log. This comes after enabling xdebug to support profiling.

Steps to reproduce

Proposed resolution

Refactor xdebug support to be off for drush, enabled for xdrush, and start with trigger in php-fpm.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

freelock created an issue. See original summary.

  • freelock committed 205b0184 on 1.0.x 
    Issue #3535937: XDebug profiling, and conflicts on /tmp/xdebug.log
freelock’s picture

freelock
Location Seattle
commented
Assigned: Unassigned » freelock
Status: Active » Needs review

Needs testing across multiple projects, scenarios.

freelock’s picture

freelock
Location Seattle
commented
Status: Needs review » Needs work

The pushed commit did work for profiling, but broke debugging. Pushing a new commit that turns off the xdebug.log and restores debugging -- profiling is not working with this now.

  • freelock committed c4c5af59 on 1.0.x 
    Issue #3535937: XDebug profiling, and conflicts on /tmp/xdebug.log
freelock’s picture

freelock
Location Seattle
commented
Status: Needs work » Fixed

The debug log option was removed.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.