Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pypy pypy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 676
    • Issues 676
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

April 05-07 - Mercurial Paris Conference 2023 - One day of workshop dedicated to Heptapod and Mercurial usage and workflow. There are still places available for both workshops and talks!

  • PyPyPyPy
  • pypypypy
  • Merge requests
  • !744

Initialize lock timeout on windows if timeout is infinite

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Ondrej Baranovič requested to merge branch/initialize_lock_timeout_on_windows into branch/default Jul 23, 2020
  • Overview 2
  • Commits 2
  • Pipelines 1
  • Changes 1

The variable milliseconds was uninitialised if the given timeout was negative (infinite). This PR fixes the undefined behaviour, the issue I had in #2073 (comment 141518), and possibly also issue #3252 (closed).

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: branch/initialize_lock_timeout_on_windows