-
-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation violation Caddy module #944
Comments
I did a bit of research, and I'm not sure this module is compatible with frankenphp. The souin cache is meant for reverse proxies, and there isn't any reverse proxy in frankenphp. |
+1 So, what is the cache option with a I was following this doc: https://api-platform.com/docs/core/performance/#built-in-caddy-http-cache But I got the same seg violations after getting it to build at all. It turns out the Caddy Cache-Handler is the culprit. |
Souin can be used with FrankenPHP/API Platform. This issue looks related to Souin, not to FrankenPHP. Maybe @darkweak knows what's going on. Otherwise I'll try to take a look when I'll have some time. |
Hello there.
Souin is a caddy module, so, it should be compatible with frankenphp. I don't see any Souin related content in the stacktrace/logs you posted @g-ra. TBH I didn't try the stack frankenphp + souin + api invalidation. Can you give me more details about the error above? Does it occur on the first request or after a while? |
@darkweak the error is repeated with each request, but it allows, for example, to execute basic cache reset commands in the console php bin/console ca:clear |
here is repo for demonstration error use not ARM proccessor docker compose up -d --build just try http://localhost/docs open php logs |
Thanks! Would you mind explaining what you've done for next readers? |
The storage refactoring solved that (so actually only available on the master branch in the Souin repository).
That's not verified but that's the only thing related to souin and the fact switching to the refactored storages that only embed needed backend storages solved this, so this seems to confirm my idea. For those who want to use the working version (while awaiting the next release), you have to use the following modules:
and read the documentation here (https://docs.souin.io/docs/middlewares/caddy/#storages) to learn more about the storages. |
@darkweak thanks! For the record, FrankenPHP also uses otter internally (which plays well with cgo). Maybe there was a version conflict or something? |
What happened?
i got errors from default Dockerfile from docs perfomance cache-handler
stacktrace.txt
here is my Dockerfile
Build Type
Docker (Debian Bookworm)
Worker Mode
Yes
Operating System
macOS
CPU Architecture
x86_64
PHP configuration
Relevant log output
External changes
The text was updated successfully, but these errors were encountered: