1 KNOWN PROBLEMS AND BUGS
4 'topic [#channel] shuffle' will produce 1 in n! (where n
5 is number of subtopics in topic. IS THIS CORRECT PROBABILITY?)
6 chance that it will be the same as before.
8 If someone wants to experiment a fix for this, do so.
10 'while (!defined $newtopic || $topic{$talkchannel} eq $newtopic) {'
12 Problem #2: [UPDATED 20000224]
13 A race condition is observed if the topic is changed very
14 quickly. If the bot is told to change the topic twice but
15 has not received notification of the new topic before
16 changing to the second modification of the topic, it
17 would use the absolute first (0) topic as a reference,
18 therefore missing out on the first alteration of the
21 A very cheap solution exists. Edit IrcHooks.pl, search for
22 'topic', alter '1' to '0'. This will only cache topics made by the
23 bot (I hope). I have a faint feeling that bot-only topics are
24 stored elsewhere (history I think) but I'm not quite sure.
26 Yet another (ultimate and preferable) solution would be to have
27 topic queueing, altering the topic once the first alteration has
28 been done, changing the topic until the queue is empty. However,
29 topic floods will eventuate unfortunately. If a queue of 2 or more
30 is detected, no more topic changes are done until a time of
31 5-10seconds (how can this be done?). This is a challenge to
35 It appears that if the last string separated by a whitespace
36 of the topic will be chopped off (if it's "()") because the
37 ownership is null. At first I thought it was a bug in the regex
38 but it was okay. I guess it's a minor problem but why should
39 there be a semi-ownerless subtopic :) If it's annoying, please
40 investigate the &topicCipher() function in Topic.pl in relation to
46 DBD::mysql::st execute failed: Duplicate entry 'xk' for key 1 at
47 ./src/Freshmeat.pl line 85.
48 when freshmeat.pl is building the table and something's said in the
49 channel... seen code tries to update table but fails.
52 This may be eliminated by reducing 4-5 INSERT/UPDATE requests to
53 just 1 (total of 2), depending on the return of SELECT. If this
54 still persists and memory leaks are happening, first make
55 sure you are not using broken mysql tables, secondly bitch at the
56 mysql-perl author that there is a memory leak when a broken table
60 doWarn is called when perl catches a "warning".
63 [ 44] !WARN! PERL: Use of uninitialized value at ./src/Modules.pl line 316.
64 [ 45] !WARN! PERL: offending line => ' if ($query eq "") {'.
69 ### From 'perlfunc'...
70 Note that this is quite safe and will not produce an endless loop,
71 since __WARN__ hooks are not called from inside one.
74 Note that __DIE__/__WARN__ handlers are very special in one
75 respect: they may be called to report (probable) errors found by
76 the parser. In such a case the parser may be in inconsistent
77 state, so any attempt to evaluate Perl code from such a handler
78 will probably result in a segfault.
81 ! 14! Debian: 12.87 sec to complete query.
82 ! 15! </#debian-bots> Debian Search of 'testing' (2 shown): ...
83 [ 38] disconnect from irc.home.org (Connection reset by peer).
84 [ 39] reconnection... cleaning out channel cache.
87 Edit /usr/lib/perl5/Net/IRC.pm
88 Comment out *->quit() on 'sub DESTROY'
89 Alternatively, bitch at author of Net::IRC.
92 <\ifvoid> apt, cellwave?
93 <apt> i haven't a clue, \ifvoid
94 <tapt> bugger all, i dunno, \ifvoid
97 <egamI-rorriM> apt: lart
98 * apt/#debian strangles with a doohicky mouse cord
101 [Flugh] i say 'rom, rom is a mud server', it says 'ok'. then
102 'rom, rom?' it says 'yes? <nick>'
104 # info package dist doesn't recognise dist.