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

Notify when a property is not available, and skip to the next dataset. #383

Merged
merged 1 commit into from
Oct 9, 2018
Merged

Conversation

flixman
Copy link
Contributor

@flixman flixman commented Oct 6, 2018

When a property on a dataset is not available, znapzend dies with an error message. This PR changes that by a warning and the skipping of that dataset. By doing this, we can set org.znapzend properties on descendant datasets (specifically thinking on the org.znapzend:enable, to skip those datasets that have it set to "off" when coming from a recursive parent).

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 87.5% when pulling 484fdd4 on flixman:master into 4ccbe71 on oetiker:master.

Copy link
Owner

@oetiker oetiker left a comment

Choose a reason for hiding this comment

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

yep makes sense not chickening out here

@oetiker oetiker merged commit c319917 into oetiker:master Oct 9, 2018
@oetiker
Copy link
Owner

oetiker commented Oct 9, 2018

sorry missed the context ... getting a warning every time around does not seem all that good a solution either ... since this one property is fine in the context of #154

@flixman
Copy link
Contributor Author

flixman commented Oct 9, 2018

I am running it right now, and I am only getting a warning when the service is reloaded or started (which is the only moment when the backup plan is refreshed).

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.

3 participants