Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • pikelang
  • pikepike
  • Issues
  • #2403
Closed
Open
Issue created Oct 11, 2001 by Peter Bortas@zinoOwner

Stdio.File->async_connect doesn't work (with threads?)

Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=2403

Reported by David Hedbor, Idonex / Real Networks david@hedbor.org

When using Stdio.File()->async_connect(), you get both the successful callback and the error callback right after doing the call. The connect is not actually done at that time.

Discussions with Hubbe seems to point to this being the case when connecting from a thread other than the main thread. True for Pike 0.6 to 7.3.

Assignee
Assign to
Time tracking