Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N nrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • argo
  • nrm
  • Issues
  • #31
Closed
Open
Issue created Feb 07, 2019 by Swann Perarnau@perarnauOwner

Update tornado/zmq/ioloop to latest stable

The current code depends on version locking of the tornado package and others to avoid a major refactor of its event loop. The latest version of these packages have indeed deprecated the APIs used in the current code.

As pipenv is somewhat lacking in terms of version locking, there's a high chance that we will end up with nasty bugs soon if we don't clean that up. See ioloop mentions in the tornado release notes.

Assignee
Assign to
Time tracking