Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M mercurial_keyring
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Mercurial Paris conference scheduled ! Main event : 2022-09-22. Call for papers deadline: 2022-06-17.

  • mercurial
  • mercurial_keyring
  • Issues
  • #39

Closed
Open
Created Jul 30, 2014 by Bitbucket Importer@bitbucket_importerOwner

repeat prompts for keyring password

Created originally on Bitbucket by clux (Eirik NA)

Hey, I am trying to troubleshoot here a little as I'm finding things have changed after updating to latest mercurial-keyring:

I have a global ~/.hgrc with:

[extensions]
mercurial_keyring =
record =

[ui]
username = x <x@y.com>

[auth]
myremote.schemes = https http
myremote.prefix = hg.y.com
myremote.username = z

and versions as follows (latest as of now):

pip freeze | grep -E "key|merc"
keyring==3.8
mercurial==2.7.2
mercurial-keyring==0.6.2

Essentially, I find that every authentication requiring hg interaction now require the keyring password. Two repeat calls to hg pull in the same repo will ask for it even if they are just seconds apart.

I'm not sure if there used to be a timer or there was a once per repo thing, but something's different. Has this changed? Is there just a way for it to bug me a bit less?

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