Is the import complete?

In T10341#158952, @chad wrote:

Is this Subversion?

This may make more sense via whatever comes of T10329.

One use case I'd like for you to consider is that the build logic might want to insert data into the commit log or differential revision. For example we may want to add reviewers, subscribers, Jira tickets (from the branch name), etc. While some of this case is handled by Herald, not all of it can be without re implementing existing logic in custom PHP

It must inconsistent:

• doc said "at least 8mb to support large file"
• truth is "bigger then 4mb will work"

For now, I'm just going to do this:

I think this should all work properly and consistently now, let me know if anyone finds a way to break it.

I believe this is now fixed at HEAD of master. It should promote to stable tomorrow morning.

Is this Subversion?

Unfortunately we can't fix bugs we can't see (well, usually). If you have further details (like what type of repository) or errors in your Apache log, please post them.

Hi @chad , I added some info. I don't know the real reason honestly.

Please see Contributing Bug Reports. Specifically we can't take a bug report without you providing the reproduction steps. How can we reproduce this error?

Digging into https://phabricator.wikimedia.org/T76913, I think the actual request there was ultimately not per-board stickiness or per-user stickiness ("the menu remembers the last thing you set it to, and remains set to that if you close and reopen the window"), but an option to save particular filters into the filter menu ("Save a particular filter as 'No Patches Yet' and add it as an option to the filter menu for all users").

I have solved the problem. A unit test was outputting a status that was not understood by my XojoUnitTestEngine class. It therefore was not setting the Result of a single unit test. I changed my XojoUnitTestEngine to read:

I just wanted to mention that I have the exact same error message, but I also can't reproduce it and I also don't see any negative effects at the moment. Still I will have an eye on it and try to find a pattern for this :)

Awesome, thanks for testing! I think this should be an easy fix, now.

I think that may be important:

+1

To prevent confusion with Git/Hg/Svn tags: What about "Label"?

Thank you Chad

Confirm. After deleting of mentioned line on top of stable everything clones fine.

See Contributing Feature Requests for how to request features in Phabricator. Specifically we need to know just the problem your facing using the software, not just what you want.

I just tested it and it seems like removing the line solves the problem.

(2) isn't a solution I'd enjoy, as the feature really helps to gain in productivity. Not to have this means revisit each closed task to assign it.

I'm fine removing it then seeing how loud (if any) complaints are.

Not directly -- I'm just digging through the Phabricator board on WMF to try to catch issues before they happen, since they have a Big Update happening soon.

Did this pop up again recently?

That seems reasonable, I filed T10339 to follow up.

A use case: "I want to see how well we're sizing points, show me all 4 point tasks"

I'm just going to co-opt this as a subtask for that piece since you already tagged it so nicely.

IMPORTANT: This is not a demo or test install. Please don't make a mess. You can launch a demo install on Phacility if you want to poke around and try things out.

These now exist. Enable them with maniphest.points.

We could do the whole-column thing, but I worry it would be confusing / not useful.

Admittedly I didn't fully grok your description, just how I pictured it in my head. What I was thinking was grouping a whole column by say a Person (like we did in Dashboards) you can see their points and drag work between them. If we go with grouped headers inside the column... how would that work for people? You'd just have their points for that column in the header?

Oh. I assumed the entire column was a group.

Here's the feature I'm thinking about:

Yeah I'm not sure how they'd appear twice in the same column, just multiple times on the board ("Easy", "Bug Report")

Oh, wait. Maybe we're talking about different things. Let me draw a picture.

Absolutely not ever implementing that, because it allows a card to appear multiple times in the same column and requires me to rewrite all the workboard code again.

Another possible Group By is by project. So going into Differential and grouping by projects should allow me to see all Bug Reports in their own column.

(This is adjacent to T4245 and should be happening fairly soon -- next big-ticket item I'm currently planning to hit after subprojects/workboards calm down.)

Oh, and make sure you restart fully after changing the code -- I suspect that might have been the cause of the revert not fixing things earlier. Here's a guide if you aren't sure how:

right, I wasn't sure if it was a special case of either of those, but I figured I'd ask just in case.

Can anyone who is able to reproduce this let me know if this fixes it?

This will be supported by diffusion.search out of T5873. See also T10329.