Platform_Mirocod

8330 Commits

0 Branches

154 Tags

505 MiB

Tree: 8d9e625f83

Commit Graph

Author	SHA1	Message	Date
Tamal Saha	171b359877	Use gitea forked macaron (#7933 ) Signed-off-by: Tamal Saha <tamal@appscode.com>	6 years ago
kolaente	f9ec2f89f2	Add golangci (#6418 )	6 years ago
zeripath	7d434376f1	Pooled and buffered gzip implementation (#5722 ) * Pooled and buffered gzip implementation * Add test for gzip * Add integration test * Ensure lfs check within transaction The previous code made it possible for a race condition to occur whereby a LFSMetaObject could be checked into the database twice. We should check if the LFSMetaObject is within the database and insert it if not in one transaction. * Try to avoid primary key problem in postgres The integration tests are being affected by https://github.com/go-testfixtures/testfixtures/issues/39 if we set the primary key high enough, keep a count of this and remove at the end of each test we shouldn't be affected by this.	6 years ago

Author

SHA1

Message

Date

Tamal Saha

171b359877

Use gitea forked macaron (#7933 )

Signed-off-by: Tamal Saha <tamal@appscode.com>

6 years ago

kolaente

f9ec2f89f2

Add golangci (#6418 )

6 years ago

zeripath

7d434376f1

Pooled and buffered gzip implementation (#5722 )

* Pooled and buffered gzip implementation

* Add test for gzip

* Add integration test

* Ensure lfs check within transaction

The previous code made it possible for a race condition to occur whereby a LFSMetaObject could be checked into the database twice. We should check if the LFSMetaObject is within the database and insert it if not in one transaction.

* Try to avoid primary key problem in postgres

The integration tests are being affected by
https://github.com/go-testfixtures/testfixtures/issues/39 if we set the
primary key high enough, keep a count of this and remove at the end of
each test we shouldn't be affected by this.

6 years ago

3 Commits (8d9e625f83bf05086cfb72087548d203aff96db3)