I think the scenario is:

Yeah, our thoughts are that full URL is easily available in your browser bar, and monogram is easily available in the crumbs. I use both. Is there a scenario where the browser URL bar doesn't work for you?

Oh, and D15263 was specifically to improve double-click behavior, although that was just me rather than external users (I double-click to select frequently).

@chad, you may have thoughts on this or remember related product stuff better than I do.

Yeah, I'm just going to merge this into T5505 since I think it's a subset of the first feature discussed there. This will probably be the major feature in the next iteration of Legalpad, since I think it's the most obvious thing we're missing:

Users @techhelpuk and @antivirussupportuk each created one new Calendar event this morning, offering help with anti-virus software instead of printers and encouraging users to call new numbers.

Are they marked for editing? Should be an option on the form "Mark as Edit".

You should reask this in https://secure.phabricator.com/ponder/
Maniphest is for bugs and feature requests, not help

T5505 is related

Thanks I made the smtp-encoding change. We're just about ready to update to a vanilla install. If it doesn't fix it and I can provide reproducible steps, I'll update this bug report.

Hmm, I don't see that one in the upstream either. Maybe your origin is also a fork?

We're running a fork and sorry, I know it's a little behind stable. We're working on getting back to a vanilla install to make updates easier.

$ git merge-base HEAD origin/master
33bf2a79def2e03c2248730afa080ead489942be

What does this show, when run in your local working copy?

P2028 is a really quick bookmarklet that will pull the content of a given Phriction document and insert it into the current Phriction edit page's textarea. Hopefully it'll save a few clicks for those of us who write lots of pages with a similar structure.

My workaround for arcanist:

metamta.email-body-limit is unset.

Also, is metamta.email-body-limit set to something crazy? I think that only means main-body (not body + attachments) right now, but it should probably mean body + attachments + headers.

Oh, never mind, that's the Differential patch responding to the commit, so metamta.diffusion.byte-limit isn't relevant.

Thanks, I'll take a more in-depth look at this.

JIRA actually seems fine: arc, web UI, and both the integrations (link / post) work properly for me at HEAD of master.

Wow I feel the same way as @lunderwood. The problem is that it now happened for the third time and users send me screenshots of how their upload didn't work. But the permissions are all correctly set up. But then it works again after some time. It's a bit frustrating.

I've been also playing with the shellcheck linter and evaluating it using the following .arclint entry:

I had a look at other bug reports. It looks like I am not the only one having this kind of problems. So it seems that hg >= 4.x is not supported yet, and actually not even the whole 3.x is supported.

@gabe - That's the same issue, I believe. You should be able to push using Mercurial 3.4. I've been meaning to do some testing to try and fix this over the winter break but a day is no longer what it used to be.

Not sure if this is the same issue, this is on a new phacility hosted phabricator instance, when attempting to push to a new mercurial repo:

Aha -- the diff as posted for review was mostly-reasonably sized. The diff as committed was the huge one:

mysql> select differential_diff.id as diff_id, creationMethod, SUM(addLines), SUM(delLines)
    ->   from differential_changeset
    ->   join differential_diff on differential_changeset.diffID = differential_diff.id
    ->  where differential_diff.revisionID = 253041
    ->  group by differential_diff.id;
+---------+----------------+---------------+---------------+
| diff_id | creationMethod | SUM(addLines) | SUM(delLines) |
+---------+----------------+---------------+---------------+
|  837437 | arc            |         11845 |          8567 |
|  837558 | commit         |       1752986 |        396108 |
+---------+----------------+---------------+---------------+

bin/worker execute --id 35362582 did not work because the task was archived. Instead I ran ./bin/phd stop; ./bin/worker retry --id 35362582; ./bin/phd debug PhabricatorTaskmasterDaemon. The key seems to be the production of the .patch file itself, not the number of files. Somehow these users managed to cram a >100M patchfile into Differential:

thank you @avivey.

The grouping is probably random / first in the list. There's no concept of"primary/main parent" either. parentIDs/subtaskIDs constraint in maniphest.search should give direct parents/children only.

Thanks, I think D17097 should fix this. It isn't intended, and is just a curious artifact of some other behaviors.

Alright, I'm actually having trouble reproducing this. Here's what I tried:

I wasn't immediately able to reproduce this:

I strongly suspect this report has enough information to let us replicate the issue locally, so you don't need to take any further action yet. I'll follow up if I have difficulty replicating it and we can figure out what differs between my synthetic test case and your real environment.

Reference in PHP 7.1 migration guide: http://php.net/manual/en/migration71.new-features.php#migration71.new-features.asynchronous-signal-handling

See also T10208

We take design feedback during product launches, and no other time.

@chad Ah bummer. Is there an official channel you guys recommend for feedback of this type?

Sorry, we don't take UI suggestions as feature request tasks, but do value the input and will keep it in mind.

It will likely be easiest to replicate again after upgrading to Week 52 stable this Friday, since I can't use precise same diff, and don't know the precise set of replication criteria yet.

You can always create a test instance in Phacility, and upload the diff there - those are free and temporary - see Reproduction/Resources
There's also rGITTEST, although maybe it's not so good for a super huge diff...

We weren't running quite HEAD then, but we were running a version that was our patches on top of something about a week old -- see the end of the description of T11743, which was the first report in that chain. Our version today is a couple of months old, so I see why that'd feel different.

Hm; we weren't running HEAD when we reported T11748. We have an upgrade planned to latest-stable in a week or so -- will that be sufficient to re-test with? Or is there a repository that we can apply a 4,800-file diff to on Phacility?

Please update to HEAD before filing a bug report. We can't take reports against old versions of Phabricator. You can use Phacility if you'd like to test an up to date installation.

You can create your own link to tasks in a few seconds; the extension above will reduce this further. I don't plan to bring a global, hard-coded "Open Tasks" link to the upstream.

(2) and (3) are correct.

Probably should be two separate tasks. 1 is implementing some sort of "global" menuitem for projects. The other is adding group by queries to workboards, which I think is already covered in another task.