Aren't 2xx statuses considered "success" in HTTP protocol, despite values of "xx"?

Hmm... This IS funny. This generally is/should be some kind of desired behaviour, but is less discoverable, because other tools don't have it, right?

I was just filling near identical task... well here it is, copied verbatim:

Could this be part of T9132? Seems like one 😉

@rsellam - Either I misunderstood You or You misunderstood me...

In T5173#135555, @rsellam wrote:

Is there a chance to have a man page for arcanist anytime soon?
Creating a manpage only requires running "help2man /path/to/arc -N -n "command-line interface to Phabricator" > arc.1". It can of course be run automatically when a new arc version changes its usage.

Your usecase is similar to what we do usually with open-projects. However, as I said in Conpherence, with this the issue still lies in git configuration. Even having noreply address would need to set up git for that repo to author's noreply mail... Plus with mail like "username+noreply@phabricatordomain" it would be almost automatic to guess proper mail (which is forced in my company and some of our clients) whis usually would be simplu dropping +noreply and phabricator from mailaddres ;)

Still - wouldn't You have to also configure git for repo to use phabricator-mail? Plus - routing to conpherence is IMO more dangerous than simply forwarding to mailbox (where once can set up nice filters and spamhandlers).

With as much opinions as participants or more, it's important to focus on what user wants to achieve and what Phacility wants to preserve.

Since I recently had to write/update some long phriction docs - section editing would help me greatly!

In those rare cases when I have to deal with "old version causes headaches, nev version is not avail everywhere", I put handlers for old and new in place, with handler of old way spilling out warnings that "old version causes headache and I don't care anymore about it, use new".

Aaaand have arc build be called arc weld! Seems fitting ;)

Item in multiple queues would IMO confuse the hell out of less-intelligent (me).

In T9212#132956, @chad wrote:

Maybe "real time" support should just be ended overall?

Follow docs - those are VERY good, well written and easy to follow.

In T7073#132775, @chad wrote:

I wouldn't be opposed to a Dashboard Panel for Actions, as in, it's an Action Panel like https://secure.phabricator.com/uiexample/view/PHUIActionPanelExample/

And small typo in this task: it's Ponder not Phonder 😉

In T9168#132007, @devurandom wrote:

If only someone would read these explanations...

There's a lot of back-an-forth here but @epriestley pointed one thing in particular that reasonates well with my experience:

In T9165#131879, @epriestley wrote:

It sounds like the root issue here is really confusion around projects, and an expectation that associating a project with an object puts the object "in" the project. It doesn't, and, by design, project associations never affect visibility.

Well... Phriction is not wiki, nor is diffusion repository ;) When You boy for example car from Tesla named "Model S" do You complain that it's not named "Sedan"? Imagine all those Ford Sedans, Mazda Sedans, Toyota Sedans... Branding is important. Before Wikipaedia, how would You call Wiki-style page editing?

I got somehow bit by this today... I have only handful "custom policies" and those are quite combination of uers/projects/legal documents etc. In current situation I fully agree with @devurandom: Dialog visible upon clicking "custom policy" should be as descriptive as the on in history - it would make it waay more readable and easy-to-use

Thank You, this was perfect reasoning. I'll then consider extension route for
"members of associated projects" and I hope I can get it done ;)

Ou... so "project members" would be rather straightforward, but I guess "members of associated projects" would be NP-hard?

This IS kinda reasonable, but imagine browsing icons for match when creating badges... not only are there ~6 levels of badge awesomnes, there would be hundreds of icons to choose from...

@epriestley - can those be set as default policies for objects that can have dynamic policies? For now my default policy is "All Users" and I lock down almost everything to specific projects, but it would be better for me to have project members be deault policy for almost everything.

@chad - that's some object-specific policy... like "subscribers of this project" [is this "watchers" ?]... which to me is weird because I still don't get the distinction between subscribers and members... I mean obviously members are member and subscribers subscribe to changes in project and are not members, but to me subscribers are useless for most projects but members are ;)

Can I has one? Maybe someday I has as much as dis guys:

"Awarded due to herald rule H102" ;)

Oh, come on now, You're no fun... Why limit badges? Let users look like russian generals during parade!

Hey @chad - badges look HUUUUUGE on what You propose... As for colour - sure pink is not perfect, but it would be even better to colour-code badges. For example:

disable open_basedir restriction in your php.ini - should work then.

With full lato font and all that, this looks great on my install.. so:

I have one major problem for me & team with redesign: font choice. It seems that choosen font misses all of polish diacritic characters. Let me try here before sending screenshots:

In T8549#122021, @avivey wrote:

"Muted" is be perfect word for what I feel: everything is good and decent, but it's not as fun as it used to be.

Header serifs are nice. Make it consistent everywhere and it'll be good. at first glance it does feel weird, but I believe in @chad

Everything on Your list seems reasonable, however Generator UI is expected. Everytime somebody creates a room for project on our install for specific project, I have to explain that they should save project image and then D&D that to settings modal.

Well, this is certainly fun drive with policies and edge cases...

I be the weird one and say that JX.Scrollbar is the best "fake scrollbar" implementation I've ever saw and if I wasn't using build-you-own-linux-window manager I wouldn't notice that scrollbars are different at all! For me - I'd go with (1) and say "it's not a bug it's a feature. Actually it's a bug in chrome, go and complain to google. You use Firefox? Well, that's a bug in windows, go complain there" ;-)

Awefricinsome!

arcanist has nice arc command...

In T7447#111479, @epriestley wrote:

In T7447#111476, @avivey wrote:

Also, I'm missing a button to "see comment in original context", in cases where the current context is confusing.

I do think this is reasonable. If we un-fold, we could make "Older Comment" / "Newer Comment" be links to the comment in its original context.

I used auto folding and I can honestly say - it's a mixture. When working on same group of code when I remember context - it's time saver. When I forget context - It's OK. So I guess that's for me it's 75% good.

@alancrisp - I'd rather have whole history of what was requested and done. That's why minimal ui for showing old done inlines is better in the long run: If I don't care, it's just one line I can skip. If I care it's visible and I can click to expand :-)

Why not both? badges awarded manually for annotating special users + badges given automagically for gamification. Second part would propably depend on being able to write herald rules like "If commiter has 100 accepted revisions, award 'No Longer a Peasant' badge" ;-)

I vote for minimal ui.

I don't understand - previous version looked OK, but this... Now docs in our Phriction look awesome and cool :-)

Just my 0.02$: In integration please support CalDAV & ics :) Many firms in europe moved away from Google to own/hosted sulutions due to "Recently exposed security risks when exchanging data overseas" (Snowden & stuff) and if Phabricator would support those it would be great.

As evident by @hach-que example - @epriestley is right that humans actually using task get task numbers etched deep into brain tissue. Most issue tracking systems then rely on either humans with good memory or good search features :-) I still can remember redmine taks numbers from years ago...

#1 best #3 2nd :)

At which git-commit are Your phabricator instance is? You've upgraded libphutil also? what commits are Your versions of those.

I wanted to test it and... Clicking Links in notifications work flawlessly regardless of durable column. Clicking notifications themselves opens in same tab regardless of durable colum state.

Hmmm... This could be handled like dot & cowsay! For starters: theres tex2im but it's not standard on many distros, there's also some forms of tex2png, also there's dvipng that You can use to convert compiled dvi file to png... there's more than one way to skin a cat... That's for starters.

Just a small and unnecessary rhetorical question here: do people really leave setup warnings & ignore them? I mean - i fix every setup warning the moment they appear and assumed same is true for everybody. I really wish that @chad's wish for airraid.wav would come true ;)

maybe rather than "duplicate" somethng that streamlines merging duplicates (but that's more work I presume)

Everything's working on commit 3c6c6552d34b53d40c30100701fcf85c140c440c from saturday, so bug crept sometime in last 2 days ;)

this is replicable as well on secure.phabricator.com:

Design-wise I believe that suggestions should be placed very near and in same screen "estate" (hard to find right word right now). Basically: suggestions based on title should appear near title (possibly while entering title). Suggestions based on keywords found in task text should be visible near area where You enter text - this would be hard for small screens, but 2-column layout I described about my experience was really nice and saved me from filling couple of tickets.

Can't comment on how wikimedia handles that but I have experienced couple different approaches that may/may not work in most cases:

Just simply allow public and remember that "To view a wiki document, you must also be able to view all of its parents." It works almost out of the box.

The best way is to pop up $EDITOR for putting the description in. All additional stuff should be done with --browse (simply - in browser). It's "Quickly create a task for yourself." after all. At first I was surprised that arc todo did not did that, but it would be cool if arc todo would support putting description in via $EDITOR

This is nice feature and I'm using D12165 as patch and it's cool. It seems like good connection between arc tasks and arc todo now that in both of those You can use --project

This looks awesome. Icons make sense and relate to description perfectly.

Non-annoying would be IMO simply put it up along with install and "setup issueas" to simply be one of setup issues to opt in.

I'm all for @aik099 suggestion - zoom while centered instead of jump.

In T7287#96791, @mholden wrote:

Is upgrading as painless as a "sudo apt-get upgrade mysql" -- or am I asking for huge amounts of trouble with that level of naivete on my production install?

I admire Your concern with malicious deletion.