Do you have a CSS only solution? position: fixed would only lock one axis.

cool, looks like that fixes it. thanks!

Specifically this feature was added in August. D13925

I think that'll fix it, let us know if you're still seeing issues? Thanks for the report!

This is from D14622, probably just a missed grep (likely because the method name is spelled QuickSand instead of Quicksand at this callsite).

Broadly, we're in no rush to get rid of these events -- definitely no need to panic. I just wanted to push things in the right direction after T9851 was filed, which originally asked for the scope of these events to be substantially expanded.

My recollection, at least, is that Herald wasn't originally suitable because of T6367. Prior to that task, an "attacker" could write a rule like this:

Is your install up to date?

See prior discussion in T5021 / D9270.

Thanks Chad, however, for some reason I do not see that select menu.
Might this be a permission issue? I am a Phabricator administrator.

/me patiently awaits @20after4's response, after being directed to this ticket from Wikimedia's Phabricator instance

What are you doing which can't be covered by Herald?

→ →

You're right, there is, I totally missed it.

There is a comment bubble next to the line number, no?

In T9870#146277, @vhbit wrote:

BTW, what are requirements for linter to be upstreamed so I can keep them in mind?

Further example:

In general, Projects in Phabricator are the best way to group any concept, and search by project is provided in (nearly) all applications.

In T9724#146283, @epriestley wrote:

I can't reproduce this. Here's what I did:

• I opened three terminal windows.
• I ran git clone ssh://dweller@secure.phabricator.com/diffusion/P/phabricator.git phabricator-X in each at the same time, where X is one of 1, 2 or 3.

All clones completed successfully, and I got three clones in the working directory after they finished.

Is the best workaround I can think of, but this means setting up Herald Rules for each hashtag.

You can look at PhabricatorCommitSearchEngine to add additional fields to the Audit Search. You'll need to add corresponding methods to DiffusionCommitQuery.

There isn't any workaround I can think of, which I included in "no built in way to achieve". You can:

what will be the workaround for this ? may be creating task say T1234 and write herlad rule to attach commits to that task ? However I didnt see any option using Herlad to attach commit to Task.

I can't reproduce this. Here's what I did:

Any news on this?

Your Github repository is a nice reference. I will do the same for T9797

clang-format-linter author here. I somehow missed the Community Resources page and yep ATM it's definitely a better place for this linter (alongside with one for Swift code).

In T9848#146061, @joshuaspence wrote:

In T9848#145894, @OCram wrote:

Hmm strange, I do not use any md5 function. I simply copied the ArcanistTextLinter and changed it to work with files containing \r\n line ends. Thats the reason why I do not know where the md5 function all or the variables come from ^^

Based on my understanding of what your linter does, it sounds like T5105 is what you want.

Just going to assume you want crumbs.

What element is on desktop that isn't on mobile?

duhh yes .. sorry!

That's expected if you've written an "every time" rule.

btw, it seems the extension comments every time there is an update to the diff instead of just the first time. That is a bit annoying: was this expected? is there a quick fix to it?

I changed my configuration to be able to see the message again, so here is the screen shot:

This usually happens when rebasing an upstream repository after a significant amount of time (like six months). When this happens, there'll be hundreds of builds all running at the same time, which can result in hundreds of working copies for the same repository.

so I end up with lots of copies of the same thing

Which instructions were you looking at which you found confusing? Can you point me at the document? (Or was it the setup warning itself?)

Because I have a lot of repositories, and there are multiple copies of each repository (because things are running in parallel), I will run out of disk space if I have multiple full copies of every repository in Phabricator kept on the build hosts for all time.