Closed Bug 1440362 Opened 8 years ago Closed 8 years ago

Phabricator Revisions aren't being synced with bugs in some cases

Categories

(Conduit :: Phabricator, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: imadueme, Assigned: dkl)

Details

(Keywords: conduit-triaged)

Examples, look at the revision creation time and the time it becomes public (either manually or by phab-bot). https://phabricator.services.mozilla.com/D614 - never synced https://phabricator.services.mozilla.com/D615 - never synced https://phabricator.services.mozilla.com/D618 - never synced https://phabricator.services.mozilla.com/D619 - never synced https://phabricator.services.mozilla.com/D620 - successfully synced immediately https://phabricator.services.mozilla.com/D621 - successfully synced immediately https://phabricator.services.mozilla.com/D622 - successfully synced immediately https://phabricator.services.mozilla.com/D633 - successfully synced immediately https://phabricator.services.mozilla.com/D634 - never synced
Actually https://phabricator.services.mozilla.com/D634 was synced later after I made it public (see the attachment on https://bugzilla.mozilla.org/show_bug.cgi?id=1437154) (this was an emergency fix so I didn't wait long just 1 minute).
And it should be noted that all the never synced revisions except (D635) did later get attachments created, but very late as you can see from the time stamps.
Keywords: conduit-triaged
Priority: -- → P1
I haven't had this bug in a while, has anything changed?
(In reply to Israel Madueme [:imadueme] from comment #4) > I haven't had this bug in a while, has anything changed? Yeah, nothing substantial has changed code wise. I was going to ping you and see if you have seen any more issues so it seems it has cleared up on its own. In my investigation, I was never able to pin down any reason for the problem either in logs or looking at phab-bot permissions. For some reason when phab-bot on BMO was looking for the latest transactions, your changes would not show up in the results from the API. But if I did the same query using the conduit API via the web UI as the phab-bot user, they would show up properly. Anyway, please let me know if you see anything else like this in the future. dkl
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.