Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A AsapoWorker
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FS-SC
  • AsapoWorker
  • Merge requests
  • !45

Handle AsapoDataNotInCacheError in AsapoReceiver

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Tim Schoof requested to merge asapo_data_not_in_cache_error into master Jun 07, 2022
  • Overview 0
  • Commits 3
  • Pipelines 3
  • Changes 5

In case the data is not in the cache any more, the data is lost, and thus an AsapoDataNotInCacheError is mapped to a MissingDataError.

SimpleAsapoReceiver can now also throw a MissingDataError, but this should be ok as a worker either expects this error or it falls back to the defaul no-op handler.

The implementation revealed an error in the testing code, which is now fixed in the first commit.

Closes #10 (closed)

Edited Jun 07, 2022 by Tim Schoof
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: asapo_data_not_in_cache_error

imprint | privacy | Conditions of Use