Edit report at https://bugs.php.net/bug.php?id=65359&edit=1
ID: 65359
User updated by: spam2 at rhsoft dot net
Reported by: spam2 at rhsoft dot net
Summary: Unknown: Skipping numeric key 1 in Unknown on line 0
Status: Assigned
Type: Bug
Package: Session related
PHP Version: 5.4.17
Assigned To: yohgaki
Block user comment: N
Private report: N
New Comment:
yeah, introduce new things and let the broken untouched broken is the way of
PHP which leaded to all the troubles over the last 10 years - hence the real
bug is that the info wich script was called is thrown away before the
error_handler is raised and burry this problem with a new session_handler does
not solve it
*there must not* be any place inside PHP where the error-handler says "in
unknown" - it doe snot matter if the script has finished by raise the error,
the fact is that the REQUEST has a URL and the error handler comes after the
script was executed - so PHP has to store whereever the script path or fix the
error_handler that it shut's up if it has nothing helpful to say
Previous Comments:
------------------------------------------------------------------------
[2013-08-10 10:30:40] yohg...@php.net
> it is not possible to have request-uri
This one is workable option.
------------------------------------------------------------------------
[2013-08-10 10:25:48] yohg...@php.net
> what we need is *NOT* a new session handler beause numeric indexes are
braindead and so what we need is a clean error message
If I fixed the issue in current serialize handler, it will break apps.
Therefore, new one is needed.
The reason you didn't get the error message is it was slightly failed.
I cannot do anything but introduce new serialize handler.
------------------------------------------------------------------------
[2013-08-10 09:57:18] spam2 at rhsoft dot net
what we need is *NOT* a new session handler beause numeric indexes are
braindead and so what we need is a clean error message and *NOBODY* can tell me
that it is not possible to have request-uri and/or path of the script which is
executed and if this is the case why in the world are tese data thrown away
instead held in memory to give useful error messages
*OR* remove this idiotic warning from the code without forcing us to lower the
error_reporting
"in Unknown on line 0" is laughable and PHP should simply sht up if it has
nothing helful like file and line-numver to say - period
------------------------------------------------------------------------
[2013-08-10 09:41:15] spam2 at rhsoft dot net
> See intern...@php.net archive for details.
> It is under discussion now. If you would
> like to see this in released version, you
> should speak out now
i am not allowed to speak out on internals because the can not handle clear
words and prefers endless discussions in cas of proposed backward compatibility
changes and so i am blocked
however i do not understand the disussion - this is a bug and a regression
somewhere because we have since 10 years "error_reporting = E_ALL | E_STRICT"
and these messages are coming since the upgrade to PHP 5.4
------------------------------------------------------------------------
[2013-08-10 09:21:12] yohg...@php.net
Related to Bug #42725
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=65359
--
Edit this bug report at https://bugs.php.net/bug.php?id=65359&edit=1
