Does this resource load for you?

Just tried again.

Done...Thanks

Install the gd extension.

When I trying to update the hosted repository from the remote GIT installed location. It is throwing following error message:
Error updating working copy: Command failed with error #255!
COMMAND
git fetch origin '+refs/*:refs/*' --prune

Linters that wish to make changes should emit a line and character position (or an absolute offset), "old" text (the incorrect text to replace) and "new" text (the suggested text to replace it with) -- for script-and-regex, these are original and replacement. They should tell arc what to fix; they should not mutate the working copy themselves.

Eh ... I just opened up an incognito tab and it didn't reproduce so maybe this is just something wonky on my end. Feel free to close this if it doesn't reproduce for you guys.

Totally my fault, I just didn't read half that sentence. 🐈

Thanks for looking into this so quickly.

And thanks for the report! Let us know if you run into anything else.

D17687 should dirty the cache properly on username changes. It should promote to stable within the next ~12 hours, and deploy to Phacility production about 24 hours from now.

I was able to resolve the issue by deleting my user's ssh key, and uploading the original ssh key material as a new Phabricator sshkey.

See also somewhat-related task T12397.

Not that I've geeked out about it.

Slack has the best version of Lato they home-cooked to have more letter-spacing. I wish it was open source.

It does look significantly better on secure.phabricator.com than it does on the internal version, at least to me, so I suspect the changed font resolves this.

I expect it to be better, but I don't know offhand. If it's still a problem, knowing real title cases might be helpful. It sounds like some sort of metadata is being set in the task title?

Good to know. Thanks!

5e16e460396e changed the header fonts, from Aleo to Lato. It's a different font on this install than the version you're running internally.

Also an out of date version of Phabricator.

We're running 216f6be11ece53cb1daafc8fff636dbdb0d7ef3d, not the SHA given above.

We only accept bug reports of current versions of Phabricator.

In particular, when you connect over HTTP to a security.require-https install, we normally just immediately redirect you to https://....

Was this on a test install on localhost? I can only reproduce this if the remote address is part of cluster.addresses.

This could definitely be more clear, but I think this is currently expected -- you still need to have valid configuration even when providing additional administrative credentials.

Actually, I figured it out... The problem was that I had security.require-https set to true but I hadn't yet setup HTTPS so I was only using plain old HTTP.

I tried to reproduce this on a Phacility host, but it doesn't reproduce there because the first user account is setup via OAuth.

• PhabricatorSyntaxHighlightingConfigOptions defines this option.
• Change the type from wild to custom:SomeClassName to switch to a custom type validator.
• The new validator class should subclass PhabricatorConfigJSONOptionType.
• You can look at PhabricatorKeyringConfigOptionType for a (more complex) example of how to validate a value.
• Test by trying to change the value to something invalid, you should get an error.
• You can test a regexp is valid like this:

Crazy, I guess I'm in some project called ? ?

Can you unhide the event please so I can fix my notifications?

Well now I have 4 notifications I can't see or reset. :(

Yeah, the user is struck through because they are "closed", which is because they are a bot. This isn't the best way to deal with this, but it dates from early 2014 (D8231) when everything was simpler.

Ah I missed that sentence above, this is why the bot user is disabled:

Mailing list and bot users are also considered "closed" because you usually want to hit normal users instead of them.

Another instance of the bug her:

Sorry, I should have thought about that!

@ivo Just a reminder this is a real install, please do not create test events on it. You can use a free instance on http://phacility.com/ if you want a clean, up to date install to test against.

My intended fix here is:

Running multiple different versions of Phabricator on a single host is not currently supported. We should probably handle this situation better than we do, and there is no technical reason we can't support this, but this use case is very rare.

I'v checked that

Thanks for the quick fix!

This should be fixed at HEAD of master, thanks for the report!