Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A AsapoWorker
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FS-SC
  • AsapoWorker
  • Merge requests
  • !9

Feat: Add function for likely_done case

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Mikhail Karnevskiy requested to merge feat/handle_likely_done into master Oct 07, 2020
  • Overview 2
  • Commits 2
  • Pipelines 2
  • Changes 2

@tim.schoof

Creation of new thread for new substream is quite special situation. It may be useful for worker to know it.

I have a used case: My worker have ZMQ connection on certain port. New connection can not be established in the new thread, because port is busy. Old connection should be closed.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feat/handle_likely_done

imprint | privacy | Conditions of Use