Thanks. I've done a full update with the sample script at https://secure.phabricator.com/book/phabricator/article/upgrading/ and got the same error.

I'd do a full update to Phabricator (pull most recent) and restart php/apache. Generally "Class not found" indicates somethings out of sync or not updated properly.

So these are all unreachable commits that have now been imported?

In T11188#181667, @epriestley wrote:

Are all of these events commits?

I got the error after the following commit

8cdafb0 - Allow users to set a line-height in their monospaced font preference

I did a full update and restart httpd and phd, and that's what I got. How I can provide more information for debugging? Thanks.

I'd do a full update to Phabricator (pull most recent) and restart php/apache. Generally "Class not found" indicates somethings out of sync or not updated properly.

I've never seen that error occur before. Can you provide steps to reproduce the error?

I've never heard of anyone running into an issue like this, and there are no tools to clean it up.

Are all of these events commits?

My PhabricatorRepositoryPullLocalDaemon is not working, with the above error. Can anyone help? Thanks.

I explained this above, in T11187#181641.

Why the customfields are not displayed in the history in the maniphest view, but only once in details?

See T3179.

I dont want to impersonate. I want to preserve a history from a redmine stack using a customfield like edited-by. Unfortunately this field wont be displayed in tasks/all. What should I do?

No. Phabricator is explicitly designed to make it impossible to impersonate other users.

May is it possible using a maniphest.customfield like 'edited-by'?

By design, it is not possible to impersonate other users over Conduit. There is no transaction you can construct which will list any user other than the authenticated user as the author.

Thx, could you give me please an example transaction, where another author than 'user' will be listed in history as editor?

When you apply a group of changes with a *.edit endpoint, they are all applied at once, as though you had submitted an "Edit" form or a comment with actions. In particular, this means:

We haven't seen any other users run into difficulty with this, but we'll keep an eye on it and consider updating the documentation if we see further confusion.

OK, I understand now what is the point

OK, I think I get it

That also doesn't look like a working copy.

I should have checked if there exists a verbose output first :-D
Anyway, here is the output :

14:21 grooveek@anlin ~/Projects/test-phabricator%  arc install-certificate --trace                                                           
 ARGV  '/home/grooveek/Projects/arcanist/bin/../scripts/arcanist.php' 'install-certificate' '--trace'
 LOAD  Loaded "phutil" from "/home/grooveek/Projects/libphutil/src".
 LOAD  Loaded "arcanist" from "/home/grooveek/Projects/arcanist/src".
Config: Did not find user configuration at "/home/grooveek/.arcrc".
Config: Did not find system configuration at "/etc/arcconfig".
Working Copy: No candidate locations for .arcconfig from this working directory.
Working Copy: Path "/home/grooveek/Projects/test-phabricator" is not in any working copy.
Usage Exception: Specify an explicit URI or run this command from within a project which is configured with a .arcconfig.

Great! Yeah, make sure to restart both after upgrading or you can be left running old code against a new schema, as here.

Working Copy: Path "/home/fl.blondeau/NetBeansProjects/namescan-phabricator" is not in any working copy.

@epriestley wow, ok thanks that seemed to work. ( I did restart nginx and phd but clearly not fpm)

Did you restart your webserver after updating? See Restarting Phabricator for help.

Can you try arc install-certificate --trace, and show me the output?

As it says clearly on the home page, this is not a test install - if you want to try something launch a free Phacility test instance.

If there have something to know.

Sorry this isn't a place to test, I quote:

I tried to reproduce your steps :

name

In T3025#181309, @jayvdb wrote:

I saved "Ignore Conflict" here and on phabricator.wikimedia.org , but a few hours later the warning message overlay has reappeared. Im going to ignore it here, so that the devs can see when I last saved "Ignore Conflict".

I am bad at code review :(

dafuq?

question

um

I pushed that junk here, yell if anyone catches issues.

I sure wrote some Javascript today

Cool. The expectation is that this won't happen again going forward (we should automatically compute reachability from here on out). Let us know if you see it again in the same repository. If we get a few more reports maybe I'll make the error message mention this command.

That did it, thanks!

Try bin/repository mark-reachable rXYZ (and show me the output, maybe)?

Thanks, this is working now.

Let me know if that doesn't fix things. Expected behavior is:

Thanks for all the help digging into this, there is pretty much zero chance I would have guessed that on my own. I think D16149 should fix this properly, I was able to reproduce a similar error once I knew what I was after.

This is in all likelihood a mistake made forever ago but I'll wait for a potential patch.

O.o

Okay, I figured this out:

Thanks! Looks like we have things flipped for some reason. Let me see if if I can track that down. I think I should have a patch in an hour or so, or I'll let you know if I need anything else.

object 78daf8de9fe15dce0b4d0e1945a57c778e0536d7
type tag
tag v2.11.1
tagger Test User <test@test.com> 1413916998 -0400

tagging v2.11.1

We should be able to parse any repository in any state, so don't delete the tag!

If it requires us to delete the v2.11.1 tag then so be it, we understand that maybe we did something wild with history in the past but that tag doesn't really give us anything anymore so it can go.

Had to redact a bit:

(I suspect v2.11.1 is a tag-object and the tag-hash and object-hash are getting mixed up somehow, but hopefully the full command will shed some light on things.)

Hrrm, I'm very confused by that behavior.

The repo uses callsign P and refers to Platform.