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
I did a composer update recently which caused the version of Silex to update to 2.3. This resulted in my tests failing due to always returning 404 even though they always returned the correct body and X-Status-Code: 200.
Some debugging output from strace for a found match:
Hello,
I did a composer update recently which caused the version of Silex to update to 2.3. This resulted in my tests failing due to always returning 404 even though they always returned the correct body and X-Status-Code: 200.
Some debugging output from strace for a found match:
sendto(4, "HTTP/1.1 404 Not Found\r\nHost: localhost:8181\r\nDate: Wed, 02 May 2018 23:33:55 +0000\r\nConnection: close\r\nX-Powered-By: PHP/7.2.4\r\nSet-Cookie: XDEBUG_SESSION=10818; expires=Thu, 03-May-2018 00:33:55 GMT; Max-Age=3600; path=/\r\nCache-Control: no-cache, private\r\nDate: Wed, 02 May 2018 23:28:09 GMT\r\nX-Status-Code: 200\r\nContent-Type: text/html; charset=UTF-8\r\n\r\n", 357, 0, NULL, 0) = 357
My temporary fix was to lock silex in composer to 2.2.2: "silex/silex": "2.2.2",
The text was updated successfully, but these errors were encountered: