Chat's down again

[BigYin]

and just when it was going so well!!!

 

[abeyptfc]

its the new 11 o clock curfew! now i'll have to actually sit and pay attention to f'n dante's peak!!

 

[BigYin]

No excuse for not getting on with my brewing!!

 

[abeyptfc]

its back on!!!!!!

 

[BigYin]

wonder what happened last night? A glitch in the force? :hmm:

 

[abeyptfc]

wonder what happened last night? A glitch in the force? :hmm:

must have been some gremlins in the system!

 

[BigYin]

Seems to have been down for almost exactly one hour, from 11pm to midnight, which suggests to me a little bug in the code that controls the chatroom :hmm:

 

[Vossy1]

Sorry once again guys .....

Please can I ask (again) that if it happens you let one of the admin know, or all of us by sending a message to THBF admin user as we won't know about it until we next log on if you don't :thumb:

There is a bug, settings are chat open 1800 Fridays to midnight Sundays, I'll e-mail eskimobob now to take a look at his convenience :thumb:

 

[BigYin]

sorry V, I was wondering who / how to let know, but at the back of 11pm on a friday evening, after a few strong beers on an empty head, I wasn't really too sure :lol: :whistle:

 

[EskiBrew]

Found the bug chaps. The times were changed over Christmas - when they were changed back, someone put a . as a separator rather than a : so e.g. the time 23:59 was entered as 23.59

The turn off time was therefore evaluating to 23:00 rather than 23:59.

Took me some time to spot that

 

[Vossy1]

sorry V, I was wondering who / how to let know, but at the back of 11pm on a friday evening, after a few strong beers on an empty head, I wasn't really too sure

No worries BY, it's sorted now

Found the bug chaps. The times were changed over Christmas - when they were changed back, someone put a . as a separator rather than a : so e.g. the time 23:59 was entered as 23.59

Many thanks M for taking the time to find MY mistake
Sorry for the error chaps and any inconvenience caused, especially to M who had to waste his own time trying to find the problem I caused .......one ruddy dot...honestly

 

[Baz Chaz]

.......one ruddy dot...honestly

There you go Vossy it's official :wha: you're one dot short of a colon :lol:

I wouldn't worry about it, it's easy to make simple mistakes in the computing world, but bloody frustrating when you can't find 'em eh :!:

 

[BigYin]

isn't it just! hee hee - it's what I do for a living, and there's always a bitter sweet feeling in finding a bug YOU introduced :whistle: :lol: :lol:

 

[Baz Chaz]

......... and there's always a bitter sweet feeling in finding a bug YOU introduced :whistle: :lol: :lol:

Yeah you sit there for hours ranting and swearing at the bloody computer :evil: then suddenly realise you'd made the cockup in the first place :whistle: :lol:

 

[Runwell-Steve]

......... and there's always a bitter sweet feeling in finding a bug YOU introduced :whistle: :lol: :lol:

Especially when they've had to call you out in the middle of the night on extortionate call out rates as the system has crashed.

I do know of some people who would deliberately build in some small defects that they would have to be called out to mend, just in order to justify there call out retainer fees, and the extortionate rates they charged to come in and fix things.