Any update on this? Th solution proposed by raman is not working for me :(

Then how can I reconfigure this outbound mail.

Properly configured outbound mail works. Your outbound mail desn't work (as you report), threfore, your outbound mail configuration is wrong - that's what I meant.

What do you mean with misconfig?

And so - You must've misconfigured outbound mail :)  or something like that :)

When I run the following command, I receive the email directly:

https://secure.phabricator.com/book/phabricator/article/configuring_outbound_email/#testing-and-debugging-ou

Where can find more information concerning the mail system.

WYSIWYG is very not cool. Not only is it complicated and consuming to build, it also unnecessarly invites users to mess around with styling. Personaly I always stick with code (hell, I even write my documents using LaTeX). I'd say it's way better to have text-only entry for all documents and coments, plus have on-dememand preview, like this beautifully crafted comment box.

👍 to @cspeckmim

This greatly depends on Your mail configuration. For example, our install has local mail server used for sending as well as some mailboxess i's sending to are local, giving near instantenous mail.

You can exclude various monograms from Remarkup in Config.

Yeah, mostly we think a really slick WYSIWYG is very complicated and time consuming to build, moreso than we'd be willing with current staff to ever pursue. It seems to take a large corporation to really have the time and willpower to do it correctly, as even tools like Wordpress still feel janky to me. Our planned 2-up display I think would resolve most of the need for such a tool and offer a best of both worlds approach (write in Remarkup, see work styled).

I would also express interest in Thoughtwork's go.cd: https://www.go.cd/

Not super-familiar with PowerShell. If the issue linked above would be helpful to you, could you please add your requirements there and we can coordinate getting it in the Uber plugin? (I'm the maintainer)

We have a number of repositories (~20, though around 5 are generally active at a time) - what do you think about having the associated repository indicated somewhere on the revision hovercard?

I find myself much more productive writing remarkup opposed to fiddling with selecting & styling with WYSIWYG (unless I'm trying to find the exact right icon to use). If a WYSIWYG editor is pursued I think there would be a sizable user-base who would find regular remarkup editing to still remain useful enough to have available as a preference.

Right now we're working around it by having another build plan called "Post results to Phabricator" which has phid and state parameters. This build plan then runs the following PowerShell on a Windows build agent to post the result:

T3967 is the first stop, but a true Medium style editor is many, many, many years away.

I have a branch up that allows for non-differential builds to submit
harbormaster from Jenkins. I dropped it before the holidays since there
didn't seem to be much interest but can resurrect it if people are
interested:

Is there any documentation on configuring Jenkins for commit builds (instead of differential builds)?

See also "Sticky Accept" here:

The upstream discussion of this issue starts with "Chain of Custody" here: T182#133871

Thanks for your response, and I agree. The rare inconvience of reverting a change that someone put in abusing the system is far less then the annoyance of having to wait for a minor change to complete the review or waiting for reviewers to approve as I make a minor change.

You mean from a Harbormaster Lease Working Copy perspective or a Land Revision perspective (when it comes to nonsensical UI).

@epriestley What is upstream's opinion on this? Is it something that can be prioritized or have an diff submitted and reviewed against it?

Not currently possible. Two quick thoughts.

I'd be fine with exposing this information from some bin/auth help me with computer since anyone with CLI access has other means available to read email addresses, but we don't currently have such a command and I don't think there are any adjacent requests to motivate building one.

This is straightforward, but I'm hesitant about it because users can use email addresses to log in, and we do not currently expose email addresses to administrators. Adding this information to the activity log could reveal lots of near-misses of email addresses. While providing this information would help administrators with users who are extremely creative in their use of computers, it seems slightly worse for the bulk of normal users from a privacy/security point of view.

The current state of things is they need to have an account on Phabricator. We have an upcoming product Nuance which is our "help desk" tool for non-users.

I had a similar error when initially trying to clone via ssh, "sudo: a password is required". For us, our repos hosted by phabricator were owned by root instead of the phabricator daemon. A chown of those repos on the server provided a quick bandaid. I can't remeber what the actual solution was, though. I'll ask around.

I upgraded a 6 month old installation to HEAD. Can it be related? Didn't experience any other issues.

A couple of them will but for the most part no they will not be in Phabricator.

I actually think failing universally like that is probably fine (you can --skip-staging anyway, as long as the error tells you about it) but the UI behavior in Phabricator itself is frequently nonsensical (we basically guess that the staging area probably exists and proceed blindly).

We have patched around this issue locally with:

Outside of Harbormaster, "Land Revision" is also impacted.

Specifically, the UI currently has this mess of a problem corner:

I'm just going to close this out, since I'm not sure we really need it -- D14963, D14962, and other work adjacent to T2450 found some general performance improvements in rendering. It's possible we might pursue this (and/or a highlighting cache) in the future, but I think we're fast enough now that the huge amount of upfront work the daemons would have to do to populate these caches probably doesn't make a ton of sense.

This is more than a year old now and we haven't seen other requests for it. Diffusion copy/pastes and links cleanly and I think this is sufficient in all reasonable cases I'm aware of.

Sorry, I still don't understand your root problem.

These should be pretty easy once Phriction has projects. You can just create a Documentation project and subproject whatever tags you need under that.

Ok, thank you for your tipps :)

I'm going to merge this into T9622, but -- oh, @chad already got it.