Go

We have sort of a mish-mash of "service" and "servicePort" and similar.

We should think about changing ALL of the places that actually relate to a service-port (a specific port of a service, not the whole service) and rename them to some new term that means "service port". E.g. "svcpt" or "spt" or "sport".

See kubernetes/kubernetes@8fffae321d66487f77692

Steps to reproduce:

Try to collapse the Explore query row using keyboard-only navigation

Actual Result:

Can’t collapse query row

Also, there is a focus-issue here. See the A11y notes:

Same tab, when you copy the query or a link to it, the focus is reset

Expected Result

Hi. I've been experiencing good reliability syncing Maildirs with Syncthing for a few weeks already - however, from time to time an occasional empty mail may now show up in my IMAP folders/e-mail client. I suspect that this is due to the partial transfers and/or temp files being read by dovecot (perhaps locking them somehow could help with this?). I was able to ignore dovecot's index files in Sync

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

Problem: trying to use place holders in the file_server's fields, e.g.:

    file_server {
      index "index.{host}.html"
    }

Does not substitute {host} with the host domain.

Request:add placeholder substitution for all file_server fields.

Thanks!

System information

Geth
Version: 1.10.13-stable
Git Commit: 7a0c19f813e285516f4b525305fd73b625d2dec8
Architecture: amd64
Go Version: go1.17.3
Operating System: linux
GOPATH=
GOROOT=go

Expected behaviour

Close files that aren't in use / have a settable limit

Actual behaviour

Every database file it opens stays open for the duration of the sync

Steps to re

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

as title

basic support for feeds was added at #569, to get backend information, just look at the 3 related pulls

Please consider adding a way to control which nodes participate in an IMPORT operation so that nodes in far regions can be excluded from the import.

Consider a 3-region cluster, with nodes in: [Japan, US West, EU]. And let's import a table into a database that has only a primary region defined in US West. All of the table's replicas will be located in US West. And the CSV data to be imported is