Sounds good, let us know if you come up with repro steps.

is that chad

This is now available in the Phacility cluster. It appeared to work correctly on a test instance:

It's just a plain text field, not a remarkup box.

got it! Could reproduce the "restricted error":

The spooky emoji and icons are real lackluster, barely a respectable spook in the lot: 👻 💀 ☠ 🍖

D17311 makes this stop fataling, but you're stuck with the panel for now. This should get fixed soon, but I don't want to try to sneak anything more ambitious in before the release cut.

Ah, ok, please feel free to close it till I can figure our reproduction :)

Oh, the way I worded my original comment is confusing. I noticed the missing/unviewable panel on the homepage first then went to investigate and found error.

tyvm 🙏

• I saw the panel
• I went to https://secure.phabricator.com/dashboard/ and clicked on Speck Dashboard (https://secure.phabricator.com/dashboard/view/136/)
• I clicked on Manage Dashboard in the top right https://secure.phabricator.com/dashboard/manage/136/
• The page I'm navigated to is the FATAL ERROR page

Was the sequence of actions like this:

I just got this fatal error when trying to manage my dashboard on this install:
https://secure.phabricator.com/dashboard/manage/136/

I can't reproduce this: removing panels from dashboards works fine for me:

In our setup (as an open source project) we often get differentials created with base commits which do not exist in upstream. As a result using arc patch often fails, even worse, in a non-recoverable way as --reject is passed to git apply. In a patch fails to cleanly apply it is hard to continue the work-flow and manually correct the merge conflicts.

"Bizarro Gremlin" is just an alias for Quicksand

i'm bad at search

I'm going to write up Diviner now, then Upgrading guide

🅾 Ⓜ 💎

🙉

Yeah, 7.1.2 RC1 seems to fix the problems. There are like 2 dozen random "uuhh fix off by one error, revert thing that overflowed something, you bastard, fix this too" commits in that commit log, even some affecting stuff like libgd (which you'd think would have been pretty hardened), so it's really impossible to tell what fixed what without it becoming tedious.

I think we currently don't really try to handle these cases:

That tip probably does not fit on screen in any of the orientations: it obviously won't fit to the north or east. If we try to put it to the south, part of it will be offscreen to the right. If we try to put it to the west, part of it will be off the top of the screen (the rectangle we use to detect the size of the tip box is slightly larger than the actual pixel size of the tip because we get weird scrollbar interactions if we use the size of the tip exactly).

My trick is:

Yeah I couldn't quite grab a screen

Here's what I see:

Chrome:

• Go to Workboard
• Click Fullscreen
• Hover over Fullscreen - tooltip is elsewhere?

Yeah, I don't think I fixed it. I tried this set of steps at master prior to D17308:

I'm not sure if I actually fixed @rphl's issue or not. D17308 was just aimed at the existing issue under the theory that we'll see more of it after this ships if we aren't already seeing it, but his report definitely might be a new issue.

I thought it might be that same issue, but sounded like it was a new issue and not a pre-existing one.

Awesome, thanks for hunting that down.

This should now be resolved at HEAD of master, and should promote to stable later today.

My testing from D17296 indicates this would also resolve the original problem described in T9639

Gotcha... Thanks for the explanation. Initially, I wasn't exactly sure what was going on... I sent an email out telling folks to use "Auditor: ..." in their commit messages, upgraded to clean up what I mentioned here T12181: Bulk Deleting Audits does not remove "Audit Required" from Commit, and then the "Auditor: ..." tag stopped working when our team started using it. Appreciate the fix!

Thanks! I think this is the timeline of events:

Ahhh... Before both "Auditor: ..." and "Auditors: ..." worked. Now it appears that only "Auditors: ..." works. I must not have been trying it with "Auditors: ..." at all.

Per above, it sounds like upgrading fixed what you were seeing?

This isn't a bug report we can accept upstream. See Contributing Bug Reports for help. In particular:

No, not yet... In those examples, I just happened to have Auditors on the first line. Usually, it's not on the first line for us.

Does that explain what you're seeing locally?

This isn't a bug report we can accept upstream. See Contributing Bug Reports for help. In particular:

Those commits are not expected to trigger an audit after D17122 / T10312. The first line of commit messages is now always parsed as a title, even if it begins "Auditors: ...", "Tests: ...", "Reviewers: ...", etc.

Is there a full description or is it a joke? I need to do my case study on tasks that contain errors. I guess that is some empty task that was deleted by the creator immediately.
Will buy case study anyway, no point in looking for phantoms here.

@epriestley can you have a look at this, please?

@epriestley can you have a look at this, please?

I would imagine they're using something along those lines yes. I think we'll probably keep a bunch of people happy if pushing Git refs up were supported.

I'm just curious how people are generating diffs, just command line then cut and paste? I would presume those users would be fine with pushing a branch up for review. Are there other methods we're not considering, like IDEs?

Chances are we're going to get complaints that go either way. Myself, i'd tend to prefer T5000.

You would prefer this over T5000?

We've had some people in KDE kick up some fuss about this.

The best way to get help here is to provide us with all information, every step taken, system, phabricator versions, if you could reproduce it on Phacility, etc. Just giving an error message isn't enough for us to give you a lot of guidance

It is a private repository - and I have access to it. I can clone it and push to it. So why would this error be thrown. Diffusion shows the number of commits correctly and the name of the recent commit as well but when I click on the repo it outputs the above error.

In T12196#210013, @epriestley wrote:

PHP7.1 segfaults about a dozen times a day for me, every day, with little apparent rhyme or reason to the segfaults.

I can only assume I am being punished for not rushing it into production as soon as possible. Perhaps we can deploy PHP 7.2 to production directly from master without waiting for an actual release.

PHP7.1 segfaults about a dozen times a day for me, every day, with little apparent rhyme or reason to the segfaults.