-
Bug
-
Resolution: Fixed
-
High
-
2
-
Severity 1 - Critical
-
NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding bug report.
When synchronizing GitHub, the DVCS Accounts show "Sync Failed: Error during sync. See server logs":
In the server log, there is:
2014-10-13 09:31:33.264521500 2014-10-13 09:31:33,263 DVCSConnector.MessageExecutor:thread-1 ERROR ServiceRunner [dvcs.service.message.MessageConsumer] Synchronization failed: null 2014-10-13 09:31:33.264523500 java.lang.NullPointerException 2014-10-13 09:31:33.264523500 at java.util.AbstractCollection.addAll(AbstractCollection.java:303) 2014-10-13 09:31:33.264524500 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestPageMessageConsumer.onReceive(GitHubPullRequestPageMessageConsumer.java:109) 2014-10-13 09:31:33.264524500 at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestPageMessageConsumer.onReceive(GitHubPullRequestPageMessageConsumer.java:29) 2014-10-13 09:31:33.264534500 at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.doRun(MessageExecutor.java:361) 2014-10-13 09:31:33.264535500 at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$ReleaseTokenAndEnqueueNextMessage.run(MessageExecutor.java:267) 2014-10-13 09:31:33.264535500 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 2014-10-13 09:31:33.264537500 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 2014-10-13 09:31:33.264537500 at java.lang.Thread.run(Thread.java:662)
UPDATE this is a bug in synchronization of GitHub/GitHub Enterprise pull requests during a full synchronization and when there are more than 30 pull requests in a repository. Commits and branches are not affected.
Impact Only the oldest (by creation time) 30 pull requests in the affected repository will be synchronized. Any pull requests newer than the oldest 30 that are not updated after the time that the full sync (or first adding the GitHub account into JIRA) will not be synchronized. Any pull requests that have been changed since the full sync, regardless of whether they are among of the oldest 30, will be synchronized during a subsequent soft sync.
Workaround start a soft sync (just clicking on the sync icon). This would synchronize changes in the pull requests.
- is caused by
-
-
- Closed
-
- is related to
-
-
- Closed
-
