Go

What would you like to be added?

The test/e2e tests are full of assertions which compare a boolean against true or false, often without any additional explanation. When those assertions fail, the error message is useless for understanding what went wrong, basically just saying "expected false to be true".

All of those assertions should be replace with `if () framework.Fa

Right now, Syncthing seems to always use LF for line endings in config.xml and .stignore. This is a problem in Windows when trying to edit those using the built-in Notepad, which until very recently had no support for other line endings than CRLF. Support for them has only been added in the very recent versions of Windows 10.

The problem is that when opening those files in Notepad under old

It seems Caddy does not support wildcards/ expression matching in the reverse proxy's header_up.

For example this does not remove any headers:

header_up -X-SHIBBOLETH-*

This works as expected, but is limited in its use:

header_up -X-SHIBBOLETH-LOGIN

It'd be great if Caddy would support wildcards/ expression matching in the reverse proxy's header_up/ header_down.

It is currently difficult to see if this API is implemented at all and what the API actually is from the docs, for which there are none. It should be here I think(?): https://geth.ethereum.org/docs/rpc/ns-eth

https://github.com/pingcap/tidb/blob/42001503cbe6fd24c51214f59e3d3f5ec510f281/parser/lexer.go#L486-L509

The break statement at line 498 will take the control out of the switch but not out of the loop. If that is the intended behavior, the break is useless.

(Found by revive's useless-break rule)

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

https://forum.rclone.org/t/display-warnings-for-paths-that-exceed-windows-path-length-limit/26608

What is your current rclone version (output from rclone version)?

rclone v1.55.1

• os/type: windows
• os/arch: amd64
• go/version: go1.16.3
• go/linking: dynamic
• go/tags: cmount

What problem are you are t

It would be good if Gitea offered support for the new citation file format, cf. https://citation-file-format.github.io/ and https://blog.front-matter.io/mfenner/step-forward-for-software-citation

This is intended to allow scientists to cite software repositories. I can imagine an implementation similar to Github: Similar to the buttons for forks and downloads of repositories, there may be a new

At README.md, there is a slack link:

Is it for public discussion for the project?

But the slack link shows "You need to sign in to see this page.", and I cannot sign up for this page(or workspace).

@spf13 please fix this.

Currently, tree.NotExpr is implemented natively in the vectorized engine, so we have to fallback to the older row-by-row engine to evaluate it. We should, instead, vectorize NotExpr.

I think the implementation will be quite similar to how tree.IsNullExpr implemented, and I think we will want to implement two version of NotExpr operator:

• one for projections, which populates a `coldata

Steps to reproduce the issue:

1. minikube -p p1 start and wait for cluster p1 to be ready => minikube created network 6775a57b0a2c p1 bridge local
2. minikube -p p1 stop => cluster stop, network p1 still exists (as expected)
3. minikube -p p2 start and wait for cluster p2 to be