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

Fix Bug #3122: Fix 'sync_list' globbing rule application #3123

Merged
merged 5 commits into from
Feb 22, 2025

Conversation

abraunegg
Copy link
Owner

  • Add check for 'globbing' and 'wildcard' rules, that the number of segments before the first wildcard character need to match before the actual rule can be applied

* Add check for 'globbing' and 'wildcard' rules, that the number of segments before the first wildcard character need to match before the actual rule can be applied
@abraunegg abraunegg added this to the v2.5.5 milestone Feb 16, 2025
* Drop this debugging
* Only calculate ruleSegments and pathSegments once
* Use same calculation method to count path segments for applicability globbing rule as this is more consistent
@abraunegg abraunegg merged commit 8ecdbab into master Feb 22, 2025
10 checks passed
@abraunegg
Copy link
Owner Author

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Repository owner locked and limited conversation to collaborators Mar 2, 2025
@abraunegg abraunegg deleted the fix-issue-3122 branch March 10, 2025 18:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: "A database statement execution error occurred: FOREIGN KEY constraint failed"
1 participant