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

Allow to error one stream and publish another #9

Open
pauby opened this issue Oct 31, 2022 · 0 comments
Open

Allow to error one stream and publish another #9

pauby opened this issue Oct 31, 2022 · 0 comments
Labels
Improvement Issues that enhances existing functionality, or adds new features

Comments

@pauby
Copy link
Member

pauby commented Oct 31, 2022

Currently, if you have 2 streams where one fails and other is updated, you can either use 'ignore' to publish updated stream and ignore error from failed one or throw an exception and fail the whole update process for that package without publishing stream which got updated. However there is no way to "throw" an exception for one stream without failing whole package.

So I think, there should be an option to put StreamsErrors along with Streams in hashtable that au_GetLatest returns. It would contain catched exceptions thrown by failed streams (or possibly just error messages, but I think passing whole exception will allow more control) for streams that failed and also increment error count returned by vars like $global:info.error_count.total, so we could fail AppVeyor build on that kind of "partial" package error too.

Issue migrated from majkinetor/au#190

@pauby pauby added the Improvement Issues that enhances existing functionality, or adds new features label Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Issues that enhances existing functionality, or adds new features
Projects
None yet
Development

No branches or pull requests

1 participant