How did you file this task?

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

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.

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.

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. ;)

Please let me know where I should file this request.

Thanks!

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

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

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.

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

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

Hello,

I upgrade Phabricator today.

The actual version is:

phabricator ad0562e15e38739c703294d7722b65cd78c1f96f (Thu, Jun 9)
arcanist c13e5a629535f460ca1a16d0bfe6d95f43b70b78 (Thu, Jun 9)
phutil 01d14978d08e87c8582d886bf712ea2e5310be45 (Thu, Jun 9)

The new commits still in the same status (Importing Commit...).

Can you help me?

Thanks.

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.

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.

Thank you.

How can I isolate one commit?

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#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.

I can import the whole repository that I am having bad commits. How I can export the repository to a zip file?

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#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.

I only need to know how do I export the repository. Can you help me?

We don't offer this service under free support.

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. :(

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. :(

Is it enough the database dump?

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

Please ignore the LDAP.zip file.

We need the repository, not the database.

In T11124#179967, @chad wrote:

We need the repository, not the database.

Do I have SSH access to the test instance?

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#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.

I am having a problem.

In the repository storage configuration I have this information: "No Local Working Copy"

On your local install or on Phacility test instance?

In T11124#179972, @chad wrote:

On your local install or on Phacility test instance?

On my local installation.

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