Project importer hangs when importing from BitBucket with an access token.

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

Importer hangs (logs show success with some attempts) when importing from BitBucket with an access token. But the "stuck" behavior doesn't occur when using login credentials.

Steps to reproduce

Example Project

What is the current bug behavior?

UI/ or the API is "stuck" in the importing stage. But logs show success of imports. Using login credentials instead of access tokens seems to be a workaround.

What is the expected correct behavior?

Conclude the import status correctly with an access token.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

 (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`)  (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`)  

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)

(we will only investigate if the tests are passing)

Possible fixes