Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N
nrm
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • argo
  • nrm
  • Issues
  • #31

Closed
Open
Opened Feb 07, 2019 by Swann Perarnau@perarnau
  • Report abuse
  • New issue
Report abuse New issue

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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: argo/nrm#31