Focused crawls are collections of frequently-updated webcrawl data from narrow (as opposed to broad or wide) web crawls, often focused on a single domain or subdomain.
In all of our current uses of os.umask or filesystem.umask, we always temporarily set it to a different value and then restore it using a try/finally block. I expect this pattern to continue.
Because of that, why don't we create a simple function in certbot.util that can be used as a context manager to set umask to a value and restore it to its previous value when exiting the with blo
When using the RateLimiter Middleware with a rate between 0 and 1 all events will be rejected instead of applying the specified rate. E.g.: e.Use(middleware.RateLimiter(middleware.NewRateLimiterMemoryStore(0.5)))
I am not saying that it is a common use case to have
Is your feature request related to a problem? Please describe.
I've experienced intermittent issues with the k8s api-server reaching the cert-manager-webhook, or so I think. I wanted to understand and verify if the webhook received the requests or not, and sometimes it seems to work out.
The issue is that there is no logs for me to see this from the webhook pod, even with --v=6 set.
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
In all of our current uses of
os.umaskorfilesystem.umask, we always temporarily set it to a different value and then restore it using atry/finallyblock. I expect this pattern to continue.Because of that, why don't we create a simple function in
certbot.utilthat can be used as a context manager to set umask to a value and restore it to its previous value when exiting thewithblo