As the title says, when there is a non existent path specified in include_path, activating open_basedir will generate the warning

Warning: open_basedir restriction in effect. File is in wrong directory in "xxxxxx.php" on line XX

This warning will not appear if the invalid path does not start with a slash.

e.g. include_path = ".:asdf/asdf:/usr/local/lib/php" will not produce warning when open_basedir is enabled but will produce warning when include_path = ".:/asdf/asdf:/usr/local/lib/php"

note the /asdf/asdf is the non-existent path.

I understand that by removing the non-existent path, the error will be gone, however I think the warning should not have appeared especially when it complains about open_basedir and not about the include_path itself which will cause confusion.