-
The version of Karaf AET makes use of, is old.
There is also a problem with downloading karaf dependencies.
Please take a look at:
https://github.com/malaskowski/aet-docker/pull/17
and
https:…
-
Hey,
after a while with AET I came to a conclusion that it'd be great to have a _fail fast_ option.
Our test suite lasts for around 10 minutes (2 Karaf workers) and the goal is to keep it green…
-
Hey,
quite recently I encountered a bunch of AET issues. Unfortunately none of them was easy to troubleshoot and fix, mostly due to not enough feedback on client side. That's rather frustrating exp…
-
Thanks for detailed and clear steps for running AET instance using Helm.
Tried the steps mentioned in https://wttech.blog/blog/2021/running-aet-using-helm/
Getting below alerts in Docker Dashboard…
-
### Komga environment
- **OS**: Synology Nas DS1019+ DSM 6.2.3-25426 (latest one available)
- **Komga version**: v0.51.1-master
- [X] **I am running Komga with Docker**
- Docker image tag [e.g. …
-
Right now karaf is pre-provisioned with only based bundles and dependencies.
The AET bundles are installed afterwards.
Please kindly consider moving pre-provisioning or adding second pre-provision…
-
Deploying AET containers in a locked down environment without access to the internet can be a challange:
* upon AET start there's quite a few calls to Central Maven repo and that produces a lot of er…
-
# Steps to reproduce
* just run Swarm stack and make sure `configs` volume is not empty
# Current state
```
00:03:52.399 INFO [activator-1-thread-2] Binding bundle: [org.apache.karaf.webco…
-
**Describe the bug**
When building with vagrant up:
==> default: * ruby_block[karaf-config-guard] action run
==> default:
==> default: waiting for response code 401 from http://localhost:8181/…
-
**Describe the bug**
When using the accessibility collector in a suite, the entire codesniffer JS source file is written to logs for each accessibility collection. This happens only in the DEBUG log…
tkaik updated
5 years ago