Releeph is a prototype application but not officially listed as one. This is a long and complicated story. Releeph is not ready for external use.

Hey chad,

Closed by commit rP8ebe9cea92d6.

I am not able to replicate any install bug on my test install. For installing Prototypes, make sure you have phabricator.show-prototypes set to true.

What are you using Releeph for? It's currently a prototype application and not for general use.

Hi Evan,

The UI here is a little misleading. Use the "Applications" application to install or uninstall applications: find the application in the "Applications" application, then click the "Help/Options" gear icon to install or uninstall it.

Need to test a few more devices, browsers, but go ahead and try this locally if you can:

font-size: 1px might also work. :3

I'd rather have a defective footer in 1 homepage that looks correct in 1000s of tasks than no footer at all. Anytime. Please don't remove it.

(I will take a 5 minute sweep and see what the landscape looks like)

@aklapper that will solve one bad page, but there will be others (Differential File Tree?). If people are already hitting issue with the footer, we might want to just remove the feature quickly until we have bandwidth to properly test/support all use cases.

@aklapper that will solve one bad page, but there will be others (Differential File Tree?). If people are already hitting issue with the footer, we might want to just remove the feature quickly until we have bandwidth to properly test/support all use cases.

This was known when we added the option, our assumption being people would work around the issue.

Ugly, but as I spot

.phabricator-nav-column-background {
  width: 204px; }

for the sidebar, one could set

.phabricator-standard-page-footer {
  padding: 8px 0px 8px 205px; }

maybe?

Some previous discussion in T5089.

Review as soon as possible

Nevermind. phd.pid-directory does the trick. Should've checked the configuration first.

This sounds like it's the same issue as T1191.

Just to follow up with some additional info:

Possibly related to T5573?

qqq context documentation is helpful, but not really needed [...]

rPbee1e09fd13086dab42f11cb54d489e7e7d5a0aa

rPbee1e09fd13086dab42f11cb54d489e7e7d5a0aa

In T4036#27, @btrahan wrote:

Closed by commit rPc75495e63fa0.

Closed by commit rPc75495e63fa0.

Transactions application sounds good to me. I doubt we'll ever have a mentions app, although who knows.

Kind of a silly question but where should MentionableInterface live? I was thinking about making a new application mentions, except there's nothing in there except the interface folder.

Closed by commit rPc180832f8441.

We haven't seen other requests for this, and you can just copy/paste -- which isn't the most elegant, but should work fine.

On OSX, this protocol is blocked by the browser in Safari, Chrome and Firefox in an almost-silent way. At least in Chrome, this is explicitly a security/policy issue. We have far more OSX users than desktop Linux users, and I don't want to include file:// in the default set because it looks easy but will fail non-obviously for most users.

Obviously its configurable. The message on the config page said to let you know if there was a protocol that should be considered for inclusion by default.

This is configurable, and file:// is an unusual protocol to use as an editor.

◀ Merged tasks: T6045.

Ah actually you're right; the configurations are different between hosts in the local config because different tiers have different configurations.

Do you intentionally have different configuration on host1 and host2?

Also, none of these HA tasks are "this is breaking some production or real-world system"; it's just me documenting what does and doesn't work so there's a clear picture on outstanding work for HA to be usable in production systems (or for Phacility SaSS).

(I can give you explicit instructions on setting up a setup like this, and provide you the configuration files, if you want to get a similar setup going)

Yeah I figured that "high availability" was probably not going to be a huge amount of information.

Can you give me some more details on the "high availability" setup? Apologies if there's lots of context I should probably have already on that. :/

I think public accessibility implying canCDN is the easiest fix here.

Files now have a "cacheable" flag, which is approximately equivalent to "public" -- internally, canCDN, i.e., can distribute over a content distribution network.

Adding the index to the build log table seems to have resolved the performance issues with viewing build logs, so I'm moving this down in priority.

I'm going to repurpose this for fixing the hang, we definitely shouldn't stall the queue over mail issues.

This was caused by Docker killing off the SETGID bit on postqueue / postdrop executables. See https://gist.github.com/porjo/35ea98cb64553c0c718a.

Thanks! That should fix it at HEAD.

From IRC:

Closed by commit rP6be8d65763ee.

This is the backtrace on an actual child PID:

Backtrace from daemons:

Closed by commit rPf015cb50fe6a.

✘ Merged into T5196.

But does beg the question why phd.user is described as 'System user to run daemons as' if you have to run them yourself?

Can you verify that D10383 fixes the issue?

Oh, that is not supposed to be creating new logs for each entry. It's supposed to add them to the existing log.