Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
TortoiseGit
TortoiseGit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 304
    • Issues 304
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 9
    • Merge requests 9
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #3210

Closed
Open
Created May 16, 2018 by Cloud@cloud9370

index.lock always created after refresh log window working tree changes

index.lock always created after refresh log window working tree changes

What steps will reproduce the problem?

  1. Watch files inside .git directory
  2. Show log window
  3. Click working tree changes at log window first row
  4. Refresh
  5. After operation done index.lock created and doesn't delete

What is the expected output? What do you see instead?

index.lock created and doesn't delete, it should be deleted.

What version of TortoiseGit and Git are you using? On what operating system?

  • Windows 10, Git 2.17.0.windows.1, Git LFS 2.4.0
  • TortoiseGit 2.6.0.0
  • TortoiseGit 2.6.1.0-preview

Please provide any additional information below.

I downgraded to 2.5.0.0, index.lock deleted fine.

Edited May 16, 2018 by Cloud
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking