Okay, I saw php7.1-mysql and just wanted to make sure you were aware.

I know that php7 is not supported. I mentioned that I switched php to 5 version

Particularly, this does not reproduce against the upstream. All patches can be re-run in order with ./bin/storage upgrade --no-quickstart --namespace ..., and we do this somewhat regularly. This process runs cleanly:

(Note that this kind of requests are normally not supported - see Support Resources. This is not likely a bug in Phabricator).

The order of stopping/starting daemons/webserver isn't important, as long as both are down during the upgrade.

I don't understand what that information has to do with this ticket.

In T11124#179972, @chad wrote:

On your local install or on Phacility test instance?

On your local install or on Phacility test instance?

In T11124#179970, @chad wrote:

You can either point Diffusion in your test instance to the URL of your SVN repository, or if it's behind a firewall and you can't, you can zip it up and add it to the Files area on Phacility and we can manually retrieve it for you.

You can either point Diffusion in your test instance to the URL of your SVN repository, or if it's behind a firewall and you can't, you can zip it up and add it to the Files area on Phacility and we can manually retrieve it for you.

In T11124#179967, @chad wrote:

We need the repository, not the database.

We need the repository, not the database.

I've already import the database dump file. The backup.sql.gz file is the result of ./bin/storage dump.

In T11124#179963, @chad wrote:

Google and Stack Overflow are going to be better resources for things like this, and we're not unfortunately. At least with those sites you can give specific details about what system you have and what you're trying to do, and can get the most up to date answer. All we're going to do here is the same thing, and charge you for our time. That's not great for anyone. :(

Google and Stack Overflow are going to be better resources for things like this, and we're not unfortunately. At least with those sites you can give specific details about what system you have and what you're trying to do, and can get the most up to date answer. All we're going to do here is the same thing, and charge you for our time. That's not great for anyone. :(

We don't offer this service under free support.

In T11124#179960, @chad wrote:

Its up to you to provide us a reproducible bug report under "free support". If you need us to do these steps for you, we'd be happy to, but we charge $1,500 an hour for this.

Its up to you to provide us a reproducible bug report under "free support". If you need us to do these steps for you, we'd be happy to, but we charge $1,500 an hour for this.

In T11124#179958, @chad wrote:

If you're willing you can just import the whole thing into the private test instance and we can inspect it from there.

If you're willing you can just import the whole thing into the private test instance and we can inspect it from there.

In T11124#179954, @chad wrote:

If you can isolate the bad commit and upload a version we can inspect on a test instance on Phacility, we can troubleshoot it further.

• http://phacility.com/
• Click "Try Free"
• Sign up
• Launch a "Test Instance"
• Report back to us if it does not import there.

This isolates any issues with your local copy of Phabricator vs. our hosted platform. It also allows us (with your permission) to privately inspect bad commits for underlying issues.

If you can isolate the bad commit and upload a version we can inspect on a test instance on Phacility, we can troubleshoot it further.

I upgrade Phabricator today.

Thank you. We will upgrade this weekend and report back.

Your versions above are over a year old. Sorry for not catching that sooner.

We don't support old versions of Phabricator. Per documentation we require all bugs and support requests be performed with a current version.

I've read through this article and I am unable to determine what the next step should be. I've already used the repository tool to reparse the bad commit but new commits all go into the same state. One thing to note, my version of the repository tool does not have an --importing flag.

https://secure.phabricator.com/book/phabricator/article/repository_imports/

https://secure.phabricator.com/book/phabricator/article/support/

I created the task, then changed the tags manually (selecting only the tags I felt necessary - also removing the BUG tag). Seems I may have found a bug with the bug tracker. ;)

That is, if you go to the Diffusion workboard, we give you a generic create form instead of a choice between the various normal create forms, currently.

You can file stuff without those tags from workboards, and maybe "Support Request" just got caught in the crossfire of typing every possible tag, so that's a legitimate-albeit-unusual pathway here. But I wouldn't expect the short-lived "New Support Request" form to be accessible any longer.

This tracker is for bug reports and feature requests, and we're surprised you were able to file something without either of those tags.

How did you file this task?

I don't remember seeing that pink banner at the top, if I had I would have emailed first assuming $1500 an hour cost was an error :)

This is the UI you saw, right? Is there any way we could make this more clear?

In T11095#178721, @epriestley wrote:

Sorry for the delay, we're mostly Pacific Time here so this was filed around 3AM for us.

Before we can continue, can you please confirm you intended to file a $1,500/hr support request?

Sorry for the delay, we're mostly Pacific Time here so this was filed around 3AM for us.