I guess I'm more used to IRC where if you ask a question (assuming someone will answer), you tend to get pointed to general vicinity of the related paging logic. Naturally I can search for that myself, its just nice to get a headstart.

What sort of answer would you prefer we provide?

(See also Contributing Feature Requests and Describing Root Problems, and T8227.)

We don't plan to implement this.

Thanks. Short, to the point, slightly rude, and not terribly helpful.

From T10170, Ponder still has some addRawSection() calls which should be addRemarkupSection() calls.

This request does not describe a root problem. See Contributing Feature Requests for details, and Describing Root Problems for help describing a root problem.

Sorry, I've created this task by mistake, and I cannot delete it :/

Thanks for the quick fix !

Thank you very much! You solved all my problems :D

The first hit on Google for "phabricator daemons" should be the documentation for them:

Thanks epriestly for detailing about the error and also the solution to it. Yep that was an database issue. After logging in as admin I was successfully able to update the phabricator.

Hi guys, any update on this general issue of viewing subtasks in a nested manner?

Hi guys, any update on this general issue of viewing subtasks in a nested manner?

That would likely work fine as long as you can see all of the comments together (like you can if you go to a diff line and view all comments there).

This would be ambiguous with other directives (lines, name, counterexample, etc).

In general we'll likely show the full conversation about an inline point on Pholio on the dialog that you can pop up, sort of like a thread on a diff line.

If you are new to Phabricator or have not modified Maniphest much, this post does not pertain to you.

Hi Evan,

We can't reproduce any of this and no other users have reported similar issues. Some of the issues described here are likely access/permissions issues, which should be communicated more clearly after D15079 / D15080.

This is probably because the user you are connecting with does not have permission to access the database.

Ah, I didn't check if HEAD had an index for the unit table. We're about 8 months behind because we can't upgrade until we resolve all of the conflicts caused by the different Drydock architecture.

I think case (1) (and maybe cases (3) and (4)) is resolved at HEAD.

One hovercard related suggestion in T10187: hard to understand status of sub-tasks from parent was to add projects/columns to Hovercards so that when mousing over subtasks you can see what projects they are in without opening them all. It looks like the latest mock has that so

@chad Thank you for quick clarification.

Herald has some very unusual code to preserve control values when you swap the selectors. Generally, the issue is:

HarbormasterBuildTarget->loadArtifact() also probably does a table scan when it doesn't need to, but if that isn't causing any problems I'll leave it alone for now until we hit it for real.

I can't reproduce the second issue; that index should already exist (or bin/storage adjust should create it if it does not). Here it is in the source:

it's on master today and stable likely on Saturday depending on what branch you track.

@spicyj Good idea, thank you for the advice :-). I just wasn't sure this feature is in production...

I think I misread your bullet. Basically we'd like to add more / better information onto hovercards soon, so information you think is important, please follow up on T10055

I believe this is fixed at head. Let us know if you're still seeing issues.

@ablekh Have you tried Googling for "how to update phabricator"?

How do I get this feature? System update? If Yes, please point me to documentation, describing the update process. Thank you!