sabre framework response with error 500 with PHP 8.2

Question

sabre framework response with error 500 with PHP 8.2

Closed this issue a year ago · 13 comments

thelittleblackbird commented a year ago

hi,

Recently i found that i get several errors 500 from the sabre framework.

The problem seems to be linked (if it is not identic) to this:
sabre-io/Baikal#1154

coudl be possible to have a PHP downgrade until sabre fixs their codebase¿?

Answer 1 · 2023-10-20T20:24:10.000Z

I asked for a new release: sabre-io/dav#1493 because it seems that their latest commit on master fixes the issue

Answer 2 · 2023-10-21T07:41:16.000Z

Thanks, then let's wait to Sabre maintainer answer

Answer 3 · 2023-11-05T09:44:12.000Z

Hi again,

It seems sabre developers are not really reacting to anything. do you think it could be possible to downgrade the PHP version to 8.1?

I know this is not a good idea from the patching point of view, but the system is not really usable in the current state. and i wouldnt like to change the dockerfile myself, I tend to be as close as possible to the main source

regards

Answer 4 · 2023-11-08T22:57:34.000Z

Hi there,

4.5.0 is coming → sabre-io/dav#1497 🎉

Hopefully this will be available next week max so I can update the dependencies on Davis' side and make a release asap 🤞🏼

Thanks for your patience

Answer 5 · 2023-11-14T20:13:39.000Z

Just released https://github.com/tchapi/davis/releases/tag/v4.2.0 ✨

Answer 6 · 2023-11-16T11:21:39.000Z

thanks for your support

Answer 7 · 2023-11-16T14:14:59.000Z

dont want to ruin the current joy. But could it be possible that the sabre version is not update in the docker image?

i can still see a 4.4.0 in the compose.json from ghcr.io/tchapi/davis:v4.2.0 :)

Answer 8 · 2023-11-16T14:18:36.000Z

Just tested right now, it seems ok:

❯ docker run -it ghcr.io/tchapi/davis:v4.2.0 sh
/var/www/davis # cat composer.json | grep sabre
    "description": "A simple, fully translatable admin interface and frontend for sabre/dav based on Symfony",
        "sabre/dav": "^4.5.0",

Are you sure your container is updated to use the latest image?

Answer 9 · 2023-11-18T20:55:20.000Z

Hi @thelittleblackbird 👋🏼

Did you finally make it work?

Answer 10 · 2023-11-19T13:01:09.000Z

hi

not really, still faces some issues that i dont know how to tackle.

small and stupid question, is there any way to enable a verbose log from all the framworks?

Answer 11 · 2023-11-19T19:32:30.000Z

small and stupid question, is there any way to enable a verbose log from all the framworks?

You could set APP_ENV=dev in the environment to get more logs (in var/log/dev.log)

Answer 12 · 2023-11-27T19:40:52.000Z

now i get an exception witht the "dev" parameter

Answer 13 · 2023-11-27T20:29:16.000Z

Ah, yes, that's expected as you have a production container (that does not include the dev profiler that your app is trying to display here). So APP_ENV=dev in a production container is not really a good solution.

What are the remaining issues you are facing and trying to debug?