If you want to see a funny thing, visit this page in your Phorge:

I would like to help in creating an account in docker.io for phorge, to publish again a similar image. It's not that difficult. But we need to use an official phorge.it email address, not a personal one.

In T15011#6569, @20after4 wrote:

There is a fully self-contained bitnami vm image which some people have had some luck with.

In D25304#8910, @Sten wrote:

Wanted to ensure you had a chance to check the changes I made based on your review first...

Wanted to ensure you had a chance to check the changes I made based on your review first...

No worries, I haven’t had time to dig in. I wanted to review D25067

For archaeologists: canUninstall = false for Audit got set in rP11861265fe94fa97e4d0563c5bdb7b8cac27282d

Hi @Sten also here feel free to

Sorry again for this regression @speck

I understand that nobody in the world likes refactoring. Even if it makes stuff more readable and a CPU cycle faster.

If a third person leaves a positive comment I would be for approving it in the master, also to receive more feedback, or eventual follow-up graphical suggestions :)

Hi @20after4 :) Can I ask you if this could be useful in Wikimedia? I think yep

This is a feature that was invaluable on wikimedia's use of phabricator, however, proliferation of a lot of forms can be troublesome / difficult to manage. Ideally the forms system could use some improvements to make things more manageable.

I think the current revision is a good compromise. The current behavior makes no sense from the perspective of modern UX patterns:

Thank you for clarifying!

Thank you speck since you helped me a lot in clarifying the situation.

Ah yeah please share that :) Premising I agree that losing the current token is a problem that can be fixed with "hey, prepare your token, 3, 2, 1, go!"

Oh, if your OS doesn't always show scrollbars, then I guess this wouldn't make a difference for you. There's probably an option somewhere to change that, if you wanted to test how it works for others. But this means that my proposed change shouldn't affect you either. :)

@Cigaryno Probably we should wait a bit before mentioning T15131 here

So probably as you can see, you are right that the operating system version is in use, but, in my operating system the bar is just awesome XD

Firefox on GNU/Linux with KDE desktop environment:

Firefox 115, Chromium 114, on Windows 10. Can you share screenshots from Firefox and Chromium on your device?

I cannot reproduce this problem with Firefox 113 provided by my distribution. What version are you using?

In D25303#8876, @speck wrote:

I like this idea. A few things I want to note

1. Could you post a screenie for what the breadcrumb rendering appears as?
2. Does the name of this new class follow other classes that extend the hierarchy? I’m guessing yes but just want to double-check.
3. Maniphest tasks will render their primary Space (assuming non-default) as a prefix to the title. I think wiki docs should do similar.
4. Do wiki docs have a description field?

I had discussed this with Evan previously and he gave a great explanation for why the current behavior exists, something he refers to as “spyglass attack”. I’d have to go back and review the explanation. What I recall the outcome being a few options, one of which was prompting the user that they are about to be promoted for MFA before issuing the challenge, to give the user time to prepare.

Thanks - the behavior I was seeing I think mirrors your own but the error I was getting was more directly related which confused me. It seems using @ does not clear the previous error from its use? Bleh.

I think updating the user script is a good idea if this functionality is needed.

I like this idea. A few things I want to note

1. Could you post a screenie for what the breadcrumb rendering appears as?
2. Does the name of this new class follow other classes that extend the hierarchy? I’m guessing yes but just want to double-check.
3. Maniphest tasks will render their primary Space (assuming non-default) as a prefix to the title. I think wiki docs should do similar.
4. Do wiki docs have a description field?

I wonder if there were plans to incorporate contact numbers with the prototype app for handling support (the name escapes me).

Eh, grep'ing the source, src/applications/metamta/engine/PhabricatorMailSMSEngine.php seems to be the only place reading those values.

Also, is it something shared to somebody? I think nope so I totally agree

In D25300#8786, @Sten wrote:

IMHO we should just do a global replacement on all 'if (strlen(<someVar>)) and have done with it. I have done this on my phabricator copy to get it working.

Agreed. The more often we specify the path, the more likely the reader will remember it.
Downside is we need to lose the path/to/ in order to keep lint happy.

Agreed. The more often we specify the path, the more likely the reader will remember it.

In T15161#4416, @avivey wrote:

I agree with this, but I think we should let this wait for broader discussion - there maybe good counter-arguments.

add dedicated CSS class

At this point, feel free to download the patch again and land it

I've tested the new revision with the soft error and this is a way better UX - thanks!

Run tests again (since they are marked as skipped now)