when trying to export records using the marc_export script we get 'Can't use an undefined value as an ARRAY reference at /openils/bin/marc_export line 386.'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.3 |
Fix Released
|
Medium
|
Unassigned | ||
2.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This likely affects all version of Evergreen, tested on 2.4 and 2.3.6, gmcharlt strongly suspects that it was introduced by b1e6cde52 (bug 1022582)
When trying to export records using the marc_export script we get 'Can't use an undefined value as an ARRAY reference at /openils/
Using diagnostics:
opensrf@test:/tmp$ cat /tmp/list_of_ids | /openils/
Subroutine section_pkg redefined at (eval 1496) line 4 (#1)
(W redefine) You redefined a subroutine. To suppress this warning, say
{
no warnings 'redefine';
eval "sub name { ... }";
}
Use of uninitialized value $required in string eq at
/usr/local/
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl will try to tell you the
name of the variable (if any) that was undefined. In some cases it cannot
do this, so it also tells you what operation you used the undefined value
in. Note, however, that perl optimizes your program and the operation
displayed in the warning may not necessarily appear literally in your
program. For example, "that $foo" is usually optimized into "that "
. $foo, and the warning will refer to the concatenation (.) operator,
even though there is no . in your program.
Use of uninitialized value $controller in split at
/usr/local/
Can't use an undefined value as an ARRAY reference at /openils/
Exports Attempted : 1
Exports Completed : 0
Overall Speed : 0
Total Time Elapsed: 0.116323947906494 seconds
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
As the one possibly responsible I'll look into this (hopefully) today.
I plan to try exporting some records using a 2.4.0 system using concerto and a 2.3.2 system using our local data. Both systems have the suspect branch applied.
Depending on what happens I'll pick out the changes introduced by the branch and repeat the test -- will update when I have some results.
Mark.