Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #6762

Closed (moved)
(moved)
Open
Created Sep 04, 2012 by Karsten Loesing@karsten

Make Atlas more robust to inconsistent Onionoo replies

When Onionoo lists a relay in its summary document but doesn't have a details document for that relay, Atlas will run into a "TypeError: relay is undefined" in js/models/relay.js in $.getJSON() in the lookup function. The effect is that Atlas shows "undefined" in its results. The fix is for Atlas to not rely on Onionoo always having a details document. (The other fix is to make Onionoo not return inconsistent replies, but that's something that the database-based Pyonionoo will fix.)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking