golang-application

I have two setups, in one the -parallel option works just fine in vscode - it generates parallel test cases as it should. In the other it doesn't do anything (not reporting errors in custom flags is a problem in the vscode go plugin, which is not the issue here).

Both were installed with go get -u github.com/cweill/gotests/... when in the $HOME directory within 15 minutes of each other.

One can use WithSyncNotifiers() and if careful to unregister/register to avoid a loop; you can process the new value but it would be simpler to have an api that returns the value instead

(use case: trim white spaces for instance on a dynstring or other transformations)

could also simplify how loglevel is done

Create Gitlab Push/Pull Mirrors

I have a need to recreate a lot of repositories with pull mirroring. This tool has all the other pieces I need except this one feature.

Propose a Solution

Using `glab repo mirror --direction=pull --src="ssh://git@gitlab.example.com:2222/namespace/project.git" --auth=ssh --allow-divergence --protected-branches-only my-new-namespace/my-new-project-na

In the current version, only the Handshake is used at the start of the connection. If the client does not send a message for a long time, the session will not be closed automatically. Will future versions do this session logic maintenance? For example, Netty can set the session to be automatically closed if the client does not send messages for a long time .

We should have a group support to handle permissions access from a LDAP, SSO, ...

allowed_resolvers_groups on templates for example.
admin_groups on configuration for example.

Describe the bug

Right now the deployment yaml (from the helm chart) has the same liveness and readiness probe:

          readinessProbe:
            httpGet:
              path: /config
              port: http
            initialDelaySeconds: 1
            periodSeconds: 3
          livenessProbe:
            httpGet:
              path: /config
              port: ht

Context

Right now the tool Killgrave is using for differents companies and users, but the documentation on the repository is very poor with a very little examples. We need to improve that point to bring closer this amazing tool to more people.

Proposed implementation

The idea will be to create a doc/ directory, with an index on the main README.md listing all the features that `K