Okay thanks for your answer. So if i used audit.Query to get (for example) audit statuses etc.. I have to wait that diffusion.commit.search implements all functionnalities?

No.

Is it possible to unfreeze audit.query if diffusion.commit.search is not returning enough informations to replace audit.Query?

Thanks! Will check.

I think this is worth acting on (by changing MySQL sandboxing or config sandboxing or some combination of things) if:

Oh, I don't think anyone should ever be running unit tests with actual production credentials. You should assume that arc unit will immediately escape all sandboxing and destroy all the data it can touch, then run BENCHMARK() for an hour and then crash the server. But you should assume arc unit will do this even if it is "supposed" to be Totally Seriously Sandboxed 100% into SQLite.

@aurelijus, D18111 is landed now in HEAD if you'd like to test this. Let us know if you have any issues.

Philosophically I'm happy with that. Just as an exercise though, I came up with:

I can't really come up with a problem that would prevent, even theoretically -- do you have a specific scenario in mind offhand where some kind of MySQL configuration could mask a test failure locally?

That makes sense. Probably not much to be done for it (other than potentially doing a config override for maniphest.priorities prior to running ManiphestTaskTestCase).

This is semi-intended, because we have to pull a lot of config (like mysql.host) from your local install for things to make sense: we can't create test fixtures if we don't know how to connect to the database.

Oh, this doesn't isolate things because they're on different databases, and thus we establish different connections. The daemon insert does not happen inside a transaction.

Should not, but looks like there are. I updated to master now, and it works now.

I used the current version, but there should be no meaningful changes to this behavior between your version and HEAD.

That's weird since I exactly did the same with my version from above. Did you used the current or my version? Or should I update and try if I can reproduce it at the master?

I can't reproduce this. Here's what I did:

Thanks :)

Version infos are:

phabricator
    0d1654446be6de43b2bd12fcc247db0dc1a46464 (Sat, Jun 10) 
arcanist
    c04f141ab0231e593a513356b3832a30f9404627 (Fri, Jun 9) 
phutil
    74a1350416eb2df825c2315d6519bee03f77bee9 (Mon, Jun 5)

How did you generate this diff?

Thanks @epriestley, that fixed it indeed!

I believe this should now be resolved in HEAD of master. Let us know if it doesn't work for you or if you're still seeing issues after upgrading. Thanks for the report!

This is not a configuration problem, and you can't fix it by changing configuration. D18119 should fix it.

Beautiful. Sorry for not finding that.

Presuming resolved by T12757 (May 25).

Sorry, just pulling that out. 4d2c7e4d3d5d61e34b7e2af3df0e901d89d29433

Version?

See also T4124 for another Solaris issue.

(Specifically, if you update this bug should be resolved.)

Please don't forget to update Phabricator before filing bug reports.

With only those fields:

{
  "data": [
    {
      "name": "Open",
      "value": "open",
      "special": "default",
      "closed": false
    },
    {
      "name": "Resolved",
      "value": "resolved",
      "special": "closed",
      "closed": true
    },
    {
      "name": "Wontfix",
      "value": "wontfix",
      "closed": true
    },
    {
      "name": "Invalid",
      "value": "invalid",
      "closed": true
    },
    {
      "name": "Duplicate",
      "value": "duplicate",
      "special": "duplicate",
      "closed": true
    },
    {
      "name": "Spite",
      "value": "spite",
      "closed": true
    }
  ]
}

Maybe just include name, value, closed and special?

Similar example for new maniphest.status.search. I'm happy to drop any of these fields if you think we won't need them (prefixes and suffixes leap to mind).

The behavior of arc land is complex. You can look at the source for the details, or run arc land --trace to see which commands it executes.

By headless strategy you mean the squash and merge one ?

Per @chad's link, PholioMockEditor->buildMailBody() does some improper stuff where it explicitly sets rendering targets and adds raw sections to the mail body.

Prior to October 2015, this flag only had an effect under git. This is why it says "Supports: git".

The version of arcanist used is the one packaged in debian.

T12776#225510

999.99999.9% sure we have this tracked "somewhere"

(We also likely have a similar problem for hg that D18105 won't fix, and can't use the same strategy there since hg grep has no -f flag or equivalent.)

Note that D18104 is not retroactive, so existing feed stories aren't expected to change after upgrading. New feed stories published after picking up the fix should show "alice committed <commit>" as the title again, though.

See also T7339 and T5554. But the approach we are generally taking there is "wherever possible, use a method where locale configuration is not relevant", which is consistent with using -f -.

This works properly on my local machine (OSX) so it's some kind of Ubuntu UTF8 CLI thing.

Herald rule:

Please read and follow Contributing Bug Reports if you think you've found a bug in Phabricator. Specifically all bug reports require steps that reproduce for the upstream developers. If you have general questions about Phabricator administration, please use Conpherence or Ponder. Thanks!

This is because of the synthetic comment from Lint near line 108 of DiffusionHistoryController.php, not because of the comment in the screenshot.