This is effectively mooted by changes in T13277.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 15 2019
No idea how to reproduce this.
I think this task has exhausted its usefulness.
This remains desirable, but probably won't happen without a stronger motivator since the patches are somewhat involved.
Changes connected to T13277 likely moot this. If users are pushing temporary personal branches to a repository, configure "Permanent Refs" to exclude them. Commits pushed to these branches will no longer publish feed stories, trigger audits, etc.
I'm going to WONTFIX this since T13277 has generally taken us in the other direction. "Publish" now controls everything (audit, feed, email/notifications, Herald, closing tasks and revisions).
No outstanding customer requests for this.
There's no specific performance/scale issue here, so waiting until one arises or this pops up on a profile.
Apr 14 2019
Okay. I'm not crazy, I'm just really bad at reading.
Examining "master" (branch) at "02f94cd7d2885de502d03934af3a0c24453e8e58" (autoclose: Y). Skipping, HEAD is known. Examining "stable" (branch) at "d3df0a49f92a8be2f5b8a030af2f8fa5471cc45d" (autoclose: Y). Skipping, HEAD is known. Examining "refs/pull/846/merge" (ref) at "d816dc011f935fdda9468c905e4af4c7fc73b322" (autoclose: N). Skipping, HEAD is known. Examining "refs/pull/839/head" (ref) at "d3df0a49f92a8be2f5b8a030af2f8fa5471cc45d" (autoclose: N). Skipping, HEAD is known. Examining "refs/pull/846/head" (ref) at "1263f335abfc5bcf7b5e2c60ae0632b4660815d8" (autoclose: N). Skipping, HEAD is known. < ... > < ... many many non-branch refs properly identified as non-autoclosing ... > < ... > Examining "refs/pull/4/head" (ref) at "e282a7707da11e3e2bca2b3a41925aeefd4f22c9" (autoclose: N). Skipping, HEAD is known.
Only branches can be "Autoclose".
Apr 8 2019
This issue is still relevant and reproducible in the current release.
Here are the steps to reproduce it:
Apr 6 2019
Mar 26 2019
Presumably obsolete since this hasn't cropped up again.
Mar 25 2019
Mar 19 2019
I believe this is now resolved. See D20291 for technical details on the main issue and T13266 for a followup.
Mar 18 2019
I also checked for more leftovers in instances/, but it looks like we don't have any non-default paging there.
I've poked around a fair bit locally, although I'm not totally confident I got every combination of paging columns and queries. I think anything that was missed is very likely to produce an explicit error rather than mysterious behavior, so I'm not too worried about it. Stuff to keep an eye on:
Mar 7 2019
An adjacent issue is that the current behavior of overheated queries is to return a partial result set and set a flag. The goal of this behavior is to let us show some results if we find some results, but it may be surprising if the caller doesn't handle overheated queries, since they may look like a queries which simply failed to match anything.
The hypothetical steps above do, in fact, reproduce this:
Mar 1 2019
somewhat tricky to explain, and somewhat tricky to resolve
From onsite:
Feb 28 2019
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.
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)
Here's what's happening in general: