gitea

7889 コミット

17 ブランチ

ツリー: 171b359877

コミットグラフ

作成者	SHA1	メッセージ	日付
Tamal Saha	171b359877	Use gitea forked macaron (#7933) Signed-off-by: Tamal Saha <tamal@appscode.com>	4年前
kolaente	f9ec2f89f2	Add golangci (#6418)	5年前
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.	5年前

作成者

SHA1

メッセージ

日付

Tamal Saha

171b359877

Use gitea forked macaron (#7933)

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

4年前

kolaente

f9ec2f89f2

Add golangci (#6418)

5年前

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.

5年前

3 コミット (171b3598778a1ecd0a921c71ed6755bfef68f7f0)