#18 Reminder of several bugs on 8rc1 under debian testing

[Luiz Castelo-Branco]

This is only a reminder note and taken from a bot under testing as they was added to it. The ones with (?) needs to be rechecked.
8rc1 under Debian Jessie/testing

BUG+query (CONFIRMED) (If in /query window) lcb> add word1 word321 | -darkbot-dev- Okay, lcb :) (and the entry is correctly parsed to info2.db || FOR DEL DELETE FORGET and REMOVE: <lcb> del word1 word321 | -darkbot-dev- lcb, shrug (the topic/description remains in info2.db) . NOTICE: this bug also affects Database Management commands: DISPLAY, FIND, DATASEARCH, REPLACE, TELL and [ABOUT] || 2 BE checked more query commands aside from data administration

BUG+limited+chars (?) Check why at one topic/description some words are missing at the end. (Truncated?...why, how? needs to be reproduced). 2 be checked better.

BUG+google Search Google unresponsive

BUG+raw (?) From /query -> !raw privmsg #darkbot :test from query -darkbot-8rc1- lcb, shrug

BUG+idle (?) commented+anti_idle by // #undef ANTI_IDLE stopped "This" every 5 mts during (during 20 mts). Uncommenting ... = No more "This". Make sure if doesn't happen again... if so run it in debug mode and trace it.

BUG+dhave_config_h (?) ... on $ make -- deebian jessie on 3.7.10-antix.5-486-smp

BUG+check-seen (?) MAX_LASTSEEN 604800 and SEEN_REPLY - looks like not functioning

BUG+check-dbtimers (?) (alarm clock) it seems not working. in fact there is no more #define DBTIMERS but only DEFAULT_DBTIMERS_PATH

BUGcheckcommandsprivate 2B checked all commands only working in /query and in chan

[Team Purple bot]

On Wed, 19 Feb 2014 14:43:32 +0000 "Luiz Castelo-Branco"
luizcb@users.sf.net wrote:

[bugs:#18] Reminder of several bugs on 8rc1 under debian testing

That's one reason to use a proper issue tracking system, then I wont
need to be reminded. B-)

Hmm, you said you are tracking these with a Darkbot? We don't need to
re invent issue tracking systems. What we could do is to add an
interface to existing issue trackers to Darkbot. I was working last
week on a script to migrate issues from a Redmine tracker system to SF's
Allura (so yes, I know what Allura does, I have a copy installed at
home, to answer a question from your last email). So I already have
code for dealing with those two systems.

Having a quick look at our current web site wrappers, we basically have
web page scrapers written in C. Web page scraping is fragile, and that
can be seen in our google support having broken in the past, and now
being broken again. Each time one of the handful of web sites we
scrape changes their web pages, we would need to fix the scraping
function. This is why things like REST, SOAP, and JSON where
invented. Some web sites publish a stable API that can be used over
HTTP to access their functions directly instead of trying to scrape
details from ever changing web pages. It would be better if we used
those sorts of API.

Allura and Redmine at least have published REST + JSON API to get to
most of their functionality. That made it easy to write my migration
script. Allura has 500 error code issues at the best of times,
sometimes it gets worse. So my script tries to work around that.

I initially looked for a C library, but the one I had my eye on didn't
actually support REST or JSON yet, but had those as a TODO item. It
would not be suitable for use in Darkbot though. Too many other
required libraries. So I next looked for high level scripting language
solutions. Lua is my current favourite scripting language, and I found
a suitable REST + JSON Lua library, so that's what I used for my
migration script.

Darkbot doesn't have Lua, but I think it would be a good idea to add
it. Adding a scripting language to Darkbot makes it easy for users to
extend the functionality, and if we convert things like google and
weather to that scripting language, then people can use them as
examples. Then it would be easy enough to use parts of my migration
script as support for Allura and Redmine ticket systems. We could even
convert the math stuff to just pass maths to Lua and let it deal with
that. It would give us a much more sophisticated maths function,
essentially for free. Lua is well sandboxed, could even let ordinary
IRC users write short scripts.

I'm not gonna try to sell you on Lua specifically right now, except to
say that it's what I would choose coz I really like it, it has a lot to
offer, and I've already added Lua scripting to two other projects.
It's something to think about later, more important stuff to do first.

--
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.

[onefang]

This is how worn out I am this week. lol

I was replying to the email notification of this ticket. Didn't realise that was gonna be a reply to a ticket, so most of that is not really relevant to the ticket, but just gonna leave it here anyway. I'll sort it out after I get some rest.

In case you are wondering, Allura matched that email I used to the bot used for Team Purple, coz at the moment while the Team Purple projects are being setup and tested, mostly by me, the bot's email address is one of mine. So the above reply is actually from me. Isn't it fun when lots of things go wrong at once. B-)

[Luiz Castelo-Branco]

David, I put it here to remind myself and inserting it the proper way in near future in case we need those. Knowing you are working on a diff version and not 8rc1 this only would be helpful in case those issues are still open on that particular version (added) as I don't see those particular issues mentioned anywhere :)
Btw, David, as of today we still need to be cautious on whatever we do/insert/change in the project because Allura issues are still ... under testing.
Just now...
"
<ctsai-sf> lcb: yes, it is. It's relatively stable, but the fix in place currently is just a stopgap while the team continues to test and investigate for the root cause.
"

[onefang]

SF's bug system seems to be mostly working fine now. You can split these into separate bug reports after testing them on 8rc4 from git HEAD.

[onefang]

BUG+check-dbtimers (?) (alarm clock) it seems not working. in fact there is no more #define DBTIMERS but only DEFAULT_DBTIMERS_PATH

This is covered in [#14]

[onefang]

BUG+google Search Google unresponsive

This is covered in [#3]

[onefang]

BUGcheckcommandsprivate 2B checked all commands only working in /query and in chan

This is covered in [#24]

[onefang]

Some of these got fixed already, at least one is already a different bug report. Could you go through these and post any remaining bugs as separate bugs please?