By the way, can bin/aphlictuse the same if user <> phd.user then try to sudo to phd.user and run else run mecanism than bin/phd

Does GIT_CURL_VERBOSE=1 git clone http://phabricator.local/diffusion/TEST/test.gitdoesn't give you useful informations ?

I think we need a theyseemerolling macro for the occasion

I guess some absolute value somewhere maybe while(abs(start--)) instead

I trust my eyes but how !

It doesn't seems to works with color AND spin

{icon heart spin color=red}

{icon heart color=red spin}

I tested and i does not fix !

Does this also add the buildable repository asdefault repository cloned ?

Reopened since the main concern was more the installation of T9669 and theire is still pending question.

@marceldegraaf : i did the first part (almanac + drydock almanac based host blueprint) of how to configure drydock here : Q179: How do you configure an Almanac based Drydock resource but not found time to get the second part (drydock working copy blueprint + harbormaster + herald). Say me if you wanna details the last part in a ponder question or shall I do it later when i have time.

it is exactly T9669 : should i merge this one into mine ?

Basically you need to extra set the repo to be cloned. The UI is kinda misleading and the exception is not handled correctly when allow_phid is null

marceldegraf see T9669: Harbormaster working copy build step shouldn't crash when user don't set any also clone repository

Uhm I tested the same last month when 2.0 was still beta then conclude that phabricator only supported 1.x.
I will follow the resolution of this.

Doing

diff --git a/src/applications/harbormaster/step/HarbormasterLeaseWorkingCopyBuildStepImplementation.php b/src/applications/harbormaster/step/HarbormasterLeaseWorkingCopyBuildStepImplementation.php
index 3c4d18f..9e20b6c 100644
--- a/src/applications/harbormaster/step/HarbormasterLeaseWorkingCopyBuildStepImplementation.php
+++ b/src/applications/harbormaster/step/HarbormasterLeaseWorkingCopyBuildStepImplementation.php
@@ -43,7 +43,9 @@ final class HarbormasterLeaseWorkingCopyBuildStepImplementation

This would be awesome !

If you agree can I submit a fix :

• same as rP43569d4e278c365a1feb9497acfa4ce336a8262c for first part
• if needed (maybe first part solve all later on by adding buildable.repository if no repository are selected) a modification of UI that say that clone instead of also clone and make it required.

Basically I see two problems:

• the fact that null isn't a normal argument and should be and empty array : it thus for me seems very similar with T9631: Don't crash when users fail to specify additional working copies and should be easy to fix
• the fact that it is not working while all seem's to be set correctly (that is the reason I posted all this (let me know if you need more). It seem's to be a reall problem too but it is probably just me being dumb !

Or it is just flood.

I guess you post this on the wrong instance !!

I did this since I thought (very dumb estimation) that working copy would need access to phabricator back (to clone ect).
I discovered later it wasn't the case and created a bot user with an other keypair and then forget to edit this.

I will edit my answer.
Thank you Sir !

@epriestley : is making /var/drydock non hard written or just documented part of this ??

@cspeckmim thank you from the multiple advices. I will correct this soon(TM).

I would be please to help and do it right (this time).

I did :

• write the diff
• commit it
• patched my remote non-production phab, tested it
• create the revision, get linting issue, canceling the rev, refactor it and indent it properly (this introduces the error), amend it to existing, send skiping unit (since my laptop mysql was not working since update and since i was on travel, it wasn't easy to reinstall it)
• since i was on travel, I thought you won't send it as it is (I should have had the WIP on title) since unit was skipped
• when i reconnected, cathed my error, audit it , contact you on irc, created a diff but vlada was faster

Yes my bad ! I was going to submit the same fix.
Y made a typo when amending changes to correct the indent on linting.

@epriestley : I just see I made a typo I typo this when reindenting !

@epriestley :correct me if Im wrong, the way of fixing this is searching in the file that describe code block ?
Then i look for code in $this->getEngine()->isHTMLMailMode() blocks and try to get it right ? Seems easy for color, a little bit less for the gap.

In T9524#139448, @epriestley wrote:

Yeah. If we did the bar UI, I think the length of the bar is just "U + C" (divided by the longest bar shown on the page, I guess? Or like log-base-something of that so the absolute length of the bar always has about the same meaning?) with something like "C / (U + C)" percent of it colored in.

Or it could just say "2% of 23,000 Coverable Lines" but I suspect that would be harder to parse at a glance than a bar if you have a bunch of subdirectories.

Ok so I hava done what you advices me and im gonna submited this.
However to make it more clear, won't it be better to just add a new can_create policy.
I guess it should be able to say that admin are only willing "Moderator" members to create a new task but then the others users may comment it (I guess, you are probably gonna want that once Nuance is out).

Well a dark theme seems to require much more effort than this and be painless to support.
However I think after @epriestley works on high contrast theme, you can do the same as extension., if you want to code it.

@epriestley : something like this would be correct ?
Is there unit test I must write for this ?

• Checking version

Oki.

Oki this is much more clear so Worflow here is a javelin workflow.
Greping workflow in phabricator get me so much different workflow type that i was lost.

Is it possible to make 4 messages (not installed - old v1 - medium v2 - recent v2). Or this is too much complexity ?
Anyway, I will start this and then you put this on hold till Pygments release the new version, if you want ! Is it ok ?

I will purpose a diff too !

I found pha-get amazing thought.

So @chad are you oki for letting me contribute?

Woooh. That is fast, clear and precise. I will do it next week.