featurebase/http
Matthew Jaffee 06235c3d70 get container ID via "docker-compose" call in clustertests
this should be a lot more reliable than trying to construct it based
on the project name as the exact construction can differ between
docker-compose versions.

There was also an issue with the backups succeeding when they should
fail in the test. There's an arcane maze of HTTP timeouts to navigate
here, but basically there are situations where the client will just
wait forever rather than erroring if the server is paused at the
right(wrong) time. I'm not convinced we've solved every possible case
of this, so we still may see the backup succeed even when it's
supposed to fail. The ultimate hammer is to add Client.Timeout, but
that's a very blunt instrument and I'm afraid it could cause a timeout
when really we just have a lot of data to download or something.

There may be a better way to say "only time out if you literally
haven't heard a peep from the server in this long", but I haven't been
able to figure it out yet.

I also fixed how the authclustertests are run as they weren't using
the PROJECT parameter correctly. Now they can run concurrently with
clustertests, and with other copies of authclustertests without having
conflicts.
2022-02-02 12:03:46 -06:00
..
client.go get container ID via "docker-compose" call in clustertests 2022-02-02 12:03:46 -06:00
client_test.go fix panic on POST /transaction on non-primary node 2022-01-24 15:24:21 -06:00
error.go add copyright notice back in 2021-12-10 11:01:04 -06:00
handler.go get container ID via "docker-compose" call in clustertests 2022-02-02 12:03:46 -06:00
handler_internal_test.go add test coverage 2022-01-21 13:57:47 -06:00
handler_test.go Upgrade go.mod to featurebase/v3 2022-01-21 10:57:05 -07:00
translator.go Upgrade go.mod to featurebase/v3 2022-01-21 10:57:05 -07:00
translator_test.go Upgrade go.mod to featurebase/v3 2022-01-21 10:57:05 -07:00