What was the push operation you tryed to do ? By default phabricator prevents dangerous changes (like history rewrite or other operations in which you have to use --force) but this can be disable in repository preferences..

I edited the answer to make it more clear.
If it works, you can upvote the answer and close the question as resolved.

You have to login using the one time loging token which you generate server side (command line) using /path/to/phabricator/bin/auth recover jpchristie.
Normally it pass all other auth. Then once loged in as administrator you can edit auth providers using auth administration.

Your welcome.

So please follow the guide from start again, then i or someone lese will helps debugging the "normal" stuff failing like permission in sudo, or git-executables not in path.

On http://phabricator.example.com/config/group/diffusion/ theire is all stuff you wanna configure ! In peculiar the ssh-port, the ssh-user ect.

Ah, oki. Was it not because comment are hidden field on new application form so if you can't edit the task, you can't edit the comment too.

because we have tooling which relies on the regular SSHD daemon being available on port 22. And thus, I have to add the remote like above.

@epriestley, not sure you are aware of this but the "create dropdown" (big "+" in navbar) still point manifest task to the default form.

Not sure what happened.
It seems logical that it also matches the caps since the @i in the regex. So it must be something else.
I would see tomorrow. Maybe it was just Cahier_des_charges fonctionelles (somehere no underscore but an space). But in my shell, since all was underlined i'm not sure I would have distinguished it but I was pretty sure I have look there wasn't space instead of underscore.

I didn't indended to submit as it was.
The description I edited just after was not send through my mobile tethered connection. I just have sended it now !

@epriestley i think I didn't delete index first.
Just bin/search index --all.

Next time, open a new ponder question (https://secure.phabricator.com/ponder/) per actual question you have, so it can serve for other people too. This task is mixing bug reports, general troubleshoting, cutsom homebrew troubleshoting and basic questions about how phabricator works. This thus makes hard for someone with same issue than you did to actually use the answser given in this task. That also makes core dev hard to close this task as resolved since there is a lot of different problem tackled.

I patched with D14370 and still get an issue. I can retry but I pretty sure I did think corectly.

Depending on what remote you have and what main branch you have.

@epriestley do you think it is worth trying to debug this ? those javelin components have alaways feel strange to me and for this one in peculiar, it really feels hard debugging it.

Can you gives more info/context. It is hard help without.

Edited, seems not to happen when week start on sunday !

@Gavin, on debian you should :

• install git-core (git is not enough)
• verify that git-http-backend exists in /usr/lib/git-core/git-http-backend
• make a link to something in your path (in my case /usr/bin)

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

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

I tested and i does not fix !

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 ??

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