In general are you aware we no longer take bug reports or feature requests here?

In T12959#230799, @chad wrote:

What does "mysterious" mean.

What does "mysterious" mean.

In T8238#218018, @avivey wrote:

A possible mid-term solution is to use something like using refs which aren't "tags" (Like github's /refs/pulls/xxx); I think we've discussed it didn't like it because T8092 is desired for other things too.

Thanks for the explanation.

Named queries will get a new flag like isGlobal

I'm not proposing that, no. Here's exactly what I'm proposing:

At least, this is what I thought you were first proposing.

Basically the same UX as the home sidebar with home/dashboards.

OH yeah.

I wasn't planning to change the behavior of the dropdown, except that it would begin listing personal filters followed by global/default filters under "Saved Queries".

We're probably saying the same thing but maybe you wanted a simpler workaround first.

PHI29

Where's the other conversation?

I realize there are two conversations on this feature, I thought I was replying to the other thread.

Sorry, when I say "still" I mean like favorites on home.

I think we should still default search the top item.

I think we should still default search the top item. So if admins put "Super special search triggers" as the top item, that is the global default. One a user says OMG NO, and adds their first filter, that becomes their first item and thus their default search.

hmmmmmmmmmmm

oh thanks!

I don't think this is resolved, just an unclear report. To access this screen:

And one more, also for Kotlin.

No longer reproduces.

No longer valid as far as I can find.

Yeah this feels low value vs. building Dropbox. Closing in favor of overengineering.

It's discoverable in settings just fine.

Unclear if this is a feature request, bug report, or general question. Going to close out as it's old and not actionable.

I'm going to wontfix this. Functionally, everything is incorrect on the batch editor on a new install, if you have no users, no projects, no spaces. These don't seem to be too confusing to understand.

I think this is resolved with Related Objects now.

I can confirm this.

Doesn't seem to reproduce any more - I have no issue importing from another milestone. Presumed fixed, but if not, please reopen with more detailed reproduction steps.

seems ok now.

caret now appears when attaching dropdown menus to buttons.

Just launched a test instancepoo and everything seems fine.

Resolved enough.

I wonder if this OOM error can also be hit in other workflow though, given that it seems to occur in PhabricatorFileStorageEngine::getRawFileDataIterator.

Yep, agreed that the re-targeted proposal is a better solution... I had just assumed that this was a documentation oversight.

The plan forward here is to correct the text. I will follow up with you on Discourse.

We require the "a revision's reviewers can always..." behavior. Please implement it instead of changing the text.

D7150 added this text ("a revision's reviewers can always...") and I said it "wasn't true but would be soon", but never made it true.

remind me to add some more icons for Link.

That looks pretty hawt.

Happy to take a look if you found a reasonable way to get access to $request. If you're reading $_REQUEST['__path__'] directly or something though the eventual upstream version probably won't look too similar.

I've written a patch to make this work for the project sidebar nav for my organization's install. I don't want to take up your time with it if it's not helpful, but let me know if you'd like me to push a diff.

PHI27 is likely adjacent here.