-
-
Notifications
You must be signed in to change notification settings - Fork 11
Drop fruitcake/laravel-cors. Segmentation fault (core dumped) #6
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
base: main
Are you sure you want to change the base?
Conversation
Thank you. I'll test it later. |
I've tested it locally. It doesn't work unfortunately. Still segmentation fault. May be you can advice what I should add here to the PR? |
@vogdb I'll probably need more info on the error that you are getting. I still had no time to check it. Do you have more info on the error message that you are getting? Sometimes Segmentation faults could be caused by external factors, like server miss config, broken PHP extensions, and many others. My suggestion to try to identify the cause is to check the error logs and to use xdebug. If you want/have more info to share about it, I'll be happy to give some insights about it. |
The only error in the log is:
I've tried every possible answer from https://stackoverflow.com/questions/56984159/composer-install-segmentation-fault. Didn't help. The full log:
|
Hi! According to https://github.com/fruitcake/laravel-cors the package is dropped in favor of Laravel's CORS. To be honest I haven't tested these changes. I just followed the "Steps to upgrade:" from
README.md
of fruitcake/laravel-cors. Feel free to adjust them accordingly.Currently I receive
Segmentation fault (core dumped)
after installing this plugin (Winter 1.2.1, PHP 8.1.2, Laravel 9.52). I hoped that dropping of fruitcake will help to overcome this problem.