Noorul Islam K M

When enabled, org mode buffer tangling becomes very slow

2

I have the following configuration ```elisp (use-package color-identifiers-mode :diminish color-identifiers-mode :init (add-hook 'after-init-hook 'global-color-identifiers-mode)) ``` With above configuration tangling functionality from org-mode is taking a lot of time

Question: multiple projects with multiple docker-compose files

11

I work on multiple projects with multiple compose files. project1 -> compose-p1-1.yaml, compose-p1-2.yaml project2 -> compose-p2-1.yaml, compose-p2-2.yaml Every time I need to run compose command I have to switch to...

### Expected behavior What should have happened? Should not have had any CVEs ### Actual behavior Found CVEs What actually happened? ### Steps to reproduce 1. trivy image --security-checks vuln...

Upgrade go modules to version which has CVE fixes

1

Fixes #1614

Bump docker_registry2 to fix #3989

3

The latest version of docker_registry2 has the fix for #3989.

Today, DB layer timeout is not configurable by the user. This makes it difficult for the user to upload bigger jars. DB API uses shared-timeout which is part of application...

Creating python context using PythonSessionContextFactory is failing

1

Here is the [traceback](https://pastebin.com/utUj69Cs) from jobserver log. It looks like we are creating multiple contexts with hive enabled.

When upload big jar the API times out. Document spray configuration parameters.

Switching contexts should fetch resources unconditionally, i.e. short-circuit poll schedule

1

For example, I have the following values set ```elisp (setq kubernetes-poll-frequency 3600 kubernetes-redraw-frequency 3600) ``` When I switch context, I see that screen is re-drawn with "Fetching..." message.

Today there is no support of scale command.