Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gdat
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • SPC
  • gdat
  • Issues
  • #45

Closed
Open
Created Oct 21, 2021 by Federico Felici@ffeliciOwner0 of 1 task completed0/1 task

Proper error handling of mds-related errors

It is proposed to use mds status flag passed through tdi to check for errors, instead of tests of the returned data directly.

For example replacing

d = tdi('expression')
if ~ischar(d.data) && ~isempty(d.data)
 % use data
else
 warning('problem')
end

with

[d] = tdi('expression')
if ~rem(d.status,2) % unambigious way to check for problems
  warning('problem')
end

Previous discussion:

  • @vallar started a discussion: (+10 comments)
Edited Oct 21, 2021 by Federico Felici
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking