In T5908#145115, @KK wrote:

Hi, when I export data from Phabricator to Excel it doesn't show all data from the the field "Description".
It shows only partial information and than it ends with tree dots.
Can I change that somehow?
Thanks

Why can't your publish step just check if the commit is on master (or even if it's HEAD of master) and no-op if it isn't?

Also FYI the way we are working around this issue now is whenever someone wants to push to a non-master branch, they go into herald and disable the herald rule, push to their branch, then turn the rule back on again. When they want to push to master, they amend the commit to update the timestamps (which changes the hash), and then they push to master (which imports as a different commit).

Neither of those tools let me use my own hardware, which is necessary for my use case. In actuality, GitHub has nothing to do with it, it just happens to be the authoritative repository instead of Phabricator. I still have the same problem regardless of whether or not I make Phabricator the authoritative repository.

I'm assuming that @terrismotox is just playing around.

There was a minor config issue with db005 but I sorted that out; no users were affected.

The 005 nodes are in production. I'm not going to bother with web002 for now but I'll probably do the other half of that the next time I do ops stuff.

This message no longer exists at HEAD. Upgrade Phabricator.

I don't think I use PHABRICATOR_ENV since my config option is set to null:
phabricator.env = null

Awesome, thanks for the report!

Just tested this on rHGTEST, it's working. Thanks for grabbing this so quick.

I've brought up the 005 nodes. I also brought up web002 while I was in there, although we don't appear to be near capacity on web001 yet.

That's the patch from earlier, yell if you spot any issues with it.

Deeply tragic.

Excellent, thanks for following up! I am glad it wasn't just some strange issue for just us.

@mbishopim3, yeah, looks like you're lucky winner #2 on this. Your workaround (creating the database) was correct.

I'm going to repurpose this as "get that data in the database so we're better prepared if this happens again", but feel free to follow up if you go on a hunting expedition or hit the issue in the meantime.

My specific plan here is:

If we do this, one has to be designated "primary" (like Projects) so we can get a consistent default /u/xyz when rendering. This broadly seems like a lot of work for not a lot of payoff, to me, at least today.

It sounds like this use case (using Harbormaster to build a GitHub project, and not using Differential) is far afield from the use cases I consider core. There are a large number of existing tools (Travis, CircleCI) which are purpose-built to address this use case.

@joshuaspence what do you think about this issue?

@avivey: Moving to a scalable SVG is probably a better long-term solution than the multiple sizes of apple-touch-icon Phabricator already has to support!

That worked for now -- hacky, but thanks.

Hi, when I export data from Phabricator to Excel it doesn't show all data from the the field "Description".
It shows only partial information and than it ends with tree dots.
Can I change that somehow?
Thanks

You can manually update phabricator_user.user_externalaccount to change the external account ID reference.

The workaround I provided in the task description ("If you click the "refresh" icon next to the Google provider, you can add a second account.") no longer works after D14319.

You should definitely follow up on the other task with your use cases. Ideally we want to group many similar feature requests so we can architect a single system to cover all or most needs. As that task is still being planned, it's better to comment on it now so those needs can be factored in.

Thank you @epriestley. This is very helpful.

We don't advertise our site except to people who are in the field, but we do still get spammers; probably about 1-2 attempted registrations per month on average. So far I think we've managed to catch them all in the approval process, usually by vetting the e-mail address.

I mentioned anticipated because you mentioned catching spammers with such a tool. Is this actively happening? We're probably the largest (by user reg) open install, and haven't had any spam concerns. If it's a problem, then that should be a different ticket.

Not sure why you think the above describes an anticipated problem. To be clear, this is an actual problem that we have today (and have had pretty much since Day 1 when we adopted Phabricator, but we hoped the addition of the Spaces module would help solve it).

It chooses an A for your default icon because pinned tabs are per domain, not per subdomain.

why can't they use a favicon like everybody else?

User Guide: Prototype Applications

For what it's worth, we have a very similar setup (40ish repositories in Phabricator, all hosted in Gitlab). We have not observed any performance issues such as those described in this ticket.