-
Notifications
You must be signed in to change notification settings - Fork 527
[WIP] Create a file-based lockstore component #3418
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
Conversation
Signed-off-by: moonorange <[email protected]>
Signed-off-by: moonorange <[email protected]>
Hi, @elena-kolevska Should I continue with this approach, or should I use files similar to |
Hi @moonorange , I'm happy to see your work on this! |
I am one of the maintainers of this repository and I have no context for what this PR is about or which issue it is addressing. Please first create a new issue in dapr/components-contrib that explains what feature or functionality is needed and why. |
Hi @berndverst, I created a new issue for this PR |
@moonorange we are approaching code freeze, it'd be great if you got the PR ready for review this week. Thanks! |
Ping @moonorange |
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
This pull request has been automatically closed because it has not had activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
This pull request has been automatically closed because it has not had activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
Description
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Related PR and discussion
dapr/dapr#7631 (comment)
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: