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.

I'd love to see support for U2F keys, as well.

I'm just going to merge this into T5258. There are two separate issues here:

This bug does exist on this server, but unclear why. Maybe related to size of image, but probably best solution is some command-line tool to regenerate all file transforms? I don't think making PHIDs easy to find inside the app is very user friendly.

fwiw, I can't reproduce this on OSX chrome any more. going to go test windows in german.... wish me glück.

I retargeted this; I think the proposed solution is not the best solution we can find to the problem.

Doesn't look like the repository will even attempt to clone over HTTPS:

In T12950#230520, @chad wrote:

Why did they need regenerating in the first place?

Why did they need regenerating in the first place?

See Planning for information on progress and priorities.

Any progress on this issue? Agreed with @dariusz that this is my number one pet peeve. This is a pretty large omission from bulk editing capabilities for a column. I can set a task to move to a different column when I am commenting in a task. I'd expect the ability to do the same bulk process on a column of tasks, even if I could only move those tasks within the same workboard. Dragging and dropping tasks individually is extremely time consuming when I have to move tasks between columns.

This is an unusually low-tech solution but I can't think of any reasons why it won't work.