It is mentioned that there is an error code page for v2 protocol:
https://github.com/etcd-io/etcd/blob/ae7862e8bc8007eb396099db4e0e04ac026c8df5/server/etcdserver/api/v2error/error.go#L16

However, I can't find Documentation/v2/errorcode.md in this repo. Is the comment stale?

Postgres provides the fuzzystrmatch module, which includes several useful functions:

• levenshtein and levenshtein_less_equal, to calculate levenshtein distance between strings
• soundex and difference to calculate Soundex codes for names
• metaphone, dmetaphone and dmetaphone_alt to compute "sounds like" stri

Issue description

Go 1.15 will introduce a new Validator interface, which may be implemented by Conn to allow drivers to signal if a connection is valid or if it should be discarded:

https://tip.golang.org/pkg/database/sql/driver/#Validator

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

go-pg doesn't follow any fixed constraint name conventions.

type TestAccess struct {
	Id        string   `pg:"type:uuid,default:uuid_generate_v4()" json:"id"`
	BatchId   string   `pg:"type:uuid,on_delete:CASCADE,unique:batch_id_test_id" json:"batch_id,omitempty"`
	Batch     *Batch   `json:"batch,omitempty"`
	StudentId string   `pg:"type:uuid,on_delete:CASCADE" json:"student_id,omitempt

Same as git.

The problem faced currently?

Currently space cloud doesn't allow the end-user to set content type while uploading objects to file store. This works in many cases. But when you are using file store for rendering media content in your app. The browser might render files depending upon the content type set in http response. For media content, if content type is not known by the browser, the Brow

微信群满了，建议用钉钉

Calling db.Drop when a bucket does not exist returns "bucket not found" and that error is directly from bolt's bolt.ErrBucketNotFound, I believe this error should be translated to storm.ErrNotFound.