Change Details

See PHI570, which describes various Drydock issues. See PHI873, which opens a discussion around broader authentication and signatures. See PHI841, which includes a request for richer `transaction.search` results for audits. See PHI916. When resolving futures during builds, we should close connections if we believe we're going to be sitting there for a while. See PHI933, which requests "Author" for build plans and an "Author" object policy. But a more clever approach is a "Current Viewer" policy which automatically turns into a concrete policy when saved. See PHI944, where an unusually shaped change is requiring a very large amount of memory to parse. --- //Resolved-ish// See PHI806. This is a sensitive request with moderate urgency. See PHI937, which identifies an issue with `packages(project)`.

See PHI873, which opens a discussion around broader authentication and signatures. See PHI841, which includes a request for richer `transaction.search` results for audits. See PHI944, where an unusually shaped change is requiring a very large amount of memory to parse. See PHI936. We could smooth out some language on the Workboards "Point Limit" field when `maniphest.points` is not configured. **Harbormaster** See PHI929, which requests that we actually use `arc.staging` in describing staging ref locations. Perhaps, see also T10093. See PHI927, which would like Harbormaster to have access to the `arc:onto` target branch. See PHI933, which requests "Author" for build plans and an "Author" object policy. But a more clever approach is a "Current Viewer" policy which automatically turns into a concrete policy when saved. See PHI916. When resolving futures during builds, we should close connections if we believe we're going to be sitting there for a while. **Drydock** See PHI570, which identifies some possible fundamental logic issues in Drydock. See PHI885, which requests timeouts on `git fetch` during working copy construction. See PHI857, which wants support for serial queues in repository operations. See PHI755, which could use verification around WorkingCopy blueprint selection. **Repositories** See PHI943 and PHI889. One primitive we should clearly build in the short term is an intracluster sync log, since it would likely have helped with about 5 different issues by now. See PHI943. We should verify the modern behavior of `PhabricatorGlobalLock` in the presence of `KILL <id>` on the `GET_LOCK()` connection. I believe it is clear and explicit after D19702, which made the `catch (...)` more narrowly scoped. See PHI930, which is approximately T10964. --- //Resolved-ish// See PHI806. This is a sensitive request with moderate urgency. See PHI937, which identifies an issue with `packages(project)`.

See PHI570, which describes various Drydock issues. See PHI873, which opens a discussion around broader authentication and signatures. See PHI841, which includes a request for richer `transaction.search` results for audits. See PHI916.44, where an unusually shaped change is requiring a very large amount of memory to parse. See PHI936. We could smooth out some language on the Workboards "Point Limit" field when `maniphest.points` is not configured. **Harbormaster** See PHI929, which requests that we actually use `arc.staging` in describing staging ref locations. Perhaps, When resolving futures during buildssee also T10093. See PHI927, we shwhich would close connections if we believe we're goinglike Harbormaster to have access to be sitting there for a whilethe `arc:onto` target branch. See PHI933, which requests "Author" for build plans and an "Author" object policy. But a more clever approach is a "Current Viewer" policy which automatically turns into a concrete policy when saved. See PHI944PHI916. When resolving futures during builds, we should close connections if we believe we're going to be sitting there for a while. **Drydock** See PHI570, which identifies some possible fundamental logic issues in Drydock. See PHI885, which requests timeouts on `git fetch` during working copy construction. See PHI857, which wants support for serial queues in repository operations. See PHI755, which could use verification around WorkingCopy blueprint selection. **Repositories** See PHI943 and PHI889. One primitive we should clearly build in the short term is an intracluster sync log, since it would likely have helped with about 5 different issues by now. See PHI943. We should verify the modern behavior of `PhabricatorGlobalLock` in the presence of `KILL <id>` on the `GET_LOCK()` connection. I believe it is clear and explicit after D19702, which made the `catch (...)` more narrowly scoped. See PHI930, where an unusually shaped change is requiring a very large amount of memory to parsewhich is approximately T10964. --- //Resolved-ish// See PHI806. This is a sensitive request with moderate urgency. See PHI937, which identifies an issue with `packages(project)`.