Fix integrity error handling

[varmar05]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 17034977458

Details

• 18 of 19 (94.74%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.1%) to 91.99%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
server/mergin/sync/public_api_v2_controller.py	4	5	80.0%

Totals
Change from base Build 16991018319:	0.1%
Covered Lines:	7488
Relevant Lines:	8140

---

💛 - Coveralls

[MarcelGeo]

If I tried this with existing Upload entry in the table. v2 project push was not not

INSERT INTO upload () VALUES ("projectid", version)

And tried then sync_project in py-client:

• pull
• push

Upload entry disappeared and I was able to do push. Not sure If this is good behavior.

[varmar05]

If I tried this with existing Upload entry in the table. v2 project push was not not

INSERT INTO upload () VALUES ("projectid", version)

And tried then sync_project in py-client:

* pull

* push

Upload entry disappeared and I was able to do push. Not sure If this is good behavior.

Not sure I understand it correctly but if you run raw SQL query (not from application) then you will insert upload record to table but lockfile will not be created, therefore such upload is considered as inactive (invalid) and will be removed by subsequent push attempt.

To have blocking upload you need both, a record in database and recently updated associated lockfile.

[MarcelGeo]

It works with lockfile ... nice 🌮