Details
-
Bug
-
Resolution: Fixed
-
Medium
-
7.13.5
-
7.13
-
9
-
Severity 3 - Minor
-
7
-
Description
Issue Summary
Some repositories are showing as still syncing in the GUI even though they have already finished.
Steps to Reproduce
- setup GHE in DVCS accounts
- set interval syncs for a very large repository
Expected Results
When the sync is complete, it should show reflect this in the GUI
Actual Results
GUI shows the repo as still syncing
Running the Repository get API:
GET /rest/bitbucket/1.0/repository/<idofrepo>
shows the following:
{ "id": xx, "organizationId":xx, "dvcsType": "githube", "slug": "repo", "name": "repo", "lastCommitDate": 1568725405000, "linked": true, "deleted": false, "smartcommitsEnabled": true, "lastActivityDate": 1568725405000, "repositoryUrl": "https://<URL>", "fork": true, "sync": { "finished": true, "changesetCount": 0, "jiraCount": 0, "pullRequestActivityCount": 0, "synchroErrorCount": 0, "startTime": 1568727290791, "finishTime": 1568727292656, "flightTimeMs": 0, "numRequests": 0, "softsync": true, "webHookSync": true, "warning": false, "hasAdminPermission": true } }
(Optional - If Necessary)
Workaround
Schedule a restart of JIRA
Attachments
Issue Links
- relates to
-
JSWSERVER-20250 DVCS sync runs indefinitely when an admin change was made in GitHub mid sync
- Gathering Impact
-
PSR-353 Loading...
- Mentioned in
(3 mentioned in)