Feature type

Quality of life

Describe the feature

I would like to be able to use relative paths in the launcher settings file to point to x32dbg.exe and x64dbg.exe respectively. I've already tried editing the file manually and assuming my implementation (.\/\//) isn't wrong, the launcher seemingly refuses the use of relative paths.

Context: https://caddy.community/t/including-files-scripts/15050/4

Right now, the templates module is inflexible in that only functions the functions registered by Caddy itself are available.

A good refactor would be to make it possible to pass an optional array of modules in the http.handlers.templates.functions.* namespace which get invoked at Provision() time to register additional

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

The ERC721Enumerable must throw according to the specification.

My 2GHz Ryzen 7 laptop needs SEVERAL minutes to compile this 2.2MB autogenerated file. the reason is. because its full of spaguetti that the compiler tries to optimise without much luck because its based on binary logic operands and zillions of consecutive conditionals that don't even try to switch/case. So this is 45KLOC of code that almost nobody uses and will live better in extras.

Sorry for not following the template. It's a straightforward question.

By enabling "WordPress-specific rules", the following codes will be added to the wordpress.conf:

# WordPress: deny general stuff
location ~* ^/(?:xmlrpc\.php|wp-links-opml\.php|wp-config\.php|wp-config-sample\.php|readme\.html|license\.txt)$ {
    deny all;
}

However, this disables xmlrpc feature, which disa

We need a flag (compose-svc-start-wait ) to control how long docker-slim should wait before starting each service when there's a compose file (build, profile, run commands though the run command doesn't have support for compose yet).

Asking about this since the NSA recently published guidance advising the public and private sectors to transition to cryptographic algorithms that are no less than sha384 & ec384 (elliptic curves).

While Edwards' Curves are different, its worth noting that prior to this update sha256 & secp256k1 were both on the list of acceptable cryptographic algorithms. My deduction was that 128-bit securit

Container scanning schemas below 14.0.0 have been deprecated.

blob/main/contrib/gitlab.tpl:3 is using a deprecated version:

"version": "2.3",

The latest version of the schema is [14.1.0](https://gitlab.com/gitlab-org/gitla