Skip to content
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

Tools: Ignore containers with invalid data/schema with a warning instead of error #788

Closed
2 tasks done
BigRoy opened this issue Jul 19, 2024 · 0 comments · Fixed by #1037
Closed
2 tasks done

Tools: Ignore containers with invalid data/schema with a warning instead of error #788

BigRoy opened this issue Jul 19, 2024 · 0 comments · Fixed by #1037
Assignees

Comments

@BigRoy
Copy link
Collaborator

BigRoy commented Jul 19, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

When containers are returned by a host with invalid data, e.g. invalid representation id, or that data completely lacking or in any way mismatching with the container schema then the tools should not fail to work, but log a warning or error and continue listing those entries that it can resolve correctly.

error

Which results in empty loader:

empty_loader

Expected Behavior:

Log a warning or error and continue listing those entries that it can resolve correctly.

Version

1.0.0

What platform you are running on?

Windows

Steps To Reproduce:

Produce some invalid container results from a hosts get_containers() implementation.

The exact data can be confirmed/tested with:

from ayon_core.pipeline import registered_host
import pprint

host = registered_host()
for container in host.get_containers():
    pprint.pprint(container)

And e.g. invalid data is:
invalid_data

Because it should adhere to this schema: https://github.com/ynput/ayon-core/blob/develop/client/ayon_core/pipeline/schema/container-3.0.json

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

See issue reported on Discord here

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 a pull request may close this issue.

3 participants