Uploaded image for project: 'SystemDS'
  1. SystemDS
  2. SYSTEMDS-2540

Stop Exception

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: SystemDS 2.0
    • Fix Version/s: SystemDS 2.0
    • Component/s: APIs, Test
    • Labels:
    • Environment:
      All
    • Flags:
      Patch

      Description

      Currently the system require us to either check stdOut, or look if a file has been created aka the script did not terminate. If one wants to test for a stop condition in SystemDS.

      Unfortunately neither is available at the moment, so we will have to make some.

      A idea is that the exception thrown from a stop should not be caught and just print, but be thrown all the way out to a user, but with the twist that it should still provide the same print as before if executed normally not a stack trace.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              baunsgaard Sebastian Baunsgaard

              Dates

              • Created:
                Updated:
                Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 3h
              3h
              Remaining:
              Remaining Estimate - 3h
              3h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Issue deployment