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

chore: backend support for notifying operation status changes #29

Merged
merged 3 commits into from
Dec 8, 2023

Conversation

aschoettler
Copy link
Contributor

No description provided.

b := tx.Bucket(OpLogBucket)

prevValue, err := o.getOperationHelper(b, id)
if err != nil {
return fmt.Errorf("getting operation %v: %w", id, err)
return prevValue, fmt.Errorf("getting operation %v: %w", id, err)
Copy link
Owner

Choose a reason for hiding this comment

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

nit: these should probably all be nil

@garethgeorge garethgeorge changed the title chore: Backend support for notifying operation status changes chore: backend support for notifying operation status changes Dec 8, 2023
@garethgeorge garethgeorge merged commit 019a0c0 into garethgeorge:main Dec 8, 2023
@garethgeorge
Copy link
Owner

Hi, I'm evaluating relicensing Backrest as AGPL-3.0 . Thanks for contributing this fix!

I'm wondering if you'd be willing to retroactively sign a CLA? Or grant more specific permission to retain the copyright for your PRs but relicense your changes in the codebase under AGPL-3.0 .

I've become aware of a few SAAS looking at selling Backrest which goes philosophically against what I created it for (well they're welcome to -- but their platforms should be OSS and self-hostable re: the same freedoms Backrest provides!).

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