June Han

> @junekhan could you please fix the conflict in the changelog and also document this new annotation? https://keda.sh/docs/2.13/concepts/scaling-deployments/ I've fixed the conflict and updated the document for v2.13.

I have no problem building this example from the latest master branch. Did you set up you project from the [CMAKEFILE](https://github.com/CrowCpp/Crow/blob/master/examples/CMakeLists.txt) ``` [build] Scanning dependencies of target example_websocket [build] [...

``` triggers: - type: rabbitmq metadata: queueName: queue hostFromEnv: RABBITMQ_URL mode: QueueLength value: "1" --- ``` @SpiritZhou Thanks for your reply. We configured the scaler as above. Increasing the `queueLength`...

```yaml --- apiVersion: keda.sh/v1alpha1 kind: ScaledJob metadata: name: worker spec: jobTargetRef: template: metadata: labels: app: worker spec: containers: - name: worker image: worker-image imagePullPolicy: Always resources: requests: memory: "4Gi" cpu:...

@JorTurFer Because these workers are long-running inherently, I preferred ScaledJob to ScaledObject naturally. [This section](https://keda.sh/docs/2.12/concepts/scaling-deployments/#long-running-executions) concerned me as pods can be terminated unexpectedly in terms of ScaledObject. Getting back to...

@JorTurFer You are correct. Thanks for the solution. I will try it out.

> Temporary solution is to install the webdriver manually for ubuntu: `sudo apt install chromium-driver` This doesn't work for me. I alternatively installed a full-sized chrome with `sudo apt install...

> Thank you! > > Can we add a test please to ensure we don't break this in the future? @thomaseizinger Sure thing! But frankly speaking, I'm a novice in...