User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080213 BonEcho/2.0.0.12 Build Identifier: Stephan has a headache. This shouldn't be. Reproducible: Always Steps to Reproduce: Wake up Actual Results: Stephan has a headache Expected Results: Stephan does not have a headache
Here is a link wich may help fix the bug: http://www.vidal.fr/Medicament/aspirine_du_rhone-1537.htm Cheers,
This bug looks more complicated than I expected. My first patch (which I liked to call "aspirin") had some really bad side-effects. We're gonna need some help on this one.
Created attachment 1520 tylenol with codeine One possible remedy. Has the added benefit of making you nice and sleepy and a little funny in the head.
Perhaps we could simply remove this head. After all, there is only one user, and therefore the impact would be minimal.
(In reply to comment #4) > Perhaps we could simply remove this head. After all, there is only one user, > and therefore the impact would be minimal. You are right. I propose the following method: $ head Stephan_Arts >/dev/null
(In reply to comment #5) > $ head Stephan_Arts >/dev/null I forgot to remove stderr, use this instead: $ head Stephan_Arts >/dev/null 2>/dev/null
(In reply to comment #6) > (In reply to comment #5) > > $ head Stephan_Arts >/dev/null > I forgot to remove stderr, use this instead: > $ head Stephan_Arts >/dev/null 2>/dev/null Either proves to be ineffective, the head remains in place and a mere copy is tossed away.
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > $ head Stephan_Arts >/dev/null > > I forgot to remove stderr, use this instead: > > $ head Stephan_Arts >/dev/null 2>/dev/null > > Either proves to be ineffective, the head remains in place and a mere copy is > tossed away. > I can confirm this bug, but it is only reproducible under great stress and tends to appear and disappear at random times... The proposed solution doesn't seem to work here: "head: cannot open `Harold_Aling' for reading: No such file or directory" Am I missing something?
I can reproduce the bug from time to time. Who wanna go with me and talk to _god_ (even kick him a bit in the nuts btw), and fix the problem at the source? Does someone know the key or the passphrase to open the right door?
(In reply to comment #8) > The proposed solution doesn't seem to work here: "head: cannot open > `Harold_Aling' for reading: No such file or directory" > > Am I missing something? Yes, this part of the command: 2>/dev/null (In reply to comment #9) > I can reproduce the bug from time to time. Who wanna go with me and talk to > _god_ (even kick him a bit in the nuts btw), and fix the problem at the source? > > Does someone know the key or the passphrase to open the right door? Maybe if you look at the manual[1] long enough, the password will apear. It may be hidden as some kind of Easter Egg. [1]: http://www.kingjamesbibleonline.org/
Candidate patch: go_to_bed(); - sleep(3*60*60); + sleep(9*60*60); wake_up(); Usually solves it for me.
All of these solutions are really just workarounds. But if you take a look at the internals, the whole thing is spaghetti code. We've got legacy organs, multiple limbs, and a lumbar spine that's simply not designed to last as long as this hardware is actually sticking around in the wild. To speak directly to the head (the source of this complaint), EVERY neuron essentially GOTOs the next neuron when executing instructions. There is no abstraction, and modularity is crude at best (Why do we have separate Wernicke's and Broca's aphasias? Because some asshole decided to split up the language center). So I propose rewriting Stephan from scratch. We'll use a high level language, a Big Up Front design, and lots of buzzword technologies. The planned effort will likely take years, while old Stephan continues to have a growing number of known bugs, but no updates. We'll switch revision control systems every time we change maintainers, which will happen every six months as a burnt out no-talent realizes he's on a dead end project that can never fulfill it's ambitious design goals. Around the time that we get Stephan able to compile on a minimum number of architectures (Look! He sends mail!) the competition will have proceeded to improve the old design in various hacky, but functional ways - such as the sleep() patch suggested here. I'll start this process rolling by suggesting we close this bug WONTFIX, dive into the rewrite, and not bother to check if the new code has the same bug (it will, but due to a slightly different cause. The future maintainer, a 19 year old college student who hacks between exams and doesn't know the original author's name will describe this state of affairs as a "Feature"). It may be messy, but we're Open Source devs! It's the only strategy we know.
(In reply to comment #8) > The proposed solution doesn't seem to work here: "head: cannot open > `Harold_Aling' for reading: No such file or directory" > > Am I missing something? > You're missing the harold-aling-dev package.
Created attachment 1522 advil Take an Advil!
> Steps to Reproduce: > Wake up I can reproduce this, sometimes even without waking up. Second patch doesn't work. First patch will damage my computer when used constantly.
Problem persists, how is the rewrite doing? Is it in a state where we can migrate the data to it yet?
Maybe there is a do_vacation() routine missing in Stephan, or at least something like relax()? if (week_day > Friday && week_day <= Monday) force_relax(2days) if (working_days > 180) do_vacation(14days)
Have you tried: - Instant coffee with 1/3 milk (yes, the instant and milk part are important) - Diclofenac/Naproxen - Eletriptan ?
And now Stephan is tired and it stops release processing: [23:19:58] (sarts): JPohlmann: sorry, but it was a long weekend... have massive shortage of sleep... (over the course of the last couple of weeks) What should we do about that?
Moving invalid bugs to the /dev/null product.