This task was filed via the "New Bug Report" form.
Wed, Mar 13
This is an unconstructive mess that I don't specifically plan to act on. T13069 and other work may eventually resolve this case indirectly.
Tue, Mar 12
Currently, expected behavior.
Mon, Mar 11
Fri, Mar 1
Currently, if an card requires MFA to edit, we're unable to prompt the user. We likely should be able to do a prompt inline. This should also probably have a warning icon on the card itself.
Feb 20 2019
D20196 removes this code.
Feb 15 2019
Feb 12 2019
Feb 7 2019
Jan 16 2019
Jan 15 2019
(I'm not 100% sure that D19972 fixes this completely, but it appeared to locally. In the future, "Mail Stamps" should include this information in a more reliable format, although they do not currently include transaction information. See T13069.)
Jan 14 2019
Jan 2 2019
Dec 18 2018
Dec 12 2018
Presuming something fixed this.
Dec 9 2018
I'm having some trouble getting this new behaviour (which IIUC basically means that multiple hosts in a Drydock pool should be load-balanced across). In "active resources" I see three Drydock hosts, which all belong to the same Almanac service. In "active leases", however, I see only a single host lease and many working copy leases.
Nov 26 2018
Nov 9 2018
I would like to add another use case where this would be beneficial.
Nov 1 2018
Oct 27 2018
Oct 25 2018
D19762 adds a "supplemental allocation" behavior, which basically lets blueprints say "I want to grow the pool instead of allowing this otherwise valid lease acquisition".
After that, both hosts will have resources and jobs will allocate randomly, which should be good enough.
I believe you can work around this today by disabling the binding to host "A" in Almanac, running one job (which will be forced to allocate on host "B"), then re-enabling the binding. After that, both hosts will have resources and jobs will allocate randomly, which should be good enough. This is exceptionally cumbersome and ridiculous, of course (and it's possible that it doesn't even work).
Oct 23 2018
Well, this sucks... But thank you for taking the time to explain the situation 😃
It's "open" in the sense of Apache-licensed and (mostly) developed in public (e.g., the information on this install is public rather than hidden behind a corporate veil).
@epriestley Does this mean that phabricator isn't open to contributions?
Support for PHPUnit 5.x ended on February 2, 2018.
We need this patch for PHPUnit 6/7 ... any idea when it can be landed on master?
Oct 5 2018
Oct 2 2018
This was almost certainly resolved by D16273.
Changes in T13209 make this the only mode.
Sep 27 2018
This is effectively fixed by T13098, which modularizes test output.
Aug 27 2018
This doesn't have a repro and will probably be fixed via rewrite / modernization in T13077 anyway.