com.atlassian.jira.plugins.dvcs.exception.SourceControlException: could not get result

Atlassian JIRA | Ashton Treadway | 4 years ago
  1. 0

    We are suddenly seeing a number of these errors cropping up: {code}2013-02-13 01:43:07,453 BitbucketConnectorExecutorServiceThread:thread-1 WARN ServiceRunner com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler:job [dvcs.servi ce.remote.ChangesetIterator] Error obtaining detailed changeset for https://github.ngmoco.com/Mobage/WebGame-defunct-test-repo, node=ef6ed8f1544a059f2488fd1ea8f95377a 8d6728b com.atlassian.jira.plugins.dvcs.exception.SourceControlException: could not get result at com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.getDetailChangeset(GithubCommunicator.java:172) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator$1.call(BranchedChangesetIterator.java:151) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator$1.call(BranchedChangesetIterator.java:147) at com.atlassian.jira.plugins.dvcs.util.Retryer.retry(Retryer.java:48) at com.atlassian.jira.plugins.dvcs.util.Retryer.retry(Retryer.java:18) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator.getDetailedChangeset(BranchedChangesetIterator.java:146) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator.next(BranchedChangesetIterator.java:118) at com.atlassian.jira.plugins.dvcs.service.remote.BranchedChangesetIterator.next(BranchedChangesetIterator.java:66) at com.atlassian.jira.plugins.dvcs.service.remote.BranchedChangesetIterator.next(BranchedChangesetIterator.java:23) at com.atlassian.jira.plugins.dvcs.sync.impl.DefaultSynchronisationOperation.synchronise(DefaultSynchronisationOperation.java:64) at com.atlassian.jira.plugins.dvcs.sync.impl.DefaultSynchronizer$1.run(DefaultSynchronizer.java:79) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.eclipse.egit.github.core.client.RequestException: Server Error (500) at org.eclipse.egit.github.core.client.GitHubClient.createException(GitHubClient.java:516) at org.eclipse.egit.github.core.client.GitHubClient.get(GitHubClient.java:662) at org.eclipse.egit.github.core.service.CommitService.getCommit(CommitService.java:179) at com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.getDetailChangeset(GithubCommunicator.java:168) ... 16 more{code} We haven't changed anything on the GHE or JIRA side, and things have been running smoothly.

    Atlassian JIRA | 4 years ago | Ashton Treadway
    com.atlassian.jira.plugins.dvcs.exception.SourceControlException: could not get result
  2. 0

    We are suddenly seeing a number of these errors cropping up: {code}2013-02-13 01:43:07,453 BitbucketConnectorExecutorServiceThread:thread-1 WARN ServiceRunner com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler:job [dvcs.servi ce.remote.ChangesetIterator] Error obtaining detailed changeset for https://github.ngmoco.com/Mobage/WebGame-defunct-test-repo, node=ef6ed8f1544a059f2488fd1ea8f95377a 8d6728b com.atlassian.jira.plugins.dvcs.exception.SourceControlException: could not get result at com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.getDetailChangeset(GithubCommunicator.java:172) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator$1.call(BranchedChangesetIterator.java:151) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator$1.call(BranchedChangesetIterator.java:147) at com.atlassian.jira.plugins.dvcs.util.Retryer.retry(Retryer.java:48) at com.atlassian.jira.plugins.dvcs.util.Retryer.retry(Retryer.java:18) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator.getDetailedChangeset(BranchedChangesetIterator.java:146) at com.atlassian.jira.plugins.dvcs.service.remote.ChangesetIterator.next(BranchedChangesetIterator.java:118) at com.atlassian.jira.plugins.dvcs.service.remote.BranchedChangesetIterator.next(BranchedChangesetIterator.java:66) at com.atlassian.jira.plugins.dvcs.service.remote.BranchedChangesetIterator.next(BranchedChangesetIterator.java:23) at com.atlassian.jira.plugins.dvcs.sync.impl.DefaultSynchronisationOperation.synchronise(DefaultSynchronisationOperation.java:64) at com.atlassian.jira.plugins.dvcs.sync.impl.DefaultSynchronizer$1.run(DefaultSynchronizer.java:79) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.eclipse.egit.github.core.client.RequestException: Server Error (500) at org.eclipse.egit.github.core.client.GitHubClient.createException(GitHubClient.java:516) at org.eclipse.egit.github.core.client.GitHubClient.get(GitHubClient.java:662) at org.eclipse.egit.github.core.service.CommitService.getCommit(CommitService.java:179) at com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.getDetailChangeset(GithubCommunicator.java:168) ... 16 more{code} We haven't changed anything on the GHE or JIRA side, and things have been running smoothly.

    Atlassian JIRA | 4 years ago | Ashton Treadway
    com.atlassian.jira.plugins.dvcs.exception.SourceControlException: could not get result
  3. 0

    GitHub comment 577#105390457

    GitHub | 2 years ago | rultor
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.github:site-maven-plugin:0.10:site (default) on project netbout: Error creating blob: You have triggered an abuse detection mechanism and have been temporarily blocked from calling the API. Please retry your request again later. (403)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 577#105388948

    GitHub | 2 years ago | rultor
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.github:site-maven-plugin:0.10:site (default) on project netbout: Error creating blob: You have triggered an abuse detection mechanism and have been temporarily blocked from calling the API. Please retry your request again later. (403)
  6. 0

    Two-factor authentication doesn't work (1.8.0)

    GitHub | 3 years ago | smarek
    org.eclipse.egit.github.core.client.RequestException: Must specify two-factor authentication OTP code. (401)

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.eclipse.egit.github.core.client.RequestException

      Server Error (500)

      at org.eclipse.egit.github.core.client.GitHubClient.createException()
    2. Eclipse EGit GitHub API Core
      CommitService.getCommit
      1. org.eclipse.egit.github.core.client.GitHubClient.createException(GitHubClient.java:516)
      2. org.eclipse.egit.github.core.client.GitHubClient.get(GitHubClient.java:662)
      3. org.eclipse.egit.github.core.service.CommitService.getCommit(CommitService.java:179)
      3 frames
    3. com.atlassian.jira
      GithubCommunicator.getDetailChangeset
      1. com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.getDetailChangeset(GithubCommunicator.java:168)
      1 frame