hi team, I noticed what looks like a bug.. I get a...
# dev
s
hi team, I noticed what looks like a bug.. I get a 404 not found error in the console whenever I select a commit from the branch selector dropdown
t
Hi @Shamika Kumar, thanks for reporting this issue. we are looking into it.
I’m unable to reproduce this. would you mind sharing your commits log, and the exact steps you took before you got a 404 error? are you running the latest lakefs code?
If this works better for you, please open a github issue with the detailed info and we will be happy to take it from there.
Was able to reproduce and opened https://github.com/treeverse/lakeFS/issues/2049
s
great! thank you!
o
Hey! good catch.. I commented on issue, pasting here as well: Hey - for more context: This happens as part of
resolveRef
- given a reference, there's a function that checks whether this reference is a branch or a commit. It does so by first attempting to get a branch with the given ID, and if a 404 is returned, try and get a commit with that ID. This logic is correct and desirable, so not sure I'd qualify this is a bug per-se. See: https://github.com/treeverse/lakeFS/blob/master/webui/src/lib/hooks/repo.jsx#L8 If there's a way to supress the error from the JS log, that would probably help avoid the confusion, but looking at this issue (open since 2012...) I doubt there is: https://bugs.chromium.org/p/chromium/issues/detail?id=124534
s
I see, that makes sense, thanks for clarifying @Oz Katz
👍 1