Question: When is a bug a bug?

Portal Home > Knowledgebase > Articles Database > Question: When is a bug a bug?

Posted by WebSnail.net, 06-16-2001, 07:49 AM
Hi, Scenario for you... A few necessary changes to my ISP's server configuration have resulted in changes to the functionality of particular aspects of setting up a new clients account. The changes involve the server doing an update (ie: adding new user accounts) every XX mins as opposed to immediately which is fine. However the problem only ever occurs if particular functions (seemingly tied to the POP3 server) are attempted before the account is created on the server. So for example if you try to create a new POP3 before the account has been created by the server (i.e. before it's latest update) it still gets reported by the control panel as "created"when it's actually not available at all. Now to my way of thinking this is a bug and needs fixing. Possibly the fix is a simple script mod to check the new/existing user account actually exists before attempting to carry out the affected functions. However, my ISP seems to take the line that if you just wait a bit then it'll all work fine. However they don't appear to be doing anything about the fact that the control panel still reports "All created" when in fact it hasn't. Granted personally I know the workaround but what about other users who don't! I'd appreciate some feedback on this as I'd like to know I'm not being unreasonable. Thanks
Posted by cperciva, 06-16-2001, 08:05 AM
I think it is quite reasonable for them to only run updates every minute or so; doing so dramatically reduces the risk of a denial of service attack being implemented through the account creation system. However, I would agree that they should not report "all done" unless it is in fact all done... I wouldn't call this really a bug, but rather an error in documentation -- they should instead report "accounts will be created within the next 60 seconds" or suchlike.
Posted by WebSnail.net, 06-16-2001, 11:01 AM
Hmm, perhaps I need to clarify. The system is automated and I have no qualms re: updates taking place every 20 minutes or so... if it means that the server will be secure and functional. Where my problem lies is with the script allegedly creating an email box that it can't... (EVER!) because, it seems, the user account hasn't been created on the server yet. Surely the code is missing the need to trap this error and tell the user "WAIT - try again in 20 minutes".
Posted by cperciva, 06-16-2001, 03:49 PM
Oh. Well in that case it is definitely a bug. When operations must be performed in order to ensure correctness, they should make sure that the operations are performed in that order. Not exactly difficult, all it means is that every 20 minutes they should create new accounts and only after that create the mailboxes.
Posted by Jaiem, 06-19-2001, 10:20 AM
First rule of programming system messages: Never say the process worked, is done, successful etc etc. There's always the chance that something didn't work right but somehow the process reach good end. People see the message and assume all is well, then when the probelm is found you get slammed for saying it was good/successful/done/etc. A little abiguity is a good thing.
Posted by ADW, 06-19-2001, 09:33 PM
WebSnail, Doesn't sound like a bug to me, A fix would be an addition to the HTML "Updates will be complete in 5 minutes"
Posted by WebSnail.net, 06-26-2001, 08:36 AM
Hmm, ok perhaps the word bug isn't quite the right term but I guess my point is... Am I right in assuming that the script is not working as advertised and that the reseller should in fact "fix" is to at bare minimum say Personally if I offered something like this to a client and it didn't do what it said it was doing, then I'd get a lot of flack... and I'd want to fix it. Bottom line, my reseller has been doing just the opposite, hence my post... Ah well... I guess others will no doubt discover the problem for themselves and he might listen then.