Can you point out which parts of Contributing Bug Reports, User Guide: Prototype Applications and Support Resources are unclear to you with respect to this report so we can improve the documentation?

So I guess this bug is neither a known issue nor do you want me to provide more details since it's a prototype app?

I for one, very appreciate recent Phame change and look forward to Application Editor (especially D14584 will help me A LOT)

Closing as this is outside what the upstream provides support for (custom development). Generally Maniphest is for feature requests and bug reporting. Ponder, IRC, Conpherence are open areas for general use discussion.

Yeah, consistency and like "attacker gets into your account and deletes all your stuff and it's gone forever and you are so very sad" and such.

Any reason to remove the delete functionality then? Just for app consistency?

We could probably just do unpublished for now and wait until we have a stronger use case for a real "archive".

How should archiving posts work? Or is hidden/unpublished enough?

Now that I have a sub-par computing experience at home, some things should naturally get better.

Way better on my monitor now, thanks!

I am also fine with articulating meaningless corporate values.

Oh you said meaningful. Nevermind.

Can it just be a gif instead?

I bought an Acer XB280HK.

Here's a super helpful photo of my screen :3 :3 :3 :3

My new "gaming" PC monitor is matte and it's amazing to me how bad the color is. And it's a top of the line display. It does open my eyes a bit on some of our more subtle colors. I can see a {lightbluebackground} at the top of a web page, but not the bottom.

Yeah, I'm using a Dell U3011.

Do you have a matte screen?

I don't know how to reproduce this, either. This may fix itself as T9132 evolves.

Here's what's happening, in detail:

This seems straightforward to reproduce:

Drydock is also a prototype, see User Guide: Prototype Applications.

You are about 4 months out of date.

Do you have any steps we can use to reproduce the bug? See Contributing Bug Reports.

Phabricator does everything there except reports (you'll have to manually build those with queries or Conduit). We're happy to answer small questions in Ponder if you're getting stuck along the way of setting Phabricator up. If you'd prefer to just hire us to install Phabricator and your preferred workflow, we do offer Consulting as well.

We always need a fully formed bug report. See Contributing Bug Reports.

In the Google codereview app when it used to be possible to submit a raw diff for submitting code for review, it was quite simple to do that. The main issue is not the revision, the main issue is the path. So simply add a field in the submission form to provide the path to the root of the patch.

test

asd

Hmm strange, I do not use any md5 function. I simply copied the ArcanistTextLinter and changed it to work with files containing \r\n line ends. Thats the reason why I do not know where the md5 function all or the variables come from ^^

Cool, let us know if you run into trouble. I think it should be pretty easy to port any existing code which does generally transaction-like things, but might have missed something.

Then please follow our bug reporting guide: Contributing Bug Reports

Makes sense. Thank you for clarification.

I am asking phabricator. Since viewing raw php files doesn't work on deskop or laptop. So I am not sure what to set.

@paladox who are you talking to, specifically, the upstream or Wikimedia?

Hi the workaround works for mobile devices not desktops and laptops.

You have the path to the library directory twice, print out the variables
that you use in the md5 function.

My initial thought is that we should maybe just parse strings in various "almost certainly time" formats -- rather than adding a special syntax -- like:

D14575 passes transactions to HeraldAdapters, so custom HeraldActions may examine them. The action will receive concrete, persisted transactions which have been validated, merged, checked, and applied. This will land shortly.

Problems with these events which you are exposed to:

I was wondering, besides that :-)

Primarily, it only fires some of the time, per this task.

Not exactly because my result is:

fatal: unable to access 'http://phabricator.vonji.fr/diffusion/VJ/': The requested URL returned error: 403

And not:

fatal: Authentication failed for 'https://phablab.krautspace.de/diffusion/M/morecms.git/'

Some feedback from our Phabricator instance. At the moment, the way we have been testing usage of Spaces is:

• S 1: Public (Default). Our open-source projects go there.
• S 2: Internal. Visible only to employees. For this, we would really, really like some way to batch assign/add users to a Policy/Space, as discussed in T9780 and T4103#145539. Handling this manually quickly becomes impractical with large numbers of employees.
• S 3+: Long-running special interest projects. They do exist, and they tend to value their privacy.

In T9848#145709, @Mnkras wrote:

If you look at the error message and the path you can see what the issue is:

md5_file(/home/admwkiv924/phab/arcanist/src//home/admwkiv924/phab/arcanist/src/extensions/ArcanistPowerShellLinter.php): failed to open stream: No such file or directory at [/home/admwkiv924/phab/arcanist/src/lint/engine/ArcanistLintEngine.php:204]

2 is such a surprising limit, it misleads you. You look at your wiki and you think, "I was sure I wrote a page on X, but no, I guess I'll start a new one".