I'm also not sure how well arc patch handoff has been working for you, but T8090 has some discussion of some more reliable approaches we're evaluating and moving toward.

This is an artifact of the PHP json_encode() method's rules for guessing whether a PHP array is an JSON object or a JSON list.

Development Log

Thanks! 99% sure that's the fix, then: you're on a 32-bit system and the 'int' type can't represent the 64-bit chronologicalKey.

It's possible that the paging code is breaking somehow, although I still haven't been able to reproduce this and can't see any way it could. Can you log the value of $cursor passed to getPagingValueMap() each time through the loop? It should look like this:

We aren't interested in making this a default.

Thanks! I think D13245 should really fix this.

Although T4207 is sort of related, in that it proposes a new kind of "parent/child" relationship (distinct from "blocks / blocked by").

Oh, sorry, I completely misread, ignore me.

See T4207 for task graphs.

There is no way to disable this.

You can likely work around it in the meantime by setting isEmailVerified to 1 in that table. (I expect D13239 will land in the next few hours.)

Sorry, bad at reading. Yeah, that's the issue. D13239 will fix things.

Oh, is auth.email-domains set?

I poked at this a bit, but it doesn't feel great to me, at least with the current header design:

D13239 will fix this in some cases.

Maybe. Do you have approval queues on, or email verification on?

I can't reproduce this locally.

(If you can, set debug.time-limit to 10 and then repro it; it should give you a more useful stack trace.)

Can you reproduce this by calling feed.query manually from the web UI?

No problem, let us know if you run into anything else.

You can use maniphest.statuses in Config to create, remove, or change statuses.

I'm also still not totally sure that we need/want icons. I'm probably going to do a diff where we just use the icon everywhere and see if that looks reasonable or not. If it's better than names, we can go from there.

Hmm.. I'm not sure if we'd pick up enough generic/flexible icons to justify adding it. A lot of the icons seem not-generic-enough or duplicated in Font Awesome.

After thinking about this, I sort of like reserving some of the more geometric shapes for Badges (T6526), since v1 is probably going to have to use icons.

I can't reproduce this. I created T8499 and immediately received mail about it to my "molepeople" list:

Development Log

This looks like it's done, although we may revisit it after T8434 has a more solid path forward.

If you want to pick some unobjectionable "default" token which is not a valid tag or branch name in Git or Mercurial (and, ideally, unlikely to ever be a valid ref in any VCS) I'm happy to implement that and shove it in the documentation. Not great, but seems least-bad to me.

I think the original form only worked by accident, we don't use it in the UI anywhere. This behavior likely changed when I fixed T7100.

I'm not sure how much I'd trust a !space command to be honest.

I think the difference with the Wikimedia Procurement use case is that tasks with files are created via email (i.e. a provider sends an offer to an email address).

At HEAD, the underlying use case discussed on that task should already be secure:

Here's how it works slightly-ahead-of-HEAD:

I believe this is effectively complete. We'll probably look at revising the control itself at some point, but I think it's likely fine until we do a more complete iteration on these UIs as part of T6943.

Presuming resolved, yell if anyone's still running into issues.

This has been implicated in other crimes by @csilvers.

I'll find a way!

I'm tentatively going to close this out, but yell if the "Private Correspondence" thing sucks and we can find another approach or find ways to refine it. I sleep better at night knowing handles aren't loading other handles, though.

Implement a new subclass of PassphraseCredentialType which works like PassphraseCredentialTypePassword but stores a large block of text (like a configuration file, or a secret will, or the eldritch words of command which must not fall on mortal ears). This could be called "Note" or "Block" or "Blob" or something similar.

You've hit this too, do you want to try to figure it out?

This is probably a one-line implements PhabricatorMentionableInterface on PholioMock.

• One possible cause of this is the application not being installed. If so, the documentation should make this more clear.
• Another possible cause is the active link to phabricator.example.com being confusing.
• The current modern approach to communicating how to get places is to use the {nav X > Y} element to show the user how to navigate: Applications → OAuth Server → Create Application. This is more resistant to UI/URI changes and teaches the user how to use the application.

• Add an 'outdated' (or similar) key after 'updated'.
  • It should map to the vector array('-updated', '-id').
  • Give 'updated' and 'outdated' human-readable names which better reflect their meanings.
  • It should appear after 'updated' in the order list.

Oh, I guess T5681 is the better fit, although the two are closely related.

(And likewise for View Policy.)

Folding this entire distinction into a modal choice at creation time seems reasonable to me.

It's technically accurate!

I plan to add a "note" or "text" type to Passphrase to handle this, but there isn't a good approach now.

I think I can cheat it in in like 3 lines of code so maybe we can try it and see if it sticks out.

I think the current state is good and would want to keep it in all the non-handle UIs (menu, Conpherence, column, etc.). I'm pretty sure the only places you actually see a Conpherence handle right now are:

Development Log

static title for untitled threads

Well, I think I figured this one out. No one look at the diff, it's real embarrassing.

@btrahan, per D13216, I'd ideally like to stop this class of problem by getting rid of the need for Conpherence threads to load other handles in order to load their own handles (I believe they're the only case where we do that) but that seems a bit tricky since we need them to generate the titles of some threads.