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

Misleading category not found processing #160

Open
manasouza opened this issue Mar 24, 2024 · 1 comment · May be fixed by #165
Open

Misleading category not found processing #160

manasouza opened this issue Mar 24, 2024 · 1 comment · May be fixed by #165
Assignees
Labels

Comments

@manasouza
Copy link
Owner

manasouza commented Mar 24, 2024

When some registry with unmapped category is processed alone, it fails and stop the processing.
In the same scenario but now while processing with other valid registries, it shows the warning only and records the registry as processed.

The fix should consider to not break the workflow, show the warning log and do not mark the registry as processed, so it could be evaluated again on the next run.

Screenshot 2024-03-22 072445

Screenshot 2024-03-22 072933

@manasouza manasouza added the bug label Mar 24, 2024
@manasouza manasouza changed the title Unmapped categories fails silently when processed with more items Misleading category not found processing Mar 24, 2024
@manasouza manasouza self-assigned this Apr 8, 2024
@manasouza
Copy link
Owner Author

Wait until branch where pubsub fix was done to be merged to main branch

@manasouza manasouza linked a pull request Oct 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

1 participant