N-o-Z
N-o-Z
Repro: 1. dump refs on repo with default branch "x" 2. create bare repo with default branch "y" 3. preform restore refs on bare repo using dump Expected: failure /...
In KV, Delete item is an idempotent operation, which succeeds whether the item existed in the store or not. In DB we relied on the postgres DELETE command which failed...
Error should not be wrapped with key information. Instead add logging to module
Since we don't want / can't modify or add to the current interface - we have many places where we call the GetRepo in the graveler level and fail to...
- See: https://github.com/treeverse/lakeFS/pull/3645#discussion_r918673348
https://github.com/treeverse/lakeFS/runs/7376726113?check_suite_focus=true ``` lakefs_1 | time="2022-07-17T09:45:07Z" level=error msg="bad S3 PutObject response" func="pkg/block/s3.(*Adapter).streamToS3" file="build/pkg/block/s3/adapter.go:250" error="s3 error: \nInternalErrorWe encountered an internal error. Please try again.VYSDHQGHXYB03VZW7+W9n4/EwOo7D8okfA2ox1Yzva6G4fUlFCHMDOvUcN+LiHaYL+jDNhRXfmZzMjF+dx769wzWBvs=" host="lakefs:8000" log_audit=API method=POST operation=PutObject path=/api/v1/repositories request_id=088b84ac-a99b-48af-ad20-5f50200ba41d service_name=rest_api status_code=500...
Currently, we have no way of knowing which ref a lakefsfs version is based on. Suggest adding tags for future versions (and possible past) Add release process documentation Maintain a...
Closes #1933 (but not really...) Design proposals document for in-house hard-delete in lakeFS The
Per discussions and as result of work on local KV driver, decided to change approach and allow defaults configuration to be managed under the config package
Support migration of lakeFS database between different KV implementations by adding 2 flows: 1. Export - dump all the data from old database into file 2. Import - load data...