#205 Cannot delete my NotABug account because of undeletable mirror repos that have 500 error codes

Open
opened 5 months ago by DandelionSprout · 9 comments

Hello.

https://notabug.org/DandelionSprout/FilterMirrorRepo2 and https://notabug.org/DandelionSprout/Adblock-list-backups-ABPindo have been showing 500 error codes for the past 2 months, which is far in excess of what could be expected of an online code repo.

So this morning I decided to try to delete my NotABug account, but was told that I couldn't, because I hadn't deleted my listed repos. But because I can not access the repos at all, I am unable to delete them (as far as I can tell).

So I want for either, 1) those two repos to get back online, 2) the repos to be deleted, or 3) my NotABug account to be deleted without first having had to delete the repos.

Hello. https://notabug.org/DandelionSprout/FilterMirrorRepo2 and https://notabug.org/DandelionSprout/Adblock-list-backups-ABPindo have been showing 500 error codes for the past 2 months, which is far in excess of what could be expected of an online code repo. So this morning I decided to try to delete my NotABug account, but was told that I couldn't, because I hadn't deleted my listed repos. But because I can not access the repos at all, I am unable to delete them (as far as I can tell). So I want for either, 1) those two repos to get back online, 2) the repos to be deleted, or 3) my NotABug account to be deleted without first having had to delete the repos.

all you needed to do was to file a bug report about the broken repos - several ppl have had that same problem in the past few months, they filed bug reports, and got their repos fixed promptly

bugs that do not get reported are not likely to be fixed - had you done that, your repos could have been fixed months ago

all you needed to do was to file a bug report about the broken repos - several ppl have had that same problem in the past few months, they filed bug reports, and got their repos fixed promptly bugs that do not get reported are not likely to be fixed - had you done that, your repos could have been fixed months ago

I was of the previous belief that this issue affected all mirrored repos on NotABug, and that a universal fix for them was on its way. That's why I felt it'd be impolite of me to e.g. report the 500 errors after a few days or so, to instead give NotABug some time to fix it without me coming across as nagging to them.

If I had known that they were fixing these issues on a repo basis, I'd of course have done this much earlier, but how was I to know that that was the intended way of doing it?

I was of the previous belief that this issue affected all mirrored repos on NotABug, and that a universal fix for them was on its way. That's why I felt it'd be impolite of me to e.g. report the 500 errors after a few days or so, to instead give NotABug some time to fix it without me coming across as nagging to them. If I had known that they were fixing these issues on a repo basis, I'd of course have done this much earlier, but how was I to know that that was the intended way of doing it?

reporting bugs against a free software project is not impolite - it is an entirely expected and encouraged, necessary ingredient for the health of a project - if the bug is not fixed in a reasonable amount of time, you definitely should nag the developers without reservation, and you should nag them repeatedly, week after week, until the bug is fixed, or until you conclude that they must be intentionally neglecting or ignoring your concerns, or woefully incompetent - only then, might it be a good idea to consider abandoning the project; but by that point it would not be very reasonable to expect them to do anything

for that reason, i could have never opened a bug report like this one - if i had concluded that the admin was so incompetent or lazy that the service was unusble, i would have simply stopped using the service; without wasting another minute of my time to close the account, or to write a public declaration of my dissatisfaction - the trail of pestering bug reports that i had left behind on their bug tracker, forever un-addressed, would suffice quite well for that purpose

reporting bugs against a free software project is not impolite - it is an entirely expected and encouraged, necessary ingredient for the health of a project - if the bug is not fixed in a reasonable amount of time, you definitely should nag the developers without reservation, and you should nag them repeatedly, week after week, until the bug is fixed, or until you conclude that they must be intentionally neglecting or ignoring your concerns, or woefully incompetent - only then, might it be a good idea to consider abandoning the project; but by that point it would not be very reasonable to expect them to do anything for that reason, i could have never opened a bug report like this one - if i had concluded that the admin was so incompetent or lazy that the service was unusble, i would have simply stopped using the service; without wasting another minute of my time to close the account, or to write a public declaration of my dissatisfaction - the trail of pestering bug reports that i had left behind on their bug tracker, forever un-addressed, would suffice quite well for that purpose

Hi @bill-auger , I'm somewhat new in this community, I commented about the same problem in this issue: #203 , is that enough or should I report it somewhere else?

Thanks

Hi @bill-auger , I'm somewhat new in this community, I commented about the same problem in this issue: https://notabug.org/hp/gogs/issues/203 , is that enough or should I report it somewhere else? Thanks

"enough" is: whatever gets the admin's attention - i only responded to this issue to give some general advice to the OP about the importance of bug reports - i am in no position to do, or prescribe, anything about bug reports on this website

if it were me, i would open a new bug report specific to your concern, just as #203 did; because this does not appear to be a general problem - if it were, i would expect it would have been fixed already - i can only assume that each person affected by this will need to make that known explicitly

generally speaking, a good bug report is one that explains the problem and indicates the steps to take that will allow others to see the problem for themselves, and where no other existing bug report expresses the identical problem - in this case, those steps are just the link to the broken web page, and as it appears not to be a general problem, the "steps to reproduce" will be different for every repo - but those are just the common-sense norms - regarding most software projects, there are no rules, guidelines,, or protocols for reporting bugs - in the rare cases where the project publishes explicit bug reporting guidelines, they will normally be found n a file named CONTRIBUTING, or on the projects wiki/formus, or sometimes each new bug report will be pre-populated with the bug reporting guidelines

