Skip to content

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

Closed
Open
Opened Jun 11, 2018 by Jaden DIEFENBAUGH@jdiefenbaugh
  • Report abuse
  • New issue
Report abuse New issue

Offline plotting support is shaky

If the plotter object and the default plotterparameters exist in the local prefix, failing to fetch info from the BEAT web platform should not stop plotting.

The issue came up when using the tutorial VM. Some people didn't have an internet connection and couldn't plot because beat.cmdline was trying to fetch stuff from beat.web even though the plotter objects and default parameters existed.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
bug discussion
Assign labels
  • View project labels
Reference: beat/beat.cmdline#38