mirror of
https://github.com/moollaza/repo-remover.git
synced 2026-04-25 16:55:49 +03:00
[GH-ISSUE #168] repo-remover status? #7
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/repo-remover-moollaza#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @janosh on GitHub (Oct 6, 2020).
Original GitHub issue: https://github.com/moollaza/repo-remover/issues/168
Originally assigned to: @moollaza on GitHub.
I'm getting an infinite spinner on the latest Chrome (85) and macOS (10.15.7). Disabled all Chrome extensions just in case. Problem remains.
@cleor41 commented on GitHub (Oct 7, 2020):
Same
@moollaza commented on GitHub (Oct 7, 2020):
I just tested and it seems to be working currently.Edit: I see this now in Chrome and Safari, however Firefox seems to be working fine.
I haven't pushed and changes in a while so I suspect it might be an upstream issues. I'll have to investigate further.
@janosh commented on GitHub (Oct 7, 2020):
Just retested. Still not working for me. Nothing logged to console.
@moollaza commented on GitHub (Oct 7, 2020):
Thanks for confirming @janosh
I've confirmed the breakage occurred in this PR: https://github.com/moollaza/repo-remover/pull/156
It should be working in the previous build here though: https://repo-remover-git-dependabot-npmandyarndot-prop-421.moollaza.vercel.app/
I'll have to debug what changed in the VueJS update that caused this breakage.
@moollaza commented on GitHub (Oct 7, 2020):
This should be fixed. I've reverted the PR that caused the issue.
I dug into this for a while, but can't determine what's actually causing the issue.
It appears that for some reason the
result()callback is not called in Chrome/Safari when the GraphQl API response is returned, so the loading state is never disabled.@janosh commented on GitHub (Oct 7, 2020):
Confirmed working again. Thanks a lot!