The coffee on my desk doesn't seem to work yet - use a proper comparison.

Use standard JS string concatenation instead of shiny padStart() because better backwards compatibility

In D25630#17685, @valerio.bozzolan wrote:

I think somebody here would propose to avoid padStart() and be boring:

if (d_m.length < 2) {
  d_m = '0' + d_m;
}

In T15820#17365, @valerio.bozzolan wrote:

Just because we can, right? Or any real concern?

The approach taken in D25621 is more wholesome and preferable thus abandoning this

This makes sense.

Tested locally before and after applying this branch, with two users sending messages in a chat room after clicking the speechbubbles icon in top bar and selecting "Persistent Chat", both functionality wise (clicking the bar in the lower right corner) and by inspecting the element in the web browser's developer tools' inspector. Works as expected.

Thanks for working on this! Works pretty well locally. From a quick test of this branch, while being logged out,

• Maniphest Advanced Search: Setting Assigned to to Current Viewer, I get a Login page.
• Diffusion Commits Advanced Search: Setting Authors to Current Viewer, I get a Login page.
• Differential Advanced Search: Setting both Authors and Reviewers to Current Viewer, I get a Login page.
• Differential Advanced Search: Setting Responsible Users to Current Viewer, I get an exception (DifferentialResponsibleDatasource - probably another source to cover here?)

Should somebody file a ticket for that?

I'm purely setting "Request Changes" to reflect that IMHO this should not get merged until there is an approach to fix T15579 - otherwise in some corner cases this proposed change would create broken URIs.

I'd prefer not to expose this as an always-visible button simply because it takes screen estate on smaller screens.
Maybe an entry Copy Revision Permalink between two separators in the expandable "View Options" dropdown is an option?

I can confirm this works as expected for the task view itself in e.g. http://phorge.localhost/T1168 . This seems to also fix http://phorge.localhost/feed/ so it does not only show me about setting high priority on a new task, but instead shows that the task was created? That would be a nice side effect too IMO.

Tested this patch on http://phorge.localhost/feed/transactions/ and in the feed at the bottom of http://phorge.localhost/W20 itself.
Also tested changing panel visibility from Public to Admin only and accessing these URIs as an average user.
All working as expected, no explosions.

In T15815#17250, @valerio.bozzolan wrote:

being able to have people running unit tests and see the results in their language was a feature

I tested this one-liner as part of the downstream conversation that pppery and I had in https://phabricator.wikimedia.org/T363364, still I would ideally prefer another upstream opinion before accepting this revision as O1.

In D25608#17388, @avivey wrote:

This is probably the right fix (or maybe moving shouldAllowPublic() to the base PhabricatorFactController).

(Per my last comment)

I guess that would imply editing 15-20 *ConduitAPIMethod.php files which currently

$limit = $request->getValue('limit');
if (!$limit) {
  $limit = $this->getDefaultLimit();
}

and add something like

if (!is_int($limit) && !ctype_digit($limit)) {
  throw new Exception(pht('Field "limit" must be an integer value.'));
}

? Hmm.

That's because we applied D25415

Add return value (though it seems to make no difference)

I do not (yet?) understand the use case of this task.

This single-casing of a specific class is not ideal, but given the complexity of other proposals here I'd like to get the current four lines in. Any other opinions? :)

The underlying issue is way more contained now that rP7868ab3754fa is merged. I'm abandoning this revision to clean up my backlog.

Break long line into two

If we find 10 minutes, let's test this on every provider, as last time it gave us a little surprise on one of them

Oh neat, I see. Thanks!

@revi: Hi, could you please provide a list of steps to reproduce, if possible, and always exact Phorge version info? Thanks!

@revi: Hi, could you please provide a list of steps to reproduce, if possible, and always exact Phorge version info? Thanks!