Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mat2
mat2
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • jvoisin
  • mat2mat2
  • Merge Requests
  • !90

Closed
Opened Nov 23, 2020 by jvoisin@jvoisinMaintainer
  • Report abuse
Report abuse

Raise a ValueError explicitly

  • Overview 3
  • Commits 2
  • Pipelines 3
  • Changes 3

Explicitly raise a ValueError exception instead of silently catching it and spit a line of log. This might be useful for interfaces to mat2.

Edited Nov 23, 2020 by jvoisin
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: jvoisin/mat2!90
Source branch: valuerror_instance