https://secure.phabricator.com/book/phabricator/article/configuring_file_storage/ explains file storage in Phabricator.

Maybe I'm missing something obvious, You say if you set the local-disk path the error goes away. So what is the bug you are reporting, specifically, and how can we reproduce it.

Yes?

Is this a bug report?

It can't currently move to translations or be per-user because it has global effects, notably the availability of "silly" statuses in Maniphest. We can't show different users different sets of available task statuses.

I imagine it will move to translations at some point, like Doge and Pirate.

Yes @epriestley, but it is a global setting and when you mentioned this Corpo-Vision® thing I though of it as a user setting, because all of us see the world differently.

Such a setting already exists: Config → phabricator.serious-business

In T10000#149838, @epriestley wrote:

....
In contrast, I can't offhand recall anyone ever complaining that the header text says "Weigh In" instead of "Add Comments".

Our use case is fairly atypical unfortunately. We have builds setup to run every time a diff is pushed. These diffs run integration tests that could take anywhere from 30minutes to a few hours and we don't require them passing since it's an extra step on top of unit tests running. However in the event that a longer running test breaks after a diff is landed we want to be able to alert not only the user who broke the integration test but also a group of users who are actively maintaining them incase they need to coordinate work.

To be more specific, I just mean:

Good point. When i was testing this i hooked into the Test Consul and allowed buildables to be passed in so everything was seemingly working for me. I am guessing i need to dig a littler deeper into the harbormaster transactions to get this working properly.

I'm out of ideas and can't reproduce this problem, then, so we can't move forward (see Contributing Bug Reports). Here's, e.g., this working fine for me against this server:

I updated to get rP9d125b45 and there is no change. Cloning a repo using http still hangs. I then reverted the change in rP8269fd6 and that did not fix the problem either.

@cspeckmim I just fixed that, unfortunately, it doesn't help. Here is a complete debug output when trying to push:

Thanks for the update of the documentation and the explanation. Perfectly fine for me.

I think this has served its purpose, so I'm going to close it out. Results:

@andyboeh - I think there might be an issue with some of the fixes I was looking at. When removing the bundle2 capability from reply, the message preceding the capabilities output is a length of the following line, usually something like

242
capabilities: a, b, c, d, bundle2=http%%%%%...

By just removing bundle2 it causes the preceding number to be off, which is what the client uses for parsing the stream. I haven't gotten back to looking at this but I think that's the issue you're seeing.

How are these tests executing?

I'm unable to reproduce this against this host or hosts in the Phacility cluster.

D15173 updates the documentation.

It wasn't too much of a hunt, but I did go easy mode towards the end (audit2allow). For others he is my basic install notes on Fedora 23 server:

doesn't seem like good practice

I'm using this unit file, which works when I manually start it or restart it. However, if I do a cold boot of the system the unit fails and I have to ssh in and manually restart it.

Yeah, I suspect that the length of the header is the issue.

I am on Mercurial 3.6 on both, the server and the client, and just tried what @cspeckmim suggested: Removing bundle2 from the capabilities in reply to the hello command. Now my client gets one step further, but still fails to push most of the time with remote: abort: stream ended unexpectedly (got 0 bytes, expected 4)

In T9348#156791, @exp10r3r wrote:

I tried doing an arc diff to submit my patch but ran into this,

[2016-02-02 21:15:55] EXCEPTION: (PhutilTypeExtraParametersException) Got unexpected parameters: standard at [<phutil>/src/parser/PhutilTypeSpec.php:150]
arcanist(), phabricator(head=master, ref.master=3264d9f680cb), phutil()
  #0 PhutilTypeSpec::checkMap(array, array) called at [<arcanist>/src/lint/engine/ArcanistConfigurationDrivenLintEngine.php:90]
  #1 ArcanistConfigurationDrivenLintEngine::buildLinters() called at [<arcanist>/src/workflow/ArcanistLintersWorkflow.php:44]
  #2 ArcanistLintersWorkflow::run() called at [<arcanist>/scripts/arcanist.php:382]

I could run through it by removing the following section in .arclint file,

,
    "xhpast": {
      "type": "xhpast",
      "include": "(\\.php$)"
    }

But it wouldn't let me commit.

If that's the case, a workaround is to query for the tasks in Maniphest with page size > 865 instead, then "Select All" and "Batch Edit Selected".

Oh, maybe the issue is actually the redirect. Specifically, we'll end up issuing this:

I can't immediately reproduce this by issuing a query for 1,000 tasks, then doing "Select All > Batch Edit Selected". The page takes a couple seconds, but loads fine.

In T10269#156825, @epriestley wrote:

sorry that I can't provide reproduction steps

Historically, I don't think these tasks (error logs with no obvious negative effects and no reproduction steps) are very useful. I don't immediately know what's going on here, nor plan to dig into it unless it creates an observable problem.

Well I don't choose any tasks, I guess it defaults to all objects visible on the workboard (of which there are 865).

How many tasks are you attempting to batch edit?

sorry that I can't provide reproduction steps

(This isn't a once off, there are a bunch of these errors)

(Specifically, the scrolling is a feature which I added in D10188 but punted on making work in Firefox.)

Write Depends on D123. in the summary of B.

I tried doing an arc diff to submit my patch but ran into this,

Tested with rP9d125b459ea8, and it's working properly: thanks for the quick fix!

Seems like once you mess with the order of the tabs, the default doesn't work.

Nice. This is likely something easy/simple/silly, I just haven't been able to reproduce it locally and the answer has yet to come to me in a dream.

I have a repro in my sandbox, will dig around.

I'm on the freenode IRC channel. Studying the code now. If I need any help and assuming I don't give up in between, I'll ask my questions.
And as for this thread, I think I've understood both your points.
Being an admirer of Phab's current documentation, I'll try imitating it in my work as well.

Right, yeah. CSI is somewhat separate, since most of it isn't intended to be picked up by autodoc tools, but it is also designed to not conflict with those. (I should have the published standard up on my site in the next week.) Docs are "what does the code do" and "how do I use it", CSI is "why is the code like this and what is it doing?"

I'm referring to that as well. Diviner builds docs from his comment blocks. Most of it is only on abstractions though like libphutil.

I'll admit, his docs are quite impressive. What I'm referring to is effectively inline-documentation of the code's intent itself, which is inherently separate from docs, and is solely to make maintenance by any programmer who takes the code on possible, without involving the previous dev in person, and largely without invoking the consequences of Brooks' Law.

In general @epriestley writes more documentation than any engineer I've ever met. At least, most abstractions are well documented.

I'd have to agree not to write things twice. That said, I do know that when we undertook starting our own animation system, we first dismantled the open source one we were considering prior (that's where we commented everything), and figured out the inherent problems at its core, which in turn prevented making the same mistakes in our system. Plus, some approaches may be at least partially salvageable for v2, tying back in with the basic idea of "don't code things twice".

For the record I did try to do this myself with my limited eng skills, and I gave up. If you're a natural with JavaScript, it's likely an easy task. I'm not.

There are two main issues. First being we prefer not to context switch ourselves to whatever the issue-du-jour is. That is, we're a very small team (2 people) on a very large project. We maintain throughput by being focused on the current task. We're not currently focused on Conpherence.

Right about now, it might be worth mentioning that my company instituted a standard of commenting every single logical statement in code, stating the intent of the logical statement (not just restating the code).

But maybe you are an adventurous soul! Code is reasonably organized by application, so src/applications/conpherence/ contains PHP and webroot/rsrc/js/application/conpherence/ contains the JavaScript.

The engineer who built Conpherence is no longer contributing code, which means another developer would have to learn it first to give you pointers on where to start. This isn't a great use of our time. I expect Conpherence to get overhauled sometime in the next 3-6 months.

Why is that?

This isn't a good task to learn how to contribute to Phabricator.

I'd like to contribute and help in finishing this. Where do I go?

ip2long can also return negative values (see rP30473549).