If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Can't use an undefined value as an ARRAY reference (Bugzilla/User.pm:773)

RESOLVED INVALID

Status

()

Bugzilla
Bugzilla-General
--
critical
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: glob, Assigned: glob)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
when viewing bugs with an empty cc list:

Can't use an undefined value as an ARRAY reference (Bugzilla/User.pm:773)
(Assignee)

Comment 1

3 years ago
Created attachment 8433202 [details] [diff] [review]
1019476_1.patch
Attachment #8433202 - Flags: review?(dkl)
Note that only BMO's Bugzilla::Bug->cc contains the line:

 $self->{'cc'} = undef if !scalar(@{$self->{'cc'}});

But upstream bugzilla does not, and $self->{'cc'} will always be defined. Git blame does not enlighten as to why this change is in BMO but not upstream.
Comment on attachment 8433202 [details] [diff] [review]
1019476_1.patch

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

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

Updated

3 years ago
Flags: approval?
(Assignee)

Comment 4

3 years ago
(In reply to Dylan William Hardison [:dylan] from comment #2)
> Note that only BMO's Bugzilla::Bug->cc contains the line:
>  $self->{'cc'} = undef if !scalar(@{$self->{'cc'}});
> But upstream bugzilla does not, and $self->{'cc'} will always be defined.
> Git blame does not enlighten as to why this change is in BMO but not
> upstream.

that line was removed by bug 819330 (bugzilla 4.4), which is why it's still present on bmo (bugzilla 4.2).
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: approval?
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.