I believe this is now resolved by the series of changes attached to T12616. In particular, D17840 introduced Quicksand-aware state to changeset lists.

That's partly because "\n" isn't a newline in bash:

Yes, the behavior depends on the shell. I was using bash.

Ah, I see that it works differently in other shells. The above output was from zsh. In bash, indeed all output is written to the file:

It shows no output because there are no warnings. If you replace phabricator/bin/storage dump with a command that does give various formats of warnings on stderr, you see that it works:

$ sh -c 'echo "output1"; echo "error\nwarning\nerror2" 1>&2; echo "output2"' >foo.txt 2> >(grep -v warning)
error
error2
$ cat foo.txt
output1
output2

A vaguely related question... how is the /status/ endpoint meant to work behind an ELB? AWS ELB's don't pass a Host header to the healthcheck endpoint, so by default it just returns a 500. I worked around this by using some nginx voodoo to rewrite the Host header if the User-Agent header matches ^ELB-HealthChecker/\d+\.\d+$, but this is less-than-ideal.

I'm not sure this works as expected.

I used the subshell redirection trick as mentioned by @epriestley to hide this warning from our cron output as well:

In T12716#223717, @chad wrote:

I assume this is T4334

I assume this is T4334

I think we're mostly in the clear, now. This stuff likely introduces some bugs beyond the (mostly minor) ones I'm aware of, but I think it's all correct enough in the substantial ways. I'm going to take a break for a bit; I may get back to it tonight and land everything or may wait until tomorrow.

All of the inline comment icons got mis-aligned slightly a while ago. This is particularly visible with "Reply", I think. Note that the tooltip is centered, but the icon is too low (I think?) and too far to the right.

Really need an icon for points.

@jeffprouty Shoot us an email at support@phacility.com with details about your instance and the issue you're hitting if you're a paying customer; see also https://admin.phacility.com/book/phacility/article/support/.

Just confirming this is broken for phacility hosted instances (it is for us at least) and that there is no work around to date? Should this be it's own issue? Or should we reopen this issue?

uuuuuuuuuuuuuugh

Understood -- thanks for the clarification. One isn't always aware of how special-case one is. :)

Go for it, a couple emails came in that I'm still digging through. Thanks!

Do you have this or should I snipe? I'm home now.

We currently (at least, in theory) prevent this situation from ever occurring by preventing simultaneous tagging with both "Warp Drive > Thermocoupling" and "Warp Drive > Milestone 1". Since a task can not appear in both a milestone and subproject of a particular parent task, users can never be faced with the opportunity to perform a destructive drag operation.

Many of the patches you've personally contributed in the past have bypassed the bulk of the requirements under the "Rise to Prominence" clause of Contributing Code, since you have a history with the project, are a member of Community, and have generally contributed very focused patches with clear context:

Okay. When a task is in "Warp Drive > Thermocoupling" and "Warp Drive > Milestone 1", and you view the "Warp Drive" board and drag the task from "Milestone 1" to "Backlog", what do you expect to happen to the projecs the task is tagged with?

Sorry, that seemed to be in response to "are you working on this?" A user has since provided a patch for the feature, which is the sort of thing which in the past you folks have generally been nice enough to review.

Okay. When a task is in "Warp Drive > Thermocoupling" and "Warp Drive > Milestone 1", and you view the "Warp Drive" board and drag the task from "Milestone 1" to "Backlog", what do you expect to happen to the projecs the task is tagged with?

Do you expect a task to be able to be tagged with "Warp Drive" and also simultaneously tagged with subproject "Warp Drive > Thermocoupling"?

No, Thermocoupling alone is enough, as it implies it's part of Warp Drive.

Do you expect a task to be able to be tagged with "Warp Drive" and also simultaneously tagged with milestone "Warp Drive > Milestone 1"?

No, Milestone 1 alone is enough, as it implies it's part of Warp Drive

Per above, see Planning. If that isn't clear, let me know how we could improve it.

Phacility folks, do you have thoughts about the patch provided by @lyngvi above? Would be it be easier to review if submitted as a Diff?

Do you expect a task to be able to be tagged with "Warp Drive" and also simultaneously tagged with subproject "Warp Drive > Thermocoupling"?
Do you expect a task to be able to be tagged with "Warp Drive" and also simultaneously tagged with milestone "Warp Drive > Milestone 1"?

What it looks like here:
We have the project Grammofy Collections which represents one of our products.
It has a milestone Full Catalog Access
It also has a subproject Grammofy Collections: Frontend/Web

As usual, thank you very much (to both of you) for your precision and speed.

This should now be resolved in HEAD of master and stable. Thanks for the report!

I think the phabricator pages typically have CSS for @media=print or whatever HTML is -- which means you can print or print-to-pdf and generally get a good result. I hadn't done it in several months, but trying it on this task it's a little narrow

If you have a very narrow and specific need for Phabricator, our expectation is you will fork the product and provide the feature to your install. This feature is unfortunately too specific for your needs since you can already easily print any page in Phabricator via your browser, already formatted for printing.

I'll just ship up the "unbreak" diff, and you can either counter-diff me or figure out something else.

I think more narrow reproduction instructions are:

It would be enough just to be able to print the title and the description, that is to say, what you actually see when you click on a task (leaving out comments). As an example, see the file attached.

thank you! sorry for this stupid question :)

Yes on the Almanac project profile.

I can't reproduce this. Here's an example of a profile working correctly for me locally:

Select "Order By: Creation (Newest First)" or "Order By: Creation (Oldest First)".