Meow Meow

Use cases we've seen FWIW:

Yeah it does, and I just didn't recall ever seeing this behavior and assumed "stack trace" meant "error".

Oh also apparently query profiling doesn't always come up when you click on it, here is an example error

(C02TW3N0HTDD is the very useful totally human interpretable name of my laptop)

Isn't the end of the public key way more useful for human readability in general? Most of my keys generated via ssh-keygen (which I assume is the practically universal method?) end in an identifier that I can plausibly use to identify the key, like this one:

@jcox do you know how to reproduce arc diff dying when you try to create certain types of diffs that move or remove symlinks? I think that's adjacent, if not identical to what's being talked about here.

Doesn't "lines" make more sense as the unit you measure the import rate at, or no?

i used gem install so that i could remain ignorant of those types of problems

it has an -s option

There is a program far superior to cat that already exists.

Or apparently just doing this anywhere

Using Chrome

🐶 🐶 🐶

Here I was thinking I found a helpful public bug.

Hm, actually the problem here is that the notification bubble doesn't show up for any file uploads on our current version. I suppose it could actually be "on our current version + extensions". I'll get a reproduction matrix together tomorrow.

We don't have a notifications server, does that make it like that?

Ok I actually get a dialog on secure., it's probably because we're out of date with the upstream.

I think it's a worthwhile adventure to find out.

If you put a * in the ->withName pattern you should also be able to combine with suffix, i think?

thank you

Yeah I just wanted to buy myself a badge.

No nothing like that but FWIW, it just worked when I tried to reproduce it again.

Yeah.

Just tried again.

I have many other excellent ideas for the Phacility online swag store, these are my favorite:

Yeah I clicked "Delete File" and can't see it anywhere now.

Edited to not give out my credit card number on the internet.

FWIW, this is the thing that I point someone at when I want to show them how to contribute changes to Phabricator, like just go through the workflow.

This might break our stuff, test async diff before deploying upstream updates.

At worst we can just add another API method to our install, like, maniphest.reallysearchtitle

I think we are doing this all downstream.

I assume everyone is fully aware of the caveats and just being lazy and not wanting to store the identifier they get back when they create the task? I will inquire further.

Is Phabricator not a suitable replacement for a Jiffy Lube inventory terminal?

Because people are filing tasks from external systems in some systematic way (consistent titles) not saving the ID, and then wanting to reference the task later.

This seems like a good plan to me, we're just checking in that this isn't totally outside the realm of possibility while we plan some super secret changes to our instance.

use array() instead of inheriting validation errors

remove class from conduit fields

This seems to work afaik. Still need to do custom fields and try this in conjunction.

• Fix display of quoted transaction values
• Remove unneeded empty checks for create transactions
• Remove getRequiredHandlePHIDs and transactionHasEffect methods
• Use generateOldValue instead of getOldValue when applying external effects

I still have stylistic stuff to do throughout, I just focused on faithfully moving functionality out of the editor/transaction into the modular transactions here. There are a few things that don't work, haven't even looked at custom fields yet.

finishing the gruntwork

(not building locally anymore, eg, any time I want to do anything with a built binary at all, i'm actually doing it with a binary on a remote server because I can get the build results faster)

Well one facet of this is that remote servers tend to be significantly more powerful than developer machines, and so since I've implemented this downstream, I have basically taken to not building locally anymore.

Don't yet presume that users will be lease owners