Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I i0mapmon-topo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cs
  • gui
  • i0mapmon-topo
  • Issues
  • #3
Closed
Open
Issue created Sep 30, 2021 by Michele Manfredda@michele.manfredda

TOPO Crash quando vengono cambiate le lambda nel "IOM"

Se aggiungo una o più lambda (dal topo), il mono muore. Questo caso deve essere gestito.

Se invece le tolgo, non sembra dar problemi

Se non ce ne sono di specificate, compare un error message complicato.

Lo possiamo lasciare, a patto di aggiungere uno "hint user friendly", tipo "Check that at least one wavelength and its weight are given in the server".

Assignee
Assign to
Time tracking