Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg-hgtk thg-hgtk
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 520
    • Issues 520
    • 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
  • TortoiseHg
  • thg-hgtkthg-hgtk
  • Issues
  • #222

Closed
Open
Created May 13, 2009 by Bitbucket Importer@bitbucket_importerOwner

traceback on gdialog due to settings

Created originally on Bitbucket by Anonymous

After using crew version of commit, the commit tool in stable tree traceback on loading settings:

{{{ File "C:\Mercurial\repos\tortoisehg-stable\hggtk\status.py", line 210, in load_settings GDialog.load_settings(self, settings) File "C:\Mercurial\repos\tortoisehg-stable\hggtk\gdialog.py", line 168, in load_settings self._setting_defsize = settings['gdialog'] KeyError: 'gdialog' }}}

I believe some handling might be needed in stable/crew to overcome this, else testing crew will be difficult. I still need to rely on stable for day-to-day work.

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