Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 834
    • Issues 834
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #5114

Closed
Open
Created Jun 15, 2018 by Bitbucket Importer@bitbucket_importerOwner

Thg 4.6 does not ask for username on pull/push

Created originally on Bitbucket by kkarbowiak (Krzysiek Karbowiak)

I think there is a regression in Thg 4.6 regarding pull/push/incoming/outgoing operations and URLs without username prefix.

Steps to reproduce:

  1. Create a local repository
  2. Do a commit
  3. Create a hosted repository, e.g. a private one on Bitbucket
  4. Add the hosted repository in Synchronize, note the "Remove authentication data from URL" checkbox is checked by default and it removes the user name
  5. Push

At the last step Thg asks for password but not username, and the operation ends with error. Below is the log:

test% % hg push https://bitbucket.org/kkarbowiak/test
pushing to https://bitbucket.org/kkarbowiak/test
http authorization required for https://bitbucket.org/kkarbowiak/test
realm: Bitbucket.org HTTP
user:  HTTP Error: 403 (Max Invalid Password Attempts)
[command returned code 255 Fri Jun 15 14:14:01 2018]

Previous versions of Thg asked for both username and password in such cases.

Adding username to the URL in Synchronize fixes the problem.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking