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
The same QUERY that results in an error in DEV MODE does not produce errors in prod modes.
When the cache is cleared, the first EXECUTE QUERY runs successfully and returns the correct result. However, subsequent executions of the same QUERY, when the cache is present, result in an ERROR.
I am considering whether the issue could be related to the use of Symfony cache or other potential causes.
I think the cache in GlobControllerQueryProvider is causing it to not find the QUERY's controller, which leads to this ERROR.
The text was updated successfully, but these errors were encountered:
I've made sure that cache is saved by setting a directory: $cache = new Psr16Cache(new FilesystemAdapter(directory: '/app/cache/dev'));, and ran it with docker run -it --rm -v $PWD:/app -w /app chialab/php-dev:8.2 php devmode.php. Running it multiple times does generate cache, but always results in the same output.
Indeed, I had no issues when testing in the LINUX environment (php8.2). I discovered that this problem only occurs in the WINDOWS environment. I also tested the same thing on another WINDOWS computer and changed the cache directory. In the cache folder, there were cache files, but the output still showed the same error.
oojacoboo
changed the title
Errors regarding devMode and prodMode
Errors regarding devMode and prodMode on Windows OS
Mar 14, 2025
I've discovered that errors occur in DEV MODE while testing in a PHP8.1 environment. For reference, please check my repository: https://github.com/mathsgod/graphqlite-test.
The same QUERY that results in an error in DEV MODE does not produce errors in prod modes.
When the cache is cleared, the first EXECUTE QUERY runs successfully and returns the correct result. However, subsequent executions of the same QUERY, when the cache is present, result in an ERROR.
I am considering whether the issue could be related to the use of Symfony cache or other potential causes.
I think the cache in GlobControllerQueryProvider is causing it to not find the QUERY's controller, which leads to this ERROR.
The text was updated successfully, but these errors were encountered: