Sem Schilder comments

Results 112 comments of


                                            Sem Schilder

Panic with error "not implemented: No support to dereference ......"

I'm also experiencing this! We have the following markup ```yaml # openapi.yml paths: /api/v1/health: $ref: 'components/internal.yml#/endpoints/getHealth' ``` This references a the file `components/internal.yml` relative to `openapi.yml` file location. It has...

Panic with error "not implemented: No support to dereference ......"

We where already using speccy to combine it into json format. However, when it's combined into a single yaml file I'm still getting these warnings ``` thread 'main' panicked at...

Add significant performance improvements for composer v2

Possible todo: add test for composer v1 and V2 package endpoint differences. Also test this with an invalid user agent. This will fix the missing coverage

[bitnami/php-fpm] Is there a reason to run php-fpm docker image as root user?

We were using the `php-fpm:8.0` image for some time now, instead of our custom build php binary and images. This worked fine on our Kubernetes cluster, where all production resources...

[bitnami/php-fpm] Is there a reason to run php-fpm docker image as root user?

@fmulero good one, we were using `bitnami/php-fpm:8.0` as base image. Which "broke" due to the permissions thingy. I can't view the last build logs because of a botched GitLab upgrade....

[bitnami/php-fpm] Is there a reason to run php-fpm docker image as root user?

I will check on Monday if this is still an issue

[bitnami/php-fpm] Is there a reason to run php-fpm docker image as root user?

Behaviour for `bitnami/php-fpm:8.0` is still broken. Specifically using `bitnami/php-fpm:8.0.19` does work as "before". Can we mark this issue so it wont become stale every x days?

[bitnami/php-fpm] Is there a reason to run php-fpm docker image as root user?

please dont.

Support using different HTTP Clients through PSR-17 and PSR-18

@ramsey I see that there are a couple of PRs linked to this issue, but they are closed. Due to the long discussions on them, I can't immediately figure out...

How to add extra data to the existing login_check route

After some more debugging, it seems the event is not fired for some reason. I currently have 2 event listers. One on `lexik_jwt_authentication.on_jwt_created` which does work as I have custom...