Sorry for not getting back sooner.

We haven't received more information about this in a few days, so I'm going to close it. Feel free to file a new request in the future, we just prefer not to keep requests open if they're outside of our control to move forward with.

We haven't ever experienced this, nor have we seen reports of users other than you experiencing it. This ("basically prevent the server from doing any other work") doesn't sound like a description of how properly configured servers are generally expected to work. My expectation of modern systems is that they have sophisticated schedulers which are largely fair in allocating resources and produce generally reasonable behavior, and this is consistent with my experience.

If this feature is valuable for you, I think you should implement it in your mail client rather than pursue implementation in every piece of software you use for work. A client-side solution could give you complete coverage with one implementation, and would be more powerful because it could perform additional filtering (e.g., allow important emails through even during off times, or deliver messages but not play an audio alert during off times, or ironically block family communication during work hours instead).

• Please report security issues via HackerOne.
• This isn't a valid bug report: it is missing required information. See Contributing Bug Reports.
• I can't reproduce this. Here's an HTML file which is properly escaped:

Feel free to file a new task when you encounter actual problems with real text and we can look at adjusting the limit, adding an additional block-level difference phase, rewriting PhutilEditDistanceMatrix in C (see T2312), or other approaches. We can make a better decision based on concrete examples of where the current solution is falling short than by guessing where issues might arise.

This is custom code.

That's why I said In my fork. This is custom code.

@epriestley thank you very much for the fast update and fix. It is working now with my example, and should be much better with a lot of pages.

how could you do this?
i cant find this configuration in my phabricator application

how could u do this?
i can't find this configuration in my phabricator

For users of the Docker container, there is now a workaround available (enabled by default), which ensures that Git processes are automatically killed if the CPU wait averages above 50% in the last minute. The commit that enables this functionality is available to view here: https://github.com/hach-que-docker/phabricator/commit/0e77c36f694605371e85d420c4aecfbd3023ec5a

We don't take hypothetical feature requests, unfortunately. See Contributing Feature Requests for what information we require. General Chat and Ponder are also available to discuss Phabricator in general as well.

https://mozilla.github.io/pdf.js/

Ah I totally missed the F1234 being in the lightbox already. And I did figure that using 3rd party code to render PDF would be out of the question. I don't really know what the current state of PDFs in browsers is so I had my project manager hat on for that question~

• I don't think that's a lightbox bug, just a general blog bug.
• To be fixed.
• If it's native? We won't be adding third party code for this.
• We added F1234 to the header of the lightbox for resharing.

Woo came here from the blog. Just a few notes so far:

1. The lightbox on the blog doesn't seem to show anything under the Comment pane even though I should be logged in (to admin.phacility.com). Or is the blog.phacility.com completely isolated/separate? These were errors I got in Firefox console, which I don't get when using lightbox on this instance.
   • Error: JX.$('phabricator-help-menu') call matched no nodes.
   • XHR POST https://blog.phacility.com/file/thread/PHID-FILE-3ittlvgojn2326tbg22z/ [HTTP/1.1 404 Not Found 338ms]
2. I'm very used to "click anywhere that isn't the image to close the lightbox" behavior. My personal preference would be to maintain that when clicking on any empty space outside the image/file. I think this is due to where my mouse is located when I click the image (towards center of screen usually) and where I would go to click to close (in most cases just slightly down vs. top right corner). But then I use a trackball so...
3. Is PDF preview considered? PDFs were specifically mentioned in the blog so I have to ask~
4. (Maybe not totally related) Some way to easily reference the same file instance from different areas. Most users I see will continue to drag/drop the same file in different areas and not use the same file reference object {F1234} - which I'm assuming would mean two separate comment chains, etc. Maybe somewhere in the lightbox listing the tasks/diffs/etc. where the file is referenced would help understanding. Or a way to view/copy the file remarkup to be used elsewhere. Or maybe this is all T11543.

Thank you! The new dialog looks excellent, it would have prevented my error.

Here's the revised dialog after D16956:

I don't think that edit is always invalid: offhand, one reason you might want to make such an edit is so that you can add a tag to all events in a series, allowing you to query them so they can be exported to another calendar. Another case I could imagine is wanting to correct a mistake in the description of an event when you know nothing will be lost by editing future events (e.g., because you are the only user who can edit the event).

No.

Is anything remotely like this already available somewhere? I would love to be able to see all my currently active tasks in currently active milestones to get an overview over the work I have to do during the next days. Right now I am using multiple workboards to achieve this: One "project X - week N" milestone for each project I am involved in and another "week N" milestone for myself, to be able to see all tasks I have to finish this week. If this could be simplified, that would be awesome!

Thanks for the explanation!

(To answer your question more directly: yeah, no way to do pht() with variables in Javascript. We can build that without TOO much trouble, but I'd like to wait for a really good use case first.)

I do not plan to pursue any variation on points which can not be summed in a linear way. You can find some discussion under "Quantitative" in T4427#157820.

I'd say just get rid of it, or render "X / Y" without pht()?

Doesn't look possible to do "Image x of y" in current phtize from JS... Worth adding or just changing the language? I don't have any great ideas on updating the language. Unsure x of y is useful though.

Thanks Chad! Will update it frequently :)

Maybe it would also be sensible to not allow mass-edits to be triggered by past events. While it may be useful to tweak a single past event, I don't see much of a use case of updating all events starting from some past date. I'd argue that that is nearly always unintended.

• Availability cache build on All-Day events may be off, I didn't pick up a dot for E1222.

Generally recommend updating weekly to stable. Also, if you have questions / need help, we always assume you're on the latest stable release. Updating frequently / before asking questions helps reduce support costs for us. Thanks!

The panel was updated in D16806, on Nov 6. Upgrade Phabricator to see these changes.

We're using this version:

phabricator 111c63955155046bbd57c3836c78d460ebe13dfb (Sat, Nov 5) 
arcanist e17fe43ca3fe6dc6dd0b5ce056f56310ea1d3d51 (Oct 22 2016) 
phutil 40e473e057885dab5de4fb42901f7fff2d340a6a (Sat, Nov 5)

In /config/version/

how do I find out which version I have?

Haha, Badges.

Very Nice!

Couple of other things:

Likewise if this only might cause confusion, but has not actually caused confusion yet, it's a hypothetical problem (see Hypotheticals). We don't accept requests to address hypothetical problems because they often never actually occur.

Is your Phabricator up to date?

Please read and follow the guidelines in Contributing Feature Requests and Describing Root Problems. These are required for any request. Specifically this request still omits a root problem and seems to be just a design / ux suggestion. Given we have thousands of tasks and 2 developers, we don't take feature requests that don't have a root problem, we'd never be able to prioritize them.

Thank you very much, I'll take a look :)

Sorry about that. I have added more details to the description.

This request doesn't describe a root problem (see Describing Root Problems), but we can only accept feature requests which completely describe root problems. See Contributing Feature Requests for more.