I saw it as two subproblems

1. Difficulty remembering whether lint or unit failed
2. Difficulty remembering excuse for lint failures in particular.

(See general churn in T9905, T9908, T9132.)

Oh -- are you creating these from the workboard? Never mind, in that case.

I don't understand the difference between this and T9936. Aren't they aiming to solve the same problem (difficulty remembering what failed during arc diff when running arc land)?

The expectation is that you'll remember what the issue was, since arc diff printed the specific problems earlier and you already explicitly confirmed that you wanted to continue despite the issues.

https://secure.phabricator.com/T9935 Thank you!

I really thought I filed as a Feature request. I will reopen there.

Of course I would double check it this time, and really try the last diff send in the production environnement where i get the problem, to be sure it don't break the world like last time.

@epriestley, do you see it can be easy enough so I can to submit some patch ?

I've never used EC2 and I'm not entirely sure what's involved with it. There are a few things I'd like to try before doing this, one being a reinstall on the local server. If that doesn't work, I will look into EC2.

(If your time is valuable, we're happy to shoulder the entire burden of building a reproduction case and fish around for environmental problems at our consulting rate; see Consulting.)

Or, let me clarify: if you give us a running VM in EC2 with root credentials, that's useful.

If I could provide a virtual machine image of some sort that shows the issue, would that be useful?

Can you give us root SSH access to a server on the public internet where this issue is reproducible?

Can you provide more details on exactly how this is a bug?

This does not describe a bug with Phabricator. For help filing a bug, see Contributing Bug Reports.

Seems convoluted to recreate the ~/.arcrc each time I change the template. Moreover, when the config is modified directly by arc (arc alias for example), it will modify the generated ~/.arcrc. So I'd have to (remember to) copy these additions back to the template.

In would be convenient, but note you could have a more generic problem here: how to store all your credentials. Solutions like Vault could help in this case.

What was the push operation you tryed to do ? By default phabricator prevents dangerous changes (like history rewrite or other operations in which you have to use --force) but this can be disable in repository preferences..

Sorry to disturb everybody, and I find the reason that, in my hooks of repo, there is also one pre-receive hook script.

Are there any more details that might be useful?

OS: Fedora 22, kernel 4.2.5-201.fc22.x86_64
PHP: 5.6.15
Webserver: Apache 2.4.17
svnserve: 1.8.13
mysql: Ver 15.1 Distrib 10.0.21-MariaDB, for Linux (x86_64) using readline 5.1

Can you give us more details on your system so we can try to reproduce? OS / PHP / Webserver / SVN / etc

Ok, sorry. I'll take a look at the support options. Thanks!

This does not describe a bug in Phabricator. See Support Resources and Contributing Bug Reports.

Sorry didn't mean to tag this as "Bug Report", more like a "Question". Not sure how I can edit that :/