Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D Demonstrator - Reasoning WebAPI
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • cogsyscogsys
  • Dare2DelDare2Del
  • Demonstrator - Reasoning WebAPI
  • Issues
  • #63
Closed
Open
Issue created Jun 09, 2021 by Siebers, Michael@michael.siebersOwner

Endpoint irrelevant/file returns 500

Test have detected a case where the endpoint irrelevant/file responds with status code 500. It turned out that the predicate irrelevant/1 throws an exception. So the behavior of the WebAPI is correct.

Source of the exception is the predicate `manipulation_time/2'. When called with a directory as first argument the stored dict does not have the appropriate key. Thus an exception is thrown.

Evidence

  • Failed tests: system_test:endpoint_irrelevant@file of job https://gitlab.rz.uni-bamberg.de/cogsys/dare2del/demonstrator/-/jobs/72393.
  • Loaded background theory database
  • Request body: {"abs_path": "dir_1/file_new"}

Tasks

  • Refine the irrelevance_common.plt tests to catch this error in the future.
  • Safeguard `manipulation_time/2' to fail when called with an directory at first argument.
  • Test other irrelevance_common.pl predicates for similar errors.
Assignee
Assign to
Time tracking