Ref T4768

Workaround is to edit this URI:

I've looked at the database, specifically the worker_activetask table. The bad transactions appear to be linked to profile panel objects (objectPHID like PHID-PANL-...).

You are right, it does not specifically describe or refer to an import button anywhere.

Okay, but the docs don't actually describe or refer to an import button anywhere -- there's no text like "click the import button" that I missed when updating things?

In T11278#184475, @epriestley wrote:

Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project.

I can't find where we say this in the documentation. Can you point me at what you're seeing?

@RuralHunter these aren't versions of Phabricator we produce. How have you modified your local install?

so the UI should still look good given that edge-case.

At HEAD you should receive a setup warning that PHP7 is not supported. We don't recommend using it for production.

Why do you have local changes in your phabricator folder?

Although the new graph display has the branch-like display at the left, that column is removed from the task titles (2 columns away) - which aren't indented to clearly show the parent-child relationship.

I just had this problem as well. Turns out I had a typo in preamble.php. A more descriptive error would be nice, but with this task open at least the cause is easy to find :)

Note that it is possible to set a path to the websocket for every server as well. This is handy, for example, when your notification websocket is hosted behind the same URL as Phabricator itself. We have https://phabricator.ourcompany.net/ for Phabricator itself, and https://phabricator.ourcompany.net/ws/ for the notifictions websocket. This corresponds to the following client config:

Maybe something like long lists with "titles" or "summaries" for list elements?

# Something top-level
  Long, multi-sentence description of this top-level list item.
 - Sub-element with "title" <br/>
   Long, multi-sentence description of this inner list item.
 - **Another sub-element, highlighted even** <br/>
   Another long description.
   Very long and very descriptive. 
# Something else

which renders like:

1. Something top-level
   Long, multi-sentence description of this top-level list item.

It seems the move_beneath.php doesn't work any more with the latest code.

Sorry to trouble you @epriestley , I have the same question(T11273) . After your committing rP5ffdb732735c, I tried to update my phabricator under the direction of doc(https://secure.phabricator.com/book/phabricator/article/upgrading/). While I executed git pull，the terminal shows

In T9640#182027, @tomelssjo wrote:

So what exactly do you need to comment out for this to work on PHP7? Is is src/applications/cache/spec/PhabricatorDataCacheSpec.php and src/applications/cache/spec/PhabricatorOpcodeCacheSpec.php

I just ran into the issue with this error on Windows:
Usage Exception: arc diff` is only supported under git, hg, svn.`

Resolved by D16246, I suppose.

Users are somewhat surprised that adding a project removes another project (Due to being sub/parent-project); Partly that's because there's no hint in the editor that this is about to happen, or that the 2 projects are related.

Oh, now that we gave posts the J monogram, we should probably also find a way to put that on the blog page somewhere (at least the internal one, and maybe the ApplicationSearch results page). Right now you have to know that you can fish the ID out of the URI. Let me see if I can poke at that a bit with my doc stuff.

I've been pretty excited about this since the unbetaing started.

I think I started the unbeta task in December. So... Merry Christmas!

Just the T6299 stuff, I think.

Anything left to fix before unbeta?

Cursory research yields Markdown uses two spaces to indicate a <br />.

@epriestley, the use case is actually from my content development department. It's hard to explain the task, but the hundreds of direct subtasks was unavoidable, and the project workboard did not work well in their workflow. Developing content for educational software can be extremely demanding. That said, I'll admit it isn't common to have hundreds of subtasks. Still, it is a scenario that can happen, so the UI should still look good given that edge-case.

I'm leaning toward making it a "Relationships" box with "Task Graph", "Mocks" (with a thumbnail/gallery view instead of just titles), and "Commits/Revisions" (probably with a little more status information than we currently show).

Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project.

I'm leaning toward just adding a big "Clippy" element to this UI:

• Choose the default colour+icon picture for the project
• In the project history, click the link to the file that has been assigned as the picture
• Note that the file is temporary, so will be cleaned up by the garbage collector

I think if you haven't activated the repository and visit URIs, we can show an "Import" type note and call it a day for now.

Yeah, I think it goes away after you push "activate"

Is that text already present and I just missed it?

We can probably start with a text hint on this view:

Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project. I was pretty confused as it clearly wasn't that. Perhaps the page after clicking the 'Create Repository' could have an option of importing, which presets the values to observe a repo.

I was confused at first - from previous workflow I thought I took a wrong step when setting up the repository and landed on a "completed" repository page which I didn't expect without selecting host vs. mirror. I deleted the repository and started again and finally got it after hours of turmoil (maybe more like a minute of prodding).

Can you give an example of what specifically you are trying to build in Phabricator?

A few questions...

That would be perfect!

It was merged into master today.

Looks like this should be available in 7.1 btw: https://wiki.php.net/rfc/async_signals#proposed_voting_choices.

One possible solution might be to make "Task Graph" box "Task Dependecies" and have a separate tab for a straight list (default, parent/sibling only) and graph.