- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 5 2019
Just a bunch of language nitpicks.
- Clarify help/guidance around "repeat" vs "retry" flags.
- (Agreed on the ">>", I'll see about touching that up a little.)
The execute workflow is always foreground, so execute --id ... --retry is now "foreground retry", and execute --id ... --retry --repeat is "foreground retry, repeating if necessary".
The new classes here are:
Mar 4 2019
Mar 3 2019
Mar 2 2019
Technical stuff:
Some old migrations call PhabricatorSearchWorker::queueDocumentForIndexing(). This no longer works after D20200 because the PHP implementation expects a dateCreated column to exist, but it won't exist until 20190220.daemon_worker.completed.02.sql runs.
Mar 1 2019
Currently, if a 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.
Another possible approach is to use -o LogLevel=ERROR. This gets us into trouble if there are useful INFO messages other than "permanently added X to list of known hosts", but presumably all the important stuff is rasied at ERROR or better.
For Drydock/Harbormaster, the only real way forward I see here is:
Currently, properties on upstream build steps are driven by CustomFields. T13248 briefly discusses a bit of context.
(This is likely to be very long, very rambling, and not particularly enlightening or useful.)
somewhat tricky to explain, and somewhat tricky to resolve
From onsite:
In T5391#234838, @epriestley wrote:
Feb 28 2019
I cherry-picked this into our fork and it fixes the problem. ✅
and now when I re-run the command again, it gets another 7 commits and fails again. So, perhaps by me viewing the commit, I kick off a job that rebuilds something on the backend?
It's now failing on this one (consistently if I keep running it):
Thanks. That looks like a perfectly normal object to me so I'm not sure what could cause it to fail to load.
You will soon be able to give builds different "Hold Drafts" behaviors. See T13258.
mysql> SELECT * FROM phabricator_repository.repository_commit WHERE id = 71471; +-------+--------------+--------------------------------+------------------------------------------+------------+------------+-------------+---------+--------------+--------------------+-----------------------+ | id | repositoryID | phid | commitIdentifier | epoch | authorPHID | auditStatus | summary | importStatus | authorIdentityPHID | committerIdentityPHID | +-------+--------------+--------------------------------+------------------------------------------+------------+------------+-------------+---------+--------------+--------------------+-----------------------+ | 71471 | 41 | PHID-CMIT-ohupojjoniypwpghvlr2 | 43034ccb9eac4ca8a655f655b726f73c5e551413 | 1438182566 | NULL | none | | 1024 | NULL | NULL | +-------+--------------+--------------------------------+------------------------------------------+------------+------------+-------------+---------+--------------+--------------------+-----------------------+ 1 row in set (0.01 sec)
Making a way to set fields to default: disabled would make this feature even better ;)