-
Notifications
You must be signed in to change notification settings - Fork 278
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
Exclusions are being ignored in 5.2 #924
Comments
Edit: check my reply |
The issue is not true, at least for me. After tinkering for a while I realized I was improperly formating the paths by using old ways of doing it. It is relative paths to your Mega drive rather an an absolute windows path. Where the root is your mega root. So surface folders to your mega drive are direct. So if you were syncing C:\Users\Bobby\Desktop\Jellyfish And Jellyfish had the folders box and moon, and box had the subfolder blue Then an exclusion towards Box would just be -d:box And furthermore an exclusion towards blue, would be -d:box\blue Edit: fix slash direction Edit 2: in some cases it does appear to be behaving strangely Edit 3: refer to post below. |
I figured out what it was. When you use "Choose folder" and choose a folder, the GUI shows the paths with "/". However, when it adds the entries to .megaignore it switches them to "\". So on a hunch I changed all "\" to "/" in .megaignore and suddenly it started ignoring correctly. Edit: I wonder if you change "\" to "\\" it will work? It might think the "\" is an escape character... |
I have no slashes in my .megaignore file.
So that subfolders Disk and eBooks are not synced. I get a Sync issue in megasync: "Error identifying folder content in local file system". When I click Ignore and confim that I want to ignore it, megasync crashed on me (I sent a diagnostic report on next start, with link to this github issue). Otherwise, the Sync issue keeps coming back and is not ignored. |
I hope this gets fixed soon, I spent hours trying to debug why my exclusions were just being ignored. Thankfully the slashes turned out to be the issue, though I would really like it if the gui worked as expected |
I had TERRABYTES of data uploaded because the program put the slashes in backwards. I'm so grateful for those who posted here - thank you. To whoever has the power to address this issue, please give it some attention, this bug is pretty serious from a user-perspective. Thank god I am paying for unlimited data right now through my ISP. |
After updating to 5.2 and realizing all my exclusions had been removed, I then re-added them to the backup settings in the new format to the .megaignore file. The only problem is that despite restarting the client and seeing the ignore settings were correct, the app isn't honoring the ignores and I'm getting sync errors about either files being in use or "error identifying folder content in local file system".
This is on Windows 11, all the latest updates installed.
The paths in .megaignore are for directories and follow the format:
-d:path_relative_to_backup_folder
The ignored folders have the green and red icons on them from Megasync meaning it's still trying to sync them, plus I'm getting the errors explained above that files in these ignored folders aren't able to sync.
The text was updated successfully, but these errors were encountered: