Error if cluster.addresses is not set at all:

D11159 seems to be related

I've upgraded our instance now this has hit stable, and our team is thrilled. The interface may not be perfect, but it satisfies the vast, vast majority of our use cases. Thank you!

Not a solution, but a workaround until fix:
Revert the repository temporarily to abf37aa9794790fbc0e215102519e9ffc7e99b7e.

Temporarily checked out abf37aa9794790fbc0e215102519e9ffc7e99b7e; Phabricator is accessable again.

Related: T10801

We do this as a minor extension to the typical 'land' workflow. That is we have a wrapper that causes 'arc land' to be equal to 'arc diff -m "automated bump" && arc land'. We do this so that the latest version in differential maps exactly to the one that got landed. This also always causes a comment to be created immediately before land. We could possibly work around this locally by comparing the diff in differential (with getdiff or the modern equivalent) but it would be amazing if we could just tell phabricator "we're attempting to update but don't generate a new transaction if its exactly the same).

git

git, svn, or hg?

To remove one variable, I experienced the same issue if both repos were locally hosted on phabricator. I tried updating just before posting this bug report. The commit I have (from stable branch) is 5ddaf5289862cce3957c5630eb11df31fb0786b8.

Please fill in the rest of the information required on bug reports please, version and clear steps to reproduce. Thanks!

@areitz FWIW, we use monit's ability to search for a process name. This isn't ideal but its the best we've come up with without forking the daemon code.

This should be fixed in HEAD of master. Thanks for the report, let us know if you run into anything else.

We could build Zelda's instead.

:+1 <- is this the internet default for upvoting something?

I'm not disagreeing there is a need for built-in navigation in Phriction, just that we're not planning to solve that with "Document Hierarchy". It will likely be a first class feature the user can intentionally structure separate from how they manage the tree / document nodes.

@epriestley thanks for the feedback. I've read through the new docs, and I think have a section explaining phd-daemon, and incorporating some of the notes from T4181 (about setting a startup script for your OS) could be really useful.

@chad Thank you for the comments and taking care of my request. But to reply to your (hopefully, not rhetorical :-) question on why the inverse statement is not true, it is IMHO quite simple: similarly to having any book's table of contents (ToC) in the beginning is natural, any long enough document will benefit from having its hierarchy (essentially, a ToC) placed prior to the main level content. An unlikely potential confusion might be further eliminated by adding an anchor hyperlink to the beginning of the said content as a part of the document structure.

Fantastic, applied locally and it works as intended. Thank you! 👍

Not 100% sure that's a fix, but I was able to reproduce something that looked similar and that appeared to fix it locally.

Awesome, thanks 👍

You can put lines=30 or similar after the triple backticks in the header:

Here it is (not sure if I caught everything that I might need to censor, please let me know if I missed anything):

(You may need to censor Authorization header bodies.)

What does GIT_CURL_VERBOSE=1 GIT_TRACE=1 look like for GitHub in your environment?

Or Phlooz.

Phunny Munney

We should build an RPG-style outfit editor...

phoenix (like Greece)? phranks?

We need a good "Ph" currency name before I can really get maximally excited about it.

Since Windows tends to languish near the bottom of the priority list and I'm fairly confident this patch is fine, I'll accept it upstream if you use it for a couple days and nothing explodes and want to submit it.

I suspect that fix is safe and correct. It would be nice to kick the tires a little more before applying it and maybe try to dream up some test coverage, but it shouldn't have broader implications within the arc ecosystem.

T8407 holds a small piece of UI for this.

We could build Zelda's instead.

Overall Phriction is simply a Wiki, and not so much a CMS, which is what I'd recommend if you have such needs. We may extend and add additional CMS-like features into Phriction during out next iteration, I'll merge this task over so your thoughts aren't lost.

Why isn't the inverse true on your statement? If people are missing there is a structure underneath, and we flipped the layout, wouldn't they then miss the fact there is content underneath? Wouldn't people be more confused by the fact that when they clicked on any page, that only a navigation element appeared?

Today the live notifications work in Firefox as well. I believe that it did not work yesterday due to caching.

T5953 might have some kind of options for this eventually with a longer timeline between polling checks (e.g., once an hour) but that's probably some ways away and probably wouldn't be a primary focus.

See T5834 for previous discussion.

I'm not worried about immediate logout. I agree that the effort / reward tradeoff is all wrong there. I was more thinking about the case where you are setup for anonymous search. Every X a check is performed to see if users still exist.

this guy is pretty cool I like him 🐗

💯💯💯

Jay: ok then, while I'll not argue about whether breaking is correct or not, gmail does break citations correctly.
That is, if I open an email and write (break before "unrelated newline"):

Per T6915, I'm likely to split the Phabricator side config into a list of services. If you run multiple servers, you list all of them and Phabricator can survive the loss of some subset gracefully. This should be easier for everyone to configure, too.

I'm currently thinking about making this configuration push-based instead of pull-based: each server is told about other servers it should publish to when it starts up. When it receives a notification, it publishes to all those servers (with reasonable mechanisms in place to prevent cycles).

This report doesn't have reproduction instructions (see Providing Reproduction Steps) and is likely obsoleted by T10697.

See T5181#136121 above.

• D15695 should fix logged-out users.
• D15696 + D15697 should smooth out security.require-https for intracluster requests.