Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: lakectl local doesn't mention the reason commit fails when writing to a protected branch #8333

Open
idanovo opened this issue Nov 3, 2024 · 1 comment
Open

[Bug]: lakectl local doesn't mention the reason commit fails when writing to a protected branch #8333

idanovo opened this issue Nov 3, 2024 · 1 comment
Labels
bug Something isn't working contributor good first issue Good for newcomers

Comments

@idanovo
Copy link
Contributor

idanovo commented Nov 3, 2024 •
edited
Loading

What happened?

When running lakectl local commit using a protected branch I get:

object to backing store: request failed (403 Forbidden)
Error executing command.

Expected behavior

We should mention why we've got 403 which is in our case, writing to a protected branch.

lakeFS version

1.40.0

Affected clients

lakectl
@idanovo idanovo added bug Something isn't working contributor labels Nov 3, 2024
@talSofer talSofer added the good first issue Good for newcomers label Nov 6, 2024
@arielshaqed
Copy link
Contributor

Looks like these lines could add this info but don't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working contributor good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@arielshaqed @talSofer @idanovo