"enough" is: whatever gets the admin's attention - i only responded to this issue to give some general advice to the OP about the importance of bug reports - i am in no position to do, or prescribe, anything about bug reports on this website if it were me, i would open a new bug report specific to your concern, just as #203 did; because this does not appear to be a general problem - if it were, i would expect it would have been fixed already - i can only assume that each person affected by this will need to make that known explicitly generally speaking, a good bug report is one that explains the problem and indicates the steps to take that will allow others to see the problem for themselves, and where no other existing bug report expresses the identical problem - in this case, those steps are just the link to the broken web page, and as it appears not to be a general problem, the "steps to reproduce" will be different for every repo - but those are just the common-sense norms - regarding most software projects, there are no rules, guidelines,, or protocols for reporting bugs - in the rare cases where the project publishes explicit bug reporting guidelines, they will normally be found n a file named CONTRIBUTING, or on the projects wiki/formus, or sometimes each new bug report will be pre-populated with the bug reporting guidelines

Hi, thank you for the clarification @bill-auger!

I think my problem is identical both to #205 and to #203. And it has been two weeks since #203 was opened and it seems he didn't get the help he needed (his repo is still returning HTTP 500). So, I don't think opening another similar issue will help...

I guess I'll ask about this on this project's IRC channel.

Hi, thank you for the clarification @bill-auger! I think my problem is identical both to #205 and to #203. And it has been two weeks since #203 was opened and it seems he didn't get the help he needed (his repo is still returning HTTP 500). So, I don't think opening another similar issue will help... I guess I'll ask about this on this project's IRC channel.

seriously, you guys - the advice i am giving is based on many years of experience with free software projects - if the IRC were a good way to report bugs, then i would have mentioned that in this thread

the best way to get the attention of a website admin or people who can fix bugs, is asynchronously, on the bug tracker or via email - it is generally true for any software project that the IRC is among the least likely ways to get your problem solved for anything more than the simplest common Q&A - you would be much much better off opening a bug report or sending email

i do know that the admin of this website is quite busy - if you open a bug report, he will see it and act upon it eventually, if there is anything he can do

as i mentioned, opening bug reports is always a good thing, as long as they are not identical duplicates - if bug reports start piling up ignored and stay that way for too long, that, in itself, serves a valuable purpose: namely, to indicate to other users that the project is in need of help or otherwise not operating at its maximum potential; but there is very little urgency with this particular web service, and two weeks is not an unreasonable amount of time for any volunteer-operated gratis service

the worst disaster that any competent dev could experience while using notabug is a temporary interruption of service - thats because a competent developer would never rely solely on a 3rd-party web service to protect their data, especially not a gratis one; so data loss should be of no concern - of course this interruption of service is an inconvenience; but so far. the others got their repos restored in tact, so there is probably little chance of data loss and im sure it will be corrected at the admin's next convenience

i am quite sure that all you need to do is create a new repo and push your local copy to it or clone it again from its upstream if for some neglectful reason you did not keep a copy

if you did not keep copies of everything, and you lose some work, it really is your fault - this website never promised to protect your data; and neither does github or any other website make such promises about it's gratis services

seriously, you guys - the advice i am giving is based on many years of experience with free software projects - if the IRC were a good way to report bugs, then i would have mentioned that in this thread the best way to get the attention of a website admin or people who can fix bugs, is asynchronously, on the bug tracker or via email - it is generally true for any software project that the IRC is among the least likely ways to get your problem solved for anything more than the simplest common Q&A - you would be much much better off opening a bug report or sending email i do know that the admin of this website is quite busy - if you open a bug report, he will see it and act upon it eventually, if there is anything he can do as i mentioned, opening bug reports is always a good thing, as long as they are not identical duplicates - if bug reports start piling up ignored and stay that way for too long, that, in itself, serves a valuable purpose: namely, to indicate to other users that the project is in need of help or otherwise not operating at its maximum potential; but there is very little urgency with this particular web service, and two weeks is not an unreasonable amount of time for any volunteer-operated gratis service the worst disaster that any competent dev could experience while using notabug is a temporary interruption of service - thats because a competent developer would never rely solely on a 3rd-party web service to protect their data, especially not a gratis one; so data loss should be of no concern - of course this interruption of service is an inconvenience; but so far. the others got their repos restored in tact, so there is probably little chance of data loss and im sure it will be corrected at the admin's next convenience i am quite sure that all you need to do is create a new repo and push your local copy to it or clone it again from its upstream if for some neglectful reason you did not keep a copy if you did not keep copies of everything, and you lose some work, it really is your fault - this website never promised to protect your data; and neither does github or any other website make such promises about it's gratis services

Thank you for the lesson @bill-auger. I think I overreacted about this minor issue, it's probably due to being tired and not able to rest properly lately. This is not even interrupting my work. I'm really sorry for bothering, thanks for taking the time to answer me.

Thank you for the lesson @bill-auger. I think I overreacted about this minor issue, it's probably due to being tired and not able to rest properly lately. This is not even interrupting my work. I'm really sorry for bothering, thanks for taking the time to answer me.

I do definitely get your point(s), but it just so happens that I was doing some cleaning in my password manager (Bitwarden) by removing some accounts that I felt I didn't have much use for anymore. However, doing such cleaning, virtually always require being able to delete the accounts before removing them from the password manager.

And since I hadn't got all that much use out of NotABug, I figured I could just as well delete that account, leading me to the situation that I wrote about in the OP.

I do definitely get your point(s), but it just so happens that I was doing some cleaning in my password manager (Bitwarden) by removing some accounts that I felt I didn't have much use for anymore. However, doing such cleaning, virtually always require being able to delete the accounts before removing them from the password manager. And since I hadn't got all that much use out of NotABug, I figured I could just as well delete that account, leading me to the situation that I wrote about in the OP.
Sign in to join this conversation.
No Milestone
No assignee
3 Participants
Loading...
Cancel
Save
There is no content yet.