Project

General

Profile

Actions
Copy link

Bug #13676

closed

Feature #13446: Upgrade PHP from 7.4 to 8.1

PHP errors on services_dhcpv6_relay.php

Added by Reid Linnemann about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Reid Linnemann
Category:
DHCP Relay
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Force Exclusion
Affected Version:
Affected Architecture:

Description

Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/services_dhcpv6_relay.php:44
Stack trace: #0 {main} thrown in /usr/local/www/services_dhcpv6_relay.php on line 44
PHP ERROR: Type: 1, File: /usr/local/www/services_dhcpv6_relay.php, Line: 44, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/services_dhcpv6_relay.php:44
Stack trace: #0 {main} thrown
Actions
Copy link
 #1

Updated by Reid Linnemann about 2 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Reid Linnemann about 2 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Reid Linnemann about 2 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Jordan G about 2 years ago

still seeing this running 23.01.a.20221118.0600 but works with changeset added via system_patches

Actions
Copy link
 #5

Updated by Reid Linnemann about 2 years ago

Jordan Greene wrote in #note-4:

still seeing this running 23.01.a.20221118.0600 but works with changeset added via system_patches

Plus just hadn't gotten a merge of the CE codebase with the changes yet, that was done this morning so next build you see should include it Saturday, so the current build should be correct.

Actions
Copy link
 #6

Updated by Jordan G almost 2 years ago

still happening on 23.01.a.20221124.0600

Actions
Copy link
 #7

Updated by Jim Pingle almost 2 years ago

Jordan Greene wrote in #note-6:

still happening on 23.01.a.20221124.0600

What exactly is the error message now? It can't be identical to the original, if it still happens the line numbers would have to be different at least. Even on current plus snapshots the line in the original message couldn't generate this error now. If it is identical, perhaps something on that test system isn't being updated properly.

Actions
Copy link
 #8

Updated by Danilo Zrenjanin almost 2 years ago

  • Status changed from Feedback to Resolved

Tested against:

23.01-DEVELOPMENT (amd64)
built on Tue Nov 29 06:04:48 UTC 2022
FreeBSD 14.0-CURRENT

It works as expected. No errors.

I am marking this ticket resolved.

Actions
Copy link
 #9

Updated by Jim Pingle almost 2 years ago

  • Release Notes changed from Default to Force Exclusion
Actions
Copy link

Also available in: Atom PDF