The default bug view has changed. See this FAQ.

[Oracle] When running checksetup.pl for the first time using Oracle as DB server, you get an "uninitialized value" warning

RESOLVED FIXED in Bugzilla 4.2

Status

()

Bugzilla
Installation & Upgrading
--
minor
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: Frédéric Buclin, Assigned: Frédéric Buclin)

Tracking

4.0.3
Bugzilla 4.2
Bug Flags:
approval +
approval4.4 +
approval4.2 +

Details

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
When running checksetup.pl for the first time using Oracle as DB server, you get an "uninitialized value" warning, because data/params doesn't exist yet:

  Use of uninitialized value in subroutine entry at Bugzilla/DB/Oracle.pm line 62

This line 62 is:

  max(Bugzilla->params->{'maxattachmentsize'}, MIN_LONG_READ_LEN) * 1024

As data/params doesn't exist yet, maxattachmentsize is undefined and max() complains. This warning is present since Bugzilla 4.0.3, see bug 701350.
(Assignee)

Comment 1

4 years ago
Created attachment 734223 [details] [diff] [review]
patch, v1
Assignee: installation → LpSolit
Status: NEW → ASSIGNED
Attachment #734223 - Flags: review?(dkl)
Comment on attachment 734223 [details] [diff] [review]
patch, v1

Review of attachment 734223 [details] [diff] [review]:
-----------------------------------------------------------------

r=dkl
Attachment #734223 - Flags: review?(dkl) → review+
(Assignee)

Updated

4 years ago
Flags: approval4.4+
Flags: approval4.2+
Flags: approval+
(Assignee)

Comment 3

4 years ago
Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/trunk/
modified Bugzilla/DB/Oracle.pm
Committed revision 8615.

Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/4.4/
modified Bugzilla/DB/Oracle.pm
Committed revision 8548.

Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/4.2/
modified Bugzilla/DB/Oracle.pm
Committed revision 8209.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.