Process Markdown-style headers in Remarkup

Summary:
Markdown supports a header style where headers are underlined with `=` or `-`. Support this in Remarkup as well.

I made this the text target rendering style too, since I think it looks a little nicer. Ref T2849.

Test Plan:
Added a bunch of unit tests.

{F42635}

Reviewers: btrahan, jevripio

Reviewed By: btrahan

CC: aran

Maniphest Tasks: T2849

Differential Revision: https://secure.phabricator.com/D5854
Parse most `[name](href)` Markdown-style links in Remarkup

Summary: Markdown has `[name](href)`-style links which we currently don't parse because they can occur naturally in discussions of source code (instead, we support Mediawiki-style links). Apply a few heuristics to reject likely accidental matches and support reasonable forms of this style. Ref T2849.

Test Plan: Added unit tests.

Reviewers: btrahan, jevripio

Reviewed By: btrahan

CC: aran

Maniphest Tasks: T2849

Differential Revision: https://secure.phabricator.com/D5857
Allow PhutilDeferredLog to fail more quietly

Summary:
We've hit a couple of issues with the exception PhutilDeferredLog throws when used in the Phabricator access log. In particular, it is thrown at an awkward time, when the request is already complete. It is also thrown from an awkward place in the stack, where we've already unwound everything and are calling `__destruct()`. It also isn't especially important.

Allow it to be degraded into a log message instead. The next diff will apply this degradation in Phabricator.

Test Plan: Unit tests; see next revision.

Reviewers: btrahan

Reviewed By: btrahan

CC: aran

Maniphest Tasks: T3144

Differential Revision: https://secure.phabricator.com/D5874
Allow comments in multi queries

Test Plan:
  print_r($conn->executeRawQueries(array(
    "SELECT 1 -- comment",
    "SELECT 2",
  )));

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin

Differential Revision: https://secure.phabricator.com/D5884
Re-execute multi-queries if some query fails

Summary:
If some query fails, all next queries are not accessible.

Also don't report correct queries not returning results as errors.

Test Plan:
  print_r(array_map('gettype', $conn->executeRawQueries(array(
    "SELECT 1",
    "DO",
    "DO SLEEP(5)",
  ))));
  // And other permutations.

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin

Differential Revision: https://secure.phabricator.com/D5900
Put a sigil on remarkip-code-block in PhutilRemarkupEngineRemarkupCodeBlockRule

Summary: Also modified few test cases.

Test Plan: I made the necessary changes, differential is loading diffs as usual. Let me know if I have done it correctly.

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin, AnhNhan

Maniphest Tasks: T3007

Differential Revision: https://secure.phabricator.com/D5888
Add missing parameter to strncasecmp()

Summary:
strncasecmp() takes 3 parameters, not 2. This worked in the general case because we usually do not set any headers, so we don't enter this comparison block. However, now that we set `User-Agent` from OAuth it is complaining in the logs.

  [13-May-2013 16:51:28] WARNING: [pool www] child 28977 said into stderr: "NOTICE: PHP message: [2013-05-13 16:51:28] ERROR 2: strncasecmp() expects exactly 3 parameters, 2 given at [/core/libphutil/src/future/http/HTTPSFuture.php:172]"
  [13-May-2013 16:51:28] WARNING: [pool www] child 28977 said into stderr: "NOTICE: PHP message:   #0 strncasecmp(User-Agent, Expect) called at [/core/libphutil/src/future/http/HTTPSFuture.php:172]"
  [13-May-2013 16:51:28] WARNING: [pool www] child 28977 said into stderr: "NOTICE: PHP message:   #1 HTTPSFuture::isReady() called at [/core/libphutil/src/future/Future.php:40]"
  [13-May-2013 16:51:28] WARNING: [pool www] child 28977 said into stderr: "NOTICE: PHP message:   #2 Future::resolve() called at [/core/libphutil/src/future/http/BaseHTTPFuture.php:231]"
  [13-May-2013 16:51:28] WARNING: [pool www] child 28977 said into stderr: "NOTICE: PHP message:   #3 BaseHTTPFuture::resolvex() called at [/core/phabricator/src/applications/auth/controller/PhabricatorOAuthLoginController.php:55]"
  [13-May-2013 16:51:28] WARNING: [pool www] child 28977 said into stderr: "NOTICE: PHP message:   #4 PhabricatorOAuthLoginController::processRequest() called at [/core/phabricator/webroot/index.php:84]"

Test Plan: Verified strncasecmp() behavior.

Reviewers: btrahan, chad

Reviewed By: btrahan

CC: aran

Differential Revision: https://secure.phabricator.com/D5917
Fix `[x]` in simple table markup

Summary:
This `*` should be a `+` since we want to match //something//.

Fixes `[x]` in a simple table, for any `x` which is not a link.

Test Plan: Added unit test, made it pass.

Reviewers: btrahan

Reviewed By: btrahan

CC: aran

Differential Revision: https://secure.phabricator.com/D5934
Move PhutilArray constructor one level up

Summary: PHP allows changing constructor signature so I see no reason why constructor shouldn't be directly in `PhutilArray`.

Test Plan: Unit tests.

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin

Differential Revision: https://secure.phabricator.com/D5935
Fix calculation of spritesheet hashes to use relative paths

Summary:
When a user generates sprites, we hash all the inputs to figure out what we actually need to regenerate. Normally (i.e., on my machine), this works fine.

However, part of the hash is the absolute path of all the input images, so my machine hashes in `/Users/epriestley/phabricator/path/to/sprite.png`, and then @chad regens them and gets a hash of `/Users/notchad/phabricator/path/to/sprite.png` instead, or whatever. The hash comes out different so every manifest and sheet gets regenerated.

Instead, hash the //relative// path -- e.g., `path/to/sprite.png`. This keeps the path the same across machines and means that only sprites which have actually changed will regenerate.

See also next diff.

Test Plan:
  - Before this patch: generated sprites in `phabricator/`, then moved `phabricator/` to `phabricator2/` and regenerated. Incorrectly, all sprites were regenerated.  - After this patch: generated sprites in `phabricator/`, then moved `phabricator/` to `phabricator2/` and regenerated. Nothing was regenerated.

Reviewers: chad, btrahan

Reviewed By: chad

CC: aran

Differential Revision: https://secure.phabricator.com/D5964
Add Filesystem::binaryExists()

Summary:
We use `which x` in various places; provide a wrapper which we might some day make work on Windows.

The motivation for this is twofold:

  - I want to commandeer D5670, which will involve another `which`. `which` is yuck.
  - Users hit issues with `svn`, `git`, etc., fairly often. It would be good to do a check after hitting an error in PhabricatorRepository so we can raise a very specific error message about "you do not have git in your webserver path, here is how to fix that".

Test Plan: Ummm... will use in next diff?

Reviewers: btrahan, vrana

Reviewed By: vrana

CC: aran

Differential Revision: https://secure.phabricator.com/D5968
Improve behavior of named anchor links

Summary: Fixes T3220. We currently don't handle `[[ #anchor ]]` very well in remarkup.

Test Plan:
Unit tests.

{F43706}

Reviewers: btrahan, chad

Reviewed By: chad

CC: aran

Maniphest Tasks: T3220

Differential Revision: https://secure.phabricator.com/D5974
Implemented phutil_utf8_is_combining_character().

Summary: Implemented phutil_utf8_is_combining_character(), which returns true if an input character is a combining character.

Test Plan: Unit test: testUTF8IsCombiningCharacter().

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin, AnhNhan

Maniphest Tasks: T2379

Differential Revision: https://secure.phabricator.com/D5981
Implemented phutil_utf8_combined().

Summary: A function which splits a given UTF-8 string into an array of characters without splitting the combined characters.

Test Plan: Unit tests.

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin, AnhNhan

Maniphest Tasks: T2379

Differential Revision: https://secure.phabricator.com/D6011
Provide the ability to set an alter-operation cost to PhutilEditDistanceMatrix

Summary:
In Arcanist, we currently price altering the edit operation so that strings like `(x)` vs `((x))` get analyzed as `isssi` instead of `issis` (that is, the first and last parens are highlighted as "new", rather than the first open and first close paren) which is better for human viewers.

Support this in PhutilEditDistanceMatrix.

Test Plan: Provided an alter cost in `arc` and ran the tests. They pass after this change.

Reviewers: btrahan, Afaque_Hussain

Reviewed By: btrahan

CC: aran

Maniphest Tasks: T2379

Differential Revision: https://secure.phabricator.com/D6013
Provide onboard optimizations for strings with similar prefixes and suffixes in PhutilEditDistanceMatrix

Summary: We can evaluate similar prefixes and suffixes in O(1). Provide this optimization within PhutilEditDistanceMatrix.

Test Plan: Ran unit tests.

Reviewers: btrahan, Afaque_Hussain

Reviewed By: btrahan

CC: aran

Maniphest Tasks: T2379

Differential Revision: https://secure.phabricator.com/D6014
Provide maximum comparison length onboard PhutilEditDistanceMatrix

Summary: After some maximum length, we bail out rather than compute the acutal edit distance because the time and memory complexity grows nonlinearly. Bring this check onboard PhutilEditDistanceMatrix.

Test Plan: Added and ran unit tests.

Reviewers: btrahan, Afaque_Hussain, ivane2004

Reviewed By: btrahan

CC: aran

Maniphest Tasks: T2379

Differential Revision: https://secure.phabricator.com/D6015
Fixing phutil_utf8_shorten().

Summary: Fixed phutil_utf8_shorten() to be combining character aware.

Test Plan: Unit tests. However, I think I may have not added enough test cases.

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin, AnhNhan

Maniphest Tasks: T2379

Differential Revision: https://secure.phabricator.com/D6025
Add Filesystem::resolveBinary to lookup full path to binary file in PATH

Summary:
Arising out of an issue with D6070, I noticed that `where` on Windows actually returns all of the entries in PATH that match, rather than just the first.  There's three places in the code that use `where` directly, one of which is in phutil for `Filesystem::binaryExists` (where the semantics don't affect it).  The other two cases exist in Arcanist; the one introduced by D6070 and one in the JSHint linter.

This adds a `Filesystem::resolveBinary` method which is aware of the semantics of `where` on Windows and `which` on Linux.  I'm recommending that code use this method to determine absolute paths to binaries in the PATH so that we don't encounter the same issue as occurred in D6070.

Test Plan:
Run the `resolveBinary` unit tests.  The other unit tests for Filesystem are failing on my Windows box, presumably because they're trying to do UNIXy things.

The other thing you can do is replace the explicit usage of where with `Filesystem::resolveBinary`, like the place it's used in D6070 and confirm that it works as expected.

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin

Maniphest Tasks: T3272

Differential Revision: https://secure.phabricator.com/D6077
Minor, fix a trim() issue with resolveBinary() on non-Windows systems.