We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Good summary at https://matthewdf10.medium.com/how-to-enable-logging-on-every-aws-service-in-existence-circa-2021-5b9105b87c9 and https://docs.google.com/spreadsheets/d/1DBmCXX1irJvxdewa85p5nSsYEf3tpSKWBbwp700mbzs/edit#gid=0

Amazon Aurora
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html#cfn-rds-dbcluster-enablecloudwatchlogsexports

AWS AppSync

Hi,

It'd love to try out alloy_ci . We run almost everything in kubernetes (incl. gitlab runner) and I think it would be awesome if there was a template / manifests to deploy alloy on kubernetes.
This would make trying it out for evaluation purposes much easier.
Have no strong opinions on how a k8s example templates should be packaged but these are some options that come to my mind:

• simpl

Look into and create a POC of a public github action using rok8s-scripts

Bug report

Expected behaviour?
All projects should be included or excluded without any delay.

Actual behaviour?
All projects are included or excluded with a noticeable delay.

Steps to reproduce?

1. Add a feed with lots of projects (mine has ~140 projects)
2. Click the "exclude all" button

This is because it loops through all projects and triggers an include/exclude

fledge beta
Git error. Command: git log origin/dev..dev
fatal: ambiguous argument 'origin/dev..dev': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'

Please suggest something to fix this...

Look at creating a custom GitHub Action for config-lint.

Resources:
https://github.com/actions/toolkit
https://help.github.com/en/actions/building-actions/creating-a-docker-container-action

Question #32 made me think of linking to the failing test and line form the annotations. Given the commit sha, test file and line, the action could generate a link like this and add to the respective annotation:

https://github.com/EnricoMi/publish-unit-test-result-action/blob/de7f7f0c5f7694846ce69e3384f2e5a03253c141/test/test_publish.py#L35

Such a link gets nicely rendered by GitHub:

ht

If I add a cmd into a step and it fails, the resulting error message is not really indicative of the actual problem.

Here's the relevant logs from the container after a failed request: (Note the cmd: "pip99" "install" "-r" "requirements.txt" - probably failed with something like command not found: pip99). We should see the command not found: pip99 message more prominently than (or ent