I think it sort-of does something if you upload an irregularly-sized image (say, 100x200) instead of a square image. But I don't think it's particularly useful or works well even in that case, and I definitely support getting rid of it.

Should basically just be UI, yeah.

Looks like we use the function to mean "codepoints" in some places in phabricator/.

With no claim that this is the world's most elegant fix, I think this may be a fix:

In the short term, I'll accept a patch to do this if you want to test it?

T9640 and T2383 are somewhat related.

When you upload a file that is stored as chunks, the chunks are also files. For example, file F123 may have chunks F124, F125, F126, etc. These files are not normally visible in the web UI but you can see that the next file you upload will skip some numbers (e.g., be F127).

Why do you believe that files which are split into chunks don't get encrypted?

The examples that use the BYSETPOS and WKST rules are omitted, because these rules are not supported by Oracle Application Server Containers for J2EE.

I'm sorry you feel that way. These kinds of requests are frustrating for us too, which is why we try to make it clear upfront in the documentation that this is not an appropriate forum for them.

Since it doesn't seem like the documentation is incorrect anywhere, this doesn't appear to describe a bug in Phabricator which we can accept upstream. See Support Resources and Contributing Bug Reports for details on what we do and do not provide support for.

Please file a new task following Contributing Feature Requests if you'd like us to consider your feature request. We do not track resolved tickets.

Please see Contributing Feature Requests and Describing Root Problems for guidance on filing a valid feature request. You need to follow all the instructions in those documents before we can accept your request upstream.

Additionally, coming to phabricator, my expectation is that arcanist would handle the front-end (i.e. phabricator), but not strong-arming my local development environment.

That document says:

What led you to arc land, specifically?

Also possible is stuff like "the diff has a custom policy which you destroyed", etc.

If an object exists but is failing to load, it's usually because a required related object does not exist (in most cases, "required" means "required in order to evaluate policy checks").

This isn't a bug -- I think we've just set you up with the wrong expectations somehow. There's probably some sort of documentation we can improve to make it more clear what arc land does, and maybe I can figure out how where we led you astray by asking some questions:

Thanks!

Yeah, ON DUPLICATE KEY UPDATE is sensitive to order. Setup:

I think this is:

(The major goal of using refs instead of tags wouldn't really be to hide them per se, just to make them extremely difficult to fetch by accident.)

Maybe my assumptions about default behaviors are off, or the more-recent base tags (but not necessarily the diff tags) are getting fetched because they're often ancestors of master?

I'm a little confused about how these tags are appearing so widely in developer working copies in the first place. Is git clone fetching them by default? Do you have unusual default options configured? Do users regularly explicitly fetch all tags present in the remote?

I think cleaning up closed tags probably isn't a particularly great long-term solution since some fraction of the revisions likely just get left open forever -- so you'd have 500 tags instead of 50000, but I assume that still causes about as many problems, and you'll be back to 50000 in just 100 more years anyway.

See some discussion in T7944, particularly T7944#194982.

We're planning to put application-level stemming on the MySQL index (see T6740). Are there problems with the InnoDB search that you're aware of that aren't fixable with application adjustments?

I clicked "Update Now" and the update frequency for our most active repository has dropped back down to 15 seconds.

(I'll follow up on this once I have a chance to bang on it a bit, but I want to try to finish up the RRULE stuff while it's still somewhat fresh in my mind.)

This went out a while ago and I confirmed the fix in production.

I'm going to presume we got this, but reopen or yell if you're still seeing issues on the new code.

Thanks for the report! The detailed reproduction instructions were very helpful in resolving this.

I'm also not sure if we can use SVG as a data: URL in CSS. It probably should work, but if it doesn't we'll have to rasterize (and, I guess, serve 5+ different sizes to every user).

Alright -- we can have bin/celerity map rasterize SVG into arbitrary sizes if I'm not comfortable serving SVG directly from Celerity.

• Create a badge.
• Award it to a user.
• Visit their profile page.
• On the profile page, the badge title should link to the badge detail page (currently: no way to get to the badge detail page).

I'm not really sure this is actually useful given that every method is now named <application>.whatever and you can search by substring.

(That will give us slightly bad scale-downs on 1X screens, but I bet they're not worse than scaling down an SVG would be.)

I think we can just do 2x in all cases for these, if that's reasonable?

This one is a little scattered, so let me know where I can fill in any gaps. Most of the details are in D16178.

Do you have any use cases which are not approximately some flavor of: