sadasdads

I understand the basic request "I want my diffs sorted on the task by dependency, not alphabetical", I just don't understand they why, or more importantly, what the core problem is. The core problem is what's missing, and what means we can't move this forward. Why do you want this, what information is missing, how would you make different conclusions from having that information. If we provided it on a different view, would that suffice, and so on.

Calculated reading time of Describing Root Problems and Contributing Feature Requests is ~12min for very slow reader. Both of those documents are very helpful and universal because not only do they provide guidance for phabricator, but provide very general guidance, that can and will enhance Your input in any situation. Quite frankly, I translated and enforced those rules with my customers - it has improved both my life and my customers (after obvious "TL;DR" comments).

Sorry, those two pages are ridiculously long, I won't read them.

T9986 is reproducible:

In T9986#149260, @chad wrote:

Afterwards I clicked on Create Task and it worked, it did not give me any other error.

Where, specifically. "Create Task" is a permission-locked form on this install.

Sorry, those two pages are ridiculously long, I won't read them.

Afterwards I clicked on Create Task and it worked, it did not give me any other error.

Not sure what you mean. Afterwards I clicked on Create Task and it worked, it did not give me any other error.

This is correct, only Community members can directly create tasks.

Please read Describing Root Problems and Contributing Feature Requests. We unfortunately don't have the ability to prioritize feature requests that can't state a core problem. A core problem indicates to us what should be built, as in we may have a different solution or another means to solve your problem. Feature requests without core problems are problematic as they only serve the author's desires, not the entire projects need.

I had the same issue, it seems related to T9908.

This does not appear to describe a bug in Phabricator. See Contributing Bug Reports.

In T9986#149208, @joshuaspence wrote:

Can you provide steps on how to reproduce this bug, it's not clear from your report. See Contributing Bug Reports.

For example here D506 should be between D560 and D561, not at the top:
https://phabricator.freedesktop.org/T3491

Ah - never mind about the landing it part. Doing a git rebase origin/master followed by arc land solved that issue. Though the error message/suggestion remains confusing (and does not at all appear related to the actual solution).

My colleagues and I have run into what seems to be the same problem. A diff D1259 was created to be dependent on D1258 (and D1261 was later added as dependent on D1259, though I do not think that is important).

Can you provide steps on how to reproduce this bug, it's not clear from your report. See Contributing Bug Reports.

I don't understand the request. In any case, see Describing Root Problems.

As a temporary workaround our company currently uses direct checkout through the standard ssh server until we have a stable phabricator-ssh daemon available.
I hope this will be fixed soon...
Thanks anyway!

@foven we have not found a solution. We had run out of time to debug SVN. Now we only host GIT repos on Phabricator and SVN is elsewhere.

That's expected, you disabled the form for creating other forms.

@epriestley I hit this again. These are some stats from SSHing into the machine:

After some digging I found the problem.

This feels like we're in much better shape, now. We can refine it if more stuff comes up once the new endpoints start to land.

whoops, that's also funky

I also put the DAO itself back to make storage adjust happy, so that should get nuked when the data is nuked.

Did a new test install. I could reproduce it.

Thanks for taking care of this!

Ah, yeah, that's reasonable.

I tested this feature and noticed that the browse button beside "Onto Branch" was not clickable unless I removed the pre-populated default branch.

Can you show me what you see at this path (replacing the domain with your domain)?

Can you show me exactly what version you're running, by navigating to Config → Versions?

D14783 fixes the second exception.

What version of Phabricator are you running?

After an exception

gotta up ur game

See T9908#148194.

Just an update:

T5397 is another copy of the pipes-in-tables issue.

I'm going to assume we're in the clear on this.