Do not use consts but keep the two pixel values defined in getMaxTransformDimensions(), make function non-static

Oh, I miss-understood the problem statement. The 4096 limit is on the size of the image that we can resize from...

Maybe since "we live in interesting times" we can increase such limit indeed also, but that logic makes some sense (but terrible user experience, I agree lol)

I also thought that, but I think the current limitation (4096 x 4096) is reasonable and was introduced to avoid to scale huge things and mitigate resource exhaustion in thumb generation.

I'd expect it to just resize the image as needed....

Still untested but seems nice thanks <3

Yes, I got the idea. It's a feasible workaround.

Yep, maybe the "Dummy project" can be a "personal project", that is, just a workboard with your name, like this:

In D25862#23134, @aklapper wrote:

@Cigaryno: What is your motivation behind and which actual problem are you trying to solve by this? For example, there are now 4 out of ~25000 patches tagged with Projects if I was about to search for patches tagged with Projects. I can imagine tags to be partially useful on Maniphest tasks and I fail to see the advantage for Differential patches so far.

@Cigaryno: What is your motivation behind and which actual problem are you trying to solve by this? For example, there are now 4 out of ~25000 patches tagged with Projects if I was about to search for patches tagged with Projects. I can imagine tags to be partially useful on Maniphest tasks and I fail to see the advantage for Differential patches so far.

@akplapper just to ask, is adding tags to revs pointless or this isn't the right revision for adding tags to?

@Cigaryno: Could you please not add project tags to patches? You seem to be the only person doing this lately, and it creates notifications that others need to read. Thanks.

• mb_chr(215) because arc lint dislikes funky ×
• const MAX_TRANSFORM_* because arc lint does not like private const, so maybe PhabricatorFileImageTransform::getMaxTransformDimensions() is overengineering as I could also access the two consts directly instead
• Cannot private const int because that requires PHP 8.3 (type safety haha)

Ah, I'm the author of this. Yes, let's abyss into decline. Thanks Andre

As a development software site, I don't think we need to support Google OAuth.

Yeah no problem.

It was my fault, I did not pay attention to the fact that in the right panel "list of added files" the files I add are marked with restricted access, with notification 'This file is referenced by this object, but not formally attached to it. Users who can see the object may not be able to see the file.' Can i adjust show my attached files all user by default .Thanks

Please answer my questions via text. The two images can only be seen by you.

{F2878762}
{F2878763}

Create a task in Phorge and attach a file (e.g., a screenshot or document).

Thanks revi. Dear @dereckson probably your nice installation is still on the legacy Phabricator? (or a Phorge before 2023 Week 17, accordingly to wiki search results)

Cannot repro on current stable (rPd3c0a7edc3fc and rARC05abd055019c as of today). Tested on local installation.

Mark as "oh noooo boring comments from bozz" :3