lakeFS icon indicating copy to clipboard operation
lakeFS copied to clipboard

lakeFS - Data version control for your data lake | Git for data

Results 460 lakeFS issues
Sort by recently updated
recently updated
newest added

Bumps [tzinfo](https://github.com/tzinfo/tzinfo) from 1.2.9 to 1.2.10. Release notes Sourced from tzinfo's releases. v1.2.10 Fixed a relative path traversal bug that could cause arbitrary files to be loaded with require when...

dependencies
ruby

Bumps [tzinfo](https://github.com/tzinfo/tzinfo) from 1.2.9 to 1.2.10. Release notes Sourced from tzinfo's releases. v1.2.10 Fixed a relative path traversal bug that could cause arbitrary files to be loaded with require when...

dependencies
ruby
exclude-changelog

Backgorund cleaning procedure to collect deleted repositories and correlated entities, as described in #3661 Pending completion of #3714

team/versioning-engine
nice-to-have
area/KV

Upon deletion - move the repository entry to `graveler_deleted` partition and delete from `graveler` Modify creation to allow collection of inital commit and default branch in case of failure. #3661...

team/versioning-engine
nice-to-have
area/KV

If the key exists in the committed data, Graveler will return `ErrPreconditionFailed`, although it may have been deleted in the in the staging area. Moreover, tombstones are not being overwritten...

bug
team/versioning-engine

UI error for conflict is misleading. By design that's conflict (changes to both right and left commits). I think the diff should not be visible for non-diffable objects (non csv,...

bug
area/UI
team/versioning-engine

Component tests run 3 times, one for every client build. This is OK, just don't run them in parallel -- it takes so much memory that we run out.

team/ecosystem

Currently when setting up lakeFS for the first time, the user is greeted with a set of credentials (and a note to keep them safe since they will never see...

area/UI
improvement
team/cloud-native
randomly-assigned

I (mistakenly...) attempted to access an ancient playground account: ```sh ❯ go run ./cmd/lakectl -c ~/.lakectl.demo.yaml repo list panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV:...

area/lakectl
team/versioning-engine

Extend lakeFS' [garbage collection](https://docs.lakefs.io/reference/garbage-collection.html) to handle abandoned branches. Ideally, let users set a policy on what qualifies as a GC-able branch: 1. it falls under a specific naming convention (i.e....

new-feature
contributor
team/ecosystem