Some applications have been around longer than Phabricator has been a platform, fwiw. Renaming them is not an insignificant task (and very disruptive).

What specific modifications are you interested in making to the messages?

We are having the same issue with one of our Mercurial repositories. This particular repository has 206 branches: 14 open, 192 closed. When a new commit is pushed to this repository, the repository update task is spawning an hg log process for every branch, causing high CPU. This process is repeated every 15 seconds for several hours.

ah ok, then I'll have to wait to get the KDE instance updated. Thanks. From my POV, this can be closed then.

Starting about ~3 weeks ago, you can "rename" them, that is - change the text on the menu, either for yourself or (As an admin) for everybody - see https://blog.phacility.com/post/8/the_new_home_menu/.

We painfully craft all our own javascript.

I'm making some amount of progress here, although I've only made it slightly past "run SSH in a loop" so far.

I meant, are there any external javascripts used with Phabricator, but nevermind. Thanks for your help!

This sounds like a great improvement for the use cases that I am interested in! Thanks!

Worth mentioning is that you can query for exact(username) to get a dashboard for only individual reviews, but this is a partial solution; there's no way to get a dashboard for "all my stuff, except stuff I've explicitly said I don't care about".

This task has meandered a bit, but the current behavior is this:

@beng pointed out this resource for future use: http://cldr.unicode.org/

I'm just trying to understand the feedback. There are points that come very close to "redesign badges" to which I'm like years away from doing, if ever.

I'm fine with just declining to implement that, it just seems like something we should fix if we're calling it a bug.

Why do we need T10698 specifically? Seems overkill.

Darn race condition.

Yep, this is no longer a problem with the new audit bucketing. 🏅

Yeah, that looks like it's ignoring the encoding, and considers the whole argument as a parameter name.

I think there is an issue with appliction/json data. If I Provide the data with a valid api.token Conduit returns:

I think there's a way to send raw json using curl, but if you go to the conduit app and invoke it, you get an example at the bottom of how to repeat the request using arc or curl.
It looks like curl is using some http-query-magic way to encode the request. You can maybe try -d <raw json> with -H 'Content-Type: application/json' instead, it might also work.

Well, I have to use curl. Is there a difference in the way how conduit parses the args?

I think it was historically possible for third-party code to read custom config, but not possible for them to add new settings until D16928 (Nov 2016), which might be why we don't warn about bad values. Should be fine to do so now, though.

Well, it looks like we didn't expect users to set encoding from arc:

Closing, because it's probably not a bug. Comment again if you think it is. But if you do, a smaller file would help debugging.

Wikimedia ran a vote to find which problems are the most annoying to developers (not limited to problems with Phabricator) and this one was the most voted by far, with over one third of the participants voting on it.

Actually I think this is my fault, I was providing the offset in Unicode characters, not in bytes.

Looks like search and edit are implemented, but not awards. Awarding a badge through conduit seems nice to have? but I don't see any requests for it, so not sure it's worth holding up unbeta.

I think we're going to end up trialling it with one project for now (just in case there's some prototype stuff that we're using on the self-hosted instance that we run into on Phacility), and then probably manually move other things over if we decide to pull the switch (just because we'll have done work on both at that point).

This has been implemented and in use for a while, so closing and will finish up smaller tasks in backlog.

Just need to tarball it up and upload it to us, and we'll do the import when your ready.

Is there any way of getting Calendar enabled on a Phacility instance? We're looking to migrate from a self-hosted instance, and it's one of the applications we use to organise meetings, etc.

Is there an import process available for customers of the Phacility free tier? We have a reasonably complex, self-hosted set up, and we're looking at Phacility but currently have no easy way of migrating the data.

Gonna just close this since I don't think the issues were really that great and I got most of the major bugs this week. I'll pick away at some of the others.

I think we've ended up in a fairly stable place here, and remaining work generally has existing tasks motivating it in terms of features (like T10967 for reviewers, T10574 for acceptance rules, T2543 for revision states, various tasks for inlines, T9713 for commit message parsing). Obsoleted transaction types also need migrations (but they should happen alongside the migrations that other features require so we're minimizing the number of weeks with migrations that need special planning) and this dumb mess got left in PhabricatorModularTransaction.php and will probably be there for an uncomfortably long time:

externally linked?

So all javascripts (including externally linked) are under Apache 2.0?

closed per user request

@epriestley Please close this task (I can't).

Ohh, that is embarrassing... Now I found where to the limit can be changed. Thanks for the help.

ooh, sorry. I believed that the linked task is an example. Ok, there is a ticket for it. Subscribed.

See Planning.

I am getting the same error with

arcanist c58f1b9a2507488b2152473dd1f0bbc7e99c09c1 (29 Apr 2016)
libphutil 0709cd5cfc2616c29104387de6dde3de1db7fa32 (2 May 2016)

and

svn, version 1.9.4 (r1740329)
   compiled Apr 28 2016, 01:15:57 on x86_64-apple-darwin15.4.0