"Use of uninitialized value" message in kinoupdate

I just downloaded and installed what I think is the latest version of KinoSearchContrib under Windows Server 2003 (found it at http://foswiki.org/pub/Extensions/KinoSearchContrib/KinoSearchContrib.tgz)

After a whole bunch of work making it run under Windows, itl seems to be working okay except...

when I run kinoupdate I see the following error messages:

Use of uninitialized value in concatenation (.) or string at c:/fwiki/lib/Foswiki/Contrib/KinoSearchContrib/Index.pm line 228.

Use of uninitialized value in hash element at c:/fwiki/lib/Foswiki/Contrib/KinoSearchContrib/Index.pm line 228.

Use of uninitialized value in concatenation (.) or string at c:/fwiki/lib/Foswiki/Contrib/KinoSearchContrib/Index.pm line 228.

Use of uninitialized value in hash element at c:/fwiki/lib/Foswiki/Contrib/KinoSearchContrib/Index.pm line 228.

It appears that the indexing does not continue after those errors. Can anyone help ?

---

• I was working with Kino today (linux) and noticed this too. I didn't get a chance to dig into it yet. -- BenBomgardner - 26 Jan 2010
• Well, this is because in the function changedTopics the @changes arr is getting an extra empty member:

KinoSearch index files update
- to suppress all normal output: kinoupdate -q
+BenBomgardner  BenBomgardner   1264536362      3
+FoswikiSiteSkinNavigationTemplate      BenBomgardner   1264425961      3
+

I don't know the inner workings of this script or why this is occuring (the web/.changes file is OK...) but here's one way to fix it:

Line 228:

next if ( ( !defined($topicName) ) || ( $skipTopics{"$web.$topicName"} ) || ( $skipTopics{$topicName} ) );

This workaround seemed to work OK for me. -- BenBomgardner - 26 Jan 2010

I have filed a task for this at Tasks.Item8426.

-- AndrewJones - 26 Jan 2010