From elsewhere, it would also be nice if this tokenizer highlighted instance members of instances associated with the billing account. There isn't a straightforward way to determine which "joe" or whatever is correct right now that works better than "ask Joe what his account name is".

See this document for instructions on getting Phacility support:

From elsewhere, it would also be nice if this tokenizer highlighted instance members of instances associated with the billing account. There isn't a straightforward way to determine which "joe" or whatever is correct right now that works better than "ask Joe what his account name is".

The driving use case for this fell through, and I no longer plan to pursue it.

I'm going to merge this into T10748, since that's now clearly the way forward.

T10358 discusses a case where we use (valid, spec-compliant) JSON for presentation, but could use an alternate form which is more human readable (specifically, when displaying unicode characters).

The resolution of T7053 should indirectly resolve this.

Resolved via email.

I do need the user deleted. It is new and was created incorrectly. I just want it gone. I'll send a mail.

If you definitely want to delete the user (usually, it's better to just disable users), can you shoot us an email at support@phacility.com with your instance name and the user you want deleted?

What are you trying to do and where? Is there a reason to delete vs. just disabling the account?

As a minor technical point, you're trying to create imported repositories (i.e., import repositories from GitHub), not hosted repositories, right? This endpoint can't create hosted repositories at all, AFAIK.

This endpoint is very old and has a lot of problems, including not being cluster-aware. In the Phacility cluster, the web host and repository hosts are separated. repository.create can not create cluster-aware repositories.

Presuming that answers the question, let us know if not. T7148 is the general production task here.

Unsatisfying conclusion here, but:

(We caught up in IRC.)