codedge

I am having the same problem on MacOS. My YAML file: ```yaml plugins: - serverless-offline service: abc app: abc org: codedge frameworkVersion: "3" provider: name: aws runtime: go1.x package: patterns:...

Sorry for the confusion. **1. Resolving the `reached timeout`** At first I got a `reached timeout` error. This error was directly visible inside the logs of Bramble. I figured out,...

.. and I can confirm, that changing the [`WriteTimeout`](https://github.com/movio/bramble/blob/main/main.go#L61) to f. ex. `60` ```golang func runHandler(ctx context.Context, wg *sync.WaitGroup, name, addr string, handler http.Handler) { srv := &http.Server{ Addr: addr,...

Is there a release planned to include the new configuration?

This has been fixed in release 4.x, so this PR can be closed.

The only thing that does work is ``` services: php: build: . ports: - "9029:80" webdriver: image: instrumentisto/geckodriver:latest command: - --binary=/opt/firefox/firefox - --host=0.0.0.0 - --port=80 - --allow-hosts=localhost,webdriver - --log=debug ports:...

I think it would better to run `docker-compose up -d`. That uses [docker compose](https://docs.docker.com/compose/) for orchestrating the container.

Here are my details: I have a custom resolver, that is filled with a custom DTO. Inside the DTO a run a validation of a property (`GreaterThan(value: 0)`). Before the...

> We all agree that the resolver shouldn't be hit if validation fails? yes

> What I've found in the meantime (maybe this is obvious to me, but it wasn't for me): setting `event_listeners_backward_compatibility_layer: true` helps to overcome this problem. But this is not...