Go

There is a strong and growing consensus in sig-node about the need of increasing the test coverage in the kubelet, improving the current testsuite about coverage and reliability. See for example the April 26 sig-node meeting notes and the [April 27 sig-node CI subgroup meeting notes](http

What happened:
Following the instructions on this page, I configure my alert with severity and component tags. I then configured PagerDuty side. However, the notification that I got in PagerDuty didn't include the correct field values. Specifically, the component
and severity fields wer

It would be a nice addition to integrate Minimal windows service stub in Caddy (built for Windows).

At the moment, it is necessary to use for example NSSM to install Caddy as a service on Windows.

See how it becomes much more natural to [install the service and remove it in the case of another project (Gitea) with the Windows tools](https:

The associated forum post URL from https://forum.rclone.org

https://forum.rclone.org/t/azure-advanced-config-option-access-tier-appears-to-be-case-sensitive/28801/4

What is the problem you are having with rclone?

When configuring an Azure Blob Storage remote, interacting

Enhancement

[2022-02-14T04:12:14.746Z] ----------------------------------------------------------------------
[2022-02-14T04:12:14.746Z] FAIL: db_test.go:7069: testSerialDBSuite.TestModifyColumnTypeWhenInterception
[2022-02-14T04:12:14.746Z] 
[2022-02-14T04:12:14.746Z] db_test.go:7124:
[2022-02-14T04:12:14.746Z]     c.Assert(checkMiddleWarningCount, Equals, true)
[2022-02-14T04:12:

Description

When creating a release in repo, the telegram bot sends the following message:

[{owner}/{repo}] Release created: {release_title} by {publisher}

A link is added to {release_title} : https://{base_url}/{owner}/{repo}/src/{tag_name}
This is a link to the tag although a link to the release was expected: https://{base_url}/{owner}/{repo}/releases/tag/{tag_name}