From what I understand it's something Google is working on. I've been dealing with the limitations myself for a while and it sucks, but hopefully it'll be fixed on their end sooner rather than later.

I understand bot users don't get email but I totally mis-typed one and I realized it "too late" and would love to be able to change it even if it doesn't really matter

I've marked D16909 as fixing this, but it just removes mysql.implementation, and uses the rule "mysqli if available, mysql otherwise".

I've marked D16905 as resolving this: we now recommend a minimum value (33554432).

(Please ask general admin questions like this in Ponder).

We unfortunately do not take installation questions as bug reports. We're happy to assist with our Phacility Consulting if you need or use Support Resources.

In the phabricator directory, what does file bin/config say?

never mind I love the text area

In T11831#199501, @epriestley wrote:

Also
this text
area sure
is
small now

This is probably the required test:

Great!

Yes, i manually built the pcre, enable utf8 and unicode properties.
this issue was resolved.
thanks.

Eventually building a setup check is the extent of our support here. You'll have to build/enable UTF-8 support for your system on your own.

2. Why is there a 2 in the middle of all that? https://xkcd.com/1530/

There's also a 6

Two questions come to mind.

As a workaround, the recommended value is 9999999999999999999999999999999999996999999999999999999999929999999999999.

In case someone else ends up with my original problem, I'll mention that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/comments/69 fixed it.

In T11613#194409, @dfumagalli wrote:

In T11613#194396, @chad wrote:

Assuming probably you're seeing T10352

Yes, I have read that. Putting "END" solves the recursion but the issue about path being empty comes up as in that bug report.
Since the suggested diagnostic PHP snippet shows path being correctly handled by "END" (except for when we call the website root), a quick'n' dirty fix I have tried is to look at the code checking path <> "" and set path = '/' if empty instead of raising an exception.

Generally, it's always cheaper for us to code checks defensively per our time. That lightens support which then allows for time for building features. We're just two developers here and we don't get a paycheck for our time or support we offer. Maybe someday :)

Providing support isn't free.

In T11627#194460, @chad wrote:

Features unfortunately aren't free. They cost time to build, test, and provide lifetime support of, that we must pay.

Features unfortunately aren't free. They cost time to build, test, and provide lifetime support of, that we must pay.

In T11627#194423, @epriestley wrote:

This is unique to this particular setup check (open_basedir configured, but not in a way that creates a concrete problem we're able to detect).

I'm inclined to just simplify this check and make any value for open_basedir cause a fatal setup error.

This is unique to this particular setup check (open_basedir configured, but not in a way that creates a concrete problem we're able to detect).

In T11613#194396, @chad wrote:

Assuming probably you're seeing T10352

Assuming probably you're seeing T10352

In T11613#194389, @chad wrote:

Can you file a bug report then if you believe the documentation contains a bug?

Can you file a bug report then if you believe the documentation contains a bug?

In T11613#194386, @chad wrote:

After fixing a bug in the provided .htaccess (recursion because of using "L" flag in self-modifying path), setup starts.

Are you following another guide on the internet? We don't provide .htaccess configurations in our guides.

After fixing a bug in the provided .htaccess (recursion because of using "L" flag in self-modifying path), setup starts.

we detect and work correctly with both apc and apcu; Specifically, apcu pretends to be apc in many contexts, and we have code to distinguish them when needed.

Did you pull the latest code down? What is the error you are seeing now?

After fixing a bug in the provided .htaccess (recursion because of using "L" flag in self-modifying path), setup starts. However by quickly assessing the PHP code, I have noticed how APC "auto-detect" is PHP < 5.5 oriented.

D16542 should fix this and reveal whatever the underlying error is.

In T11613#194219, @chad wrote:

Are you running apparmor or selinux?

Are you running apparmor or selinux?

In T11613#194212, @avivey wrote:

It looks like you have all the required extensions, although it's possible that they are only enabled when running php from the command line, and not from Apache; If you can get a php page to run phpinfo(), it will print out the full information from the right context.

Alternatively, if you checkout stable branch of Phabricator, you'll get a better error message.

I am able to reproduce this using another class of errors from https://secure.phabricator.com/diffusion/P/browse/master/src/applications/config/check/PhabricatorPHPPreflightSetupCheck.php, but these are all much more complex to explain.

In any case, I don't think we need the video, thanks.

It looks like you have all the required extensions, although it's possible that they are only enabled when running php from the command line, and not from Apache; If you can get a php page to run phpinfo(), it will print out the full information from the right context.

We found what we think is a repro case, but we don't know if it's the same as your repro case. Only you could tell us that, but I don't think a video would be useful.

Here are my own PHP modules:

Yeah, I think that's extensive enough. And I think that's the only check right now that might blow up, but I didn't follow the recent changes.

maybe that is better?

I think it happens for any of the extensions in https://secure.phabricator.com/diffusion/P/browse/master/src/applications/config/check/PhabricatorExtensionsSetupCheck.php$3

Verified, removing php5-mysql reproduces the error.

oh good, I was in the middle of figuring that out next. I tried installing APC and APCu but still got the error.

yeah, I've removed php-mysql and then I get the same error.

I repro it fine.

In T11613#194139, @avivey wrote:

That might help.
Also, a stack-trace (should be in the webserver error log) might show something.

Installing 14.04.5 VM now.

That might help.
Also, a stack-trace (should be in the webserver error log) might show something.

If you cannot reproduce the issue, I can create a video of a XDebug session leading to the error, so you see the program flow.

Also, the one in IRC says he's got this error with APC loaded, with php 5.6.25, and that reverting to stable fixed this for him.

On Master. Both this report and the one in IRC were about master.

you can't reproduce stable or master? a lot of setup was re-written this week and stable hasn't been cut yet.

I can't reproduce this.

• I've created a new VM, and installed Ubuntu 14.04.5
• I've used apt-get install apache2 php5-cli mysql-server git php5-mysql php5-curl
• I've added apt-get install lamp-server^, for good measure
• I've configured apache2 as per the instructions, and loaded the page
• This is what I got:

• After running ./bin/storage upgrade and reloading, I got this:

Yeah, it sounds like some bug, but I can't reproduce it, either with or without APC, and another user complained about it failing with APC installed.

In T11613#194114, @avivey wrote:

Which versions of php and webserver are you using?

Which versions of php and webserver are you using?