See also:

Sorry, we do not support third-party application development. See T5447 for discussion.

Comcastic!

(If you immediately get another error, there's some more serious problem with state tracking. This usually means you imported/exported awkwardly or mucked with the data somehow, and recovery depends on exactly what state you're in and how you got there.)

(If you immediately get another error, there's some more serious problem with state tracking. This usually means you imported/exported awkwardly or mucked with the data somehow, and recovery depends on exactly what state you're in and how you got there.)

Delete all the text in 20150609.spaces.1.pholio.sql (but not the file itself), then run bin/storage upgrade again.

Ah, thanks! I think we're probably in fairly good shape once everything is properly documented so I'll plan to close this out and we can look at placeholder results in the future if there's a compelling need for it from somewhere else.

I'll add one thing to Evan's comments there, which is that it would be useful to be able to create a test before the results are available. That way reviewers can see that such and such tests are still running and their results are pending.

See T4213 for "we change CSS all the time and your stuff will break every few months if you mess with it".

We have roughly 10 of these in our queue.

Can you give me a better idea of what these huge, extremely similar projects are? I can't come up with any guesses from my experience, and the categories don't precisely sound like operations or software engineering. I've never heard the term "Fitout" before and Google is only giving me hits in the context of interior design.

I pushed this host, should be all set now?

Broadly, we're much more able to solve problems if you describing the problem you're facing rather than just the solution you're interested in:

There's some prior discussion of something similar in T7190. Is your use case a lot like that, or a lot different, or somewhere in between?

Put another way, there is no scenario where running bin/remove destroy is desirable:

It is difficult to concisely communicate what bin/remove destroy does.

Whoops, that's half a draft. Ignore that, I'll write a proper version...

This stuff is now in HEAD, and HEAD no longer loads (or even contains) HeraldCustomAction.

I've deployed this to this server, let me know if anyone catches anything suspicious with Herald.

See also T7819.

Should I be using Phame?

For the original issue: when a change is blocked, we do not send email about it. There is no way to be alerted to blocked pushes right now, and I generally don't think this is useful enough to include in the upstream. This interaction could possibly be more clear, but feels like something we just stick in the documentation to me.

Just to follow up on this, the transcript will show this at HEAD once T8726 lands:

This has been in the update notes for a while, but just for completeness: T8726 is changing this substantially. After those change land, you must extend HeraldAction instead of HeraldCustomAction. The API is similar, but doesn't directly map to the old class.

This should wait for T8726 since the API for actions is completely changed in unlanded work.

See some discussion in D13777.

Sorry, I made a mistake and didn't update my local copy properly before trying to reproduce this. This is an error on our side.

I can't reproduce this. When I follow these steps, the workflow completes successfully.

I can't reproduce this (resetting my own password works fine), and this report doesn't include enough information to allow us to help you.

Currently nowhere. However I've created custom code

This might be sort of a copy of T7617.

I can't reproduce this issue. For example, here's an index of this task:

In T9028#129241, @epriestley wrote:

Have a daemon that processes deleted commits/branches and deletes associated (incomplete?) audits

I think we probably don't want to do this. If someone accidentally deletes master and no one realizes for a little while, it would be bad to potentially destroy years worth of history, state and discussion contained in audits. Even just auto-closing them (without actually removing any comments/discussion) seems a bit bad.

Looks like this is in good shape now.

Ah, perfect. Yeah, either contact@ or support@ will work fine. Thanks!

Cool, I'll get this importing. Do you want to shoot us an email at support@phacility.com to coordinate the rest of the import? There might be some private questions later on in the process about data specifics in case we run into any issues.

When they occasionally break people complain, so I think some users find them useful.

They're supposed to show open tasks.

Improve the error message and provide a button to close the audit

I do this routinely (roughly every day) without encountering this problem, so I'm surprised by this behavior.

Specifically: empty commits and commits which strictly undo some of the work on a branch (e.g., revert HEAD, or revert HEAD + the prior commit, etc) produce a new commit with the same tree hash as an older commit.

See also T4411, although I expect to get to this before that.

"Mark All Read" should remove them, but only if you have another newer notification than any of the phantom notifications.

It's not difficult to implement.