Marcel

I had the same issue running the container on a qnap nas. After clearing the cache as described in the readme, this error seems to have gone at the moment...

It seems that clearing the cache once doesn't fix it permanently. Since 3 days it is again "unable to connect to destination", just cleared the cache again now and will...

No not really, "unable to connect" reappears after some days again. The weird thing is, right at the moment it says "Last Backup 4.8 hours ago" and the error has...

so far it runs smoothly with the updated image and the latest crashplan version, I will monitor it for the next days but anyways i think this issue isn't related...

I guess you are missing the `/project` part in the target, for me it works like this: ``` docker run -v $(PWD)/openapi.yml:/project/openapi.yml wework/speccy lint openapi.yml ```

I think i got a similar problem regarding a test for a StreamedResponse: working test with symfony 6.0 ``` ob_start(); $client->request(Request::METHOD_GET, 'myTestUrl'); $content = \ob_get_clean(); self::assertEquals('foo', $content); ``` What (know)...

> I'm not sure if we need the new `getUserAgent()` function because we store defaults in `js/defaults.js`, so AFAIK would be the normal way to add the entry > >...

I have the same issue as described. I guess it is related to containers being recreated/updated/restarted with updated container images - either by re-pulling the image manually or automatically e.g....

In general neither `git` nor `mysql`/`mysqldump` is installed by default in the docker kimai image. A temporary workaround is to install those packages within the container via `apt install git...

Yes i think that would be a good idea to have a minimal board, that just contains the transmit and receive circuit, protection , the optoisolators and pin connectors to...