Skip to content

Add models and routes for reporting dataset lookup errors #1134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

ponyisi
Copy link
Collaborator

@ponyisi ponyisi commented Aug 4, 2025

Companion to ssl-hep/ServiceX_DID_Finder_lib#38 . Adds a new dataset lookup failure endpoint and updates models as necessary. Still missing an endpoint to query what the error was (for client information) and tests.

Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds functionality to handle and report dataset lookup errors in the ServiceX application. It introduces a new endpoint for receiving error notifications from the dataset lookup service and updates the data models to support error tracking.

  • Adds a new /servicex/internal/transformation/<dataset_id>/error endpoint for reporting dataset lookup failures
  • Extends the DatasetStatus enum with three new error states: does_not_exist, bad_name, and internal_failure
  • Adds a new TransformStatus.bad_dataset state to mark transformations that fail due to dataset issues

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
servicex_app/routes.py Registers the new FilesetError resource and endpoint
servicex_app/resources/internal/fileset_error.py Implements the error handling endpoint with dataset status updates and transformation cleanup
servicex_app/models.py Extends DatasetStatus and TransformStatus enums with new error states

@ponyisi
Copy link
Collaborator Author

ponyisi commented Aug 4, 2025

Actually we already have the endpoint for querying dataset status so all that's needed is the tests

Copy link
Collaborator

@gordonwatts gordonwatts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But wait - where are the tests?

@@ -157,6 +157,7 @@ class TransformStatus(Enum):
complete = ("Complete", True)
fatal = ("Fatal", True)
canceled = ("Canceled", True)
bad_dataset = ("Bad Dataset", True)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I'm just getting going in the review here, but shouldn't empty be here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

? I don't think "existing but empty" dataset should be an error condition?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants