mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-10-12 22:07:59 +00:00
117cbd6590
There's no actual way to forcibly sequence our check of the history until after the history has been updated, but it's pretty fast usually, just not always instantaneous. Without this, adding a few millisecond delay in the tracker reliably produces the test failures we kept seeing with an unexpectedly low length of 3. With this, it passes consistently even with the artificial delay. The query tracker being asynchronous is probably fine, but we need to test it as though it might take a while. |
||
|---|---|---|
| .. | ||
| testdata/certs | ||
| cluster_test.go | ||
| config.go | ||
| config_internal_test.go | ||
| config_test.go | ||
| dup.go | ||
| dup_arm64.go | ||
| grpc.go | ||
| grpc_internal_test.go | ||
| grpc_test.go | ||
| handler_test.go | ||
| server.go | ||
| server_internal_test.go | ||
| server_test.go | ||
| sql.go | ||
| tlsconfig.go | ||
| tlsconfig_test.go | ||
| trial.go | ||