You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, this objectively is not a fault of Safe but I am wondering if this could/should be solved on Safe's side.
The problem is, that when xdebug extension is enabled. The set_time_limit returns false even if it was successful. Safe\set_time_limit then converts this false into exception that crashes the application.
It is annoying when debugging and I run into this several times a week.
Maybe this weird edge case could be handled and the false from this function could be ignored when xdebug is enabled.
Obviously there is a workaround to temporarily comment out the Safe/set_time_limit calls or not use them at all.
The text was updated successfully, but these errors were encountered:
Hello, this objectively is not a fault of Safe but I am wondering if this could/should be solved on Safe's side.
The problem is, that when
xdebug
extension is enabled. Theset_time_limit
returns false even if it was successful.Safe\set_time_limit
then converts thisfalse
into exception that crashes the application.It is annoying when debugging and I run into this several times a week.
Maybe this weird edge case could be handled and the
false
from this function could be ignored whenxdebug
is enabled.Obviously there is a workaround to temporarily comment out the
Safe/set_time_limit
calls or not use them at all.The text was updated successfully, but these errors were encountered: