Cannot delete LFS objects #17

Closed
opened 7 months ago by alifara · 5 comments
alifara commented 7 months ago

Description

Cannot delete LFS objects from Repo-Settings->LFS.

Clicking on the delete button will cause a popup to open but it immediately disappears.

Inspect Log

[Warning] index.js?v=ff4f81624cfee25acd96f76cd1613476:1 [Violation] 'click' handler took 600ms
[Warning] [Violation] Forced reflow while executing JavaScript took 242ms
[Warning] index.js?v=ff4f81624cfee25acd96f76cd1613476:1 [Violation] 'setTimeout' handler took 72ms
[Error] chrome-browser-polyfill.js:1 Uncaught (in promise) {}
(anonymous) @ chrome-browser-polyfill.js:1

Screen Record

Uploaded as an attachment.

## Description ##### Cannot delete LFS objects from Repo-Settings->LFS. Clicking on the delete button will cause a popup to open but it immediately disappears. ## Inspect Log ``` [Warning] index.js?v=ff4f81624cfee25acd96f76cd1613476:1 [Violation] 'click' handler took 600ms [Warning] [Violation] Forced reflow while executing JavaScript took 242ms [Warning] index.js?v=ff4f81624cfee25acd96f76cd1613476:1 [Violation] 'setTimeout' handler took 72ms [Error] chrome-browser-polyfill.js:1 Uncaught (in promise) {} (anonymous) @ chrome-browser-polyfill.js:1 ``` ## Screen Record [Uploaded as an attachment.](https://codeberg.org/attachments/28c6dba0-599d-46ac-919f-03c57b6cf22d)
Collaborator

Thank you for the report. Could you please check upstream at Gitea (https://github.com/go-gitea/gitea/) if this has already been reported or even fixed? If not, it would really help us if you could move forward and test on try.gitea.io if it's still reproducible and report it to the Gitea issue tracker otherwise.

If you do not have a GitHub account, you can also share your findings here and we'll forward the report to the maintainers of Gitea.

Thanks.

Thank you for the report. Could you please check upstream at Gitea (https://github.com/go-gitea/gitea/) if this has already been reported or even fixed? If not, it would really help us if you could move forward and test on try.gitea.io if it's still reproducible and report it to the Gitea issue tracker otherwise. If you do not have a GitHub account, you can also share your findings here and we'll forward the report to the maintainers of Gitea. Thanks.
Collaborator

@alifara can not reporduce on codeberg witch browser do you use?

@alifara can not reporduce on codeberg witch browser do you use?
Poster

@6543

@alifara can not reporduce on codeberg witch browser do you use?

Chromium


Yeah, I can not reproduce it either (on Falkon browser).

@6543 >@alifara can not reporduce on codeberg witch browser do you use? Chromium --- Yeah, I can not reproduce it either (on [Falkon browser](https://www.falkon.org/)).
Collaborator

hmm strange,

@alifara by the way the main issue tracker is at https://codeberg.org/Codeberg/Community/issues :)

hmm strange, @alifara by the way the main issue tracker is at https://codeberg.org/Codeberg/Community/issues :)
Collaborator

Is this still valid? If yes, let's please move it to a proper issue tracker :-)
Otherwise, I'm happy to close this.

Is this still valid? If yes, let's please move it to a proper issue tracker :-) Otherwise, I'm happy to close this.
alifara closed this issue 2 months ago
Sign in to join this conversation.
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.