-
-
Notifications
You must be signed in to change notification settings - Fork 879
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
Bug: logs blame skip_dir config instead of skip_file #3173
Comments
Please can you test the following PR to potentially resolve your issue. To test the PR, first install all the require platform dependencies to build the client on your respective platforms. Please read https://github.com/abraunegg/onedrive/blob/master/docs/install.md#building-from-source---high-level-requirements and then follow correctly for your platform. Important Currently there is an issue with installing the DMD or LDC compiler using the documentation instructions: This is not something I can solve and I have emailed the appropriate folk and raised dlang/dmd#20830 Please augment the installation of DMD or LDC with your distribution version if it is available Once this is done, to clone the PR to resolve your issue, you can use a script like the following:
This script will create a local folder called To run the PR, you need to run the client from the PR build directory:
To install the PR, you will need to perform When running the PR, your version should be: If you still encounter an issue, please generate a new verbose debug log following this process: https://github.com/abraunegg/onedrive/wiki/Generate-debug-log-for-support |
Hi, I so I fetched the fix branch (with commit 07a679...) on the repo downloaded and kept after initial installation, checked it out on it, ran the configure, and executed
I'll just say that I did not double check if all matching 3 lines of sync.d needed the update (nor which one is involved here), but guess you are right to change them all, given the code comments. |
Describe the bug
In src/sync.d, search for the string "Skipping file - excluded by skip_dir config:". Then, you will see that what is actually tested there (in at least 1 of the 3 matches you get) is the skip_file pattern. I got confuse slightly by the logs. Minor, but could you adjust the debug log ?
Operating System Details
Linux belalachnos 6.8.0-55-generic #57-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 12 23:42:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Linuxmint Description: Linux Mint 22.1 Release: 22.1 Codename: xia
Client Installation Method
From Source
OneDrive Account Type
Business | Office365
What is your OneDrive Application Version
onedrive v2.5.5-5-g0389483
What is your OneDrive Application Configuration
What is your 'curl' version
bwak@belalachnos:~$ curl --version curl 8.5.0 (x86_64-pc-linux-gnu) libcurl/8.5.0 OpenSSL/3.0.13 zlib/1.3 brotli/1.1.0 zstd/1.5.5 libidn2/2.3.7 libpsl/0.21.2 (+libidn2/2.3.7) libssh/0.10.6/openssl/zlib nghttp2/1.59.0 librtmp/2.3 OpenLDAP/2.6.7 Release-Date: 2023-12-06, security patched: 8.5.0-2ubuntu10.6 Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd
Where is your 'sync_dir' located
Local
What are all your system 'mount points'
What are all your local file system partition types
bwak@belalachnos:~$ lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda ├─sda1 vfat FAT32 1F03-23F3 500,6M 2% /boot/efi └─sda2 ext4 1.0 0f3fbe06-91f9-4f92-a70a-cbfd43f98e08 97,2G 11% / sdb ├─sdb1 ext4 1.0 Parmesan 0804bca6-f221-48f7-b010-4525b41456ad 649,4G 0% /home └─sdb3 ext4 1.0 Backer decc4eaa-d191-4d38-bfef-bcb8bc9dad32 69,2G 19% /timeshift
How do you use 'onedrive'
Not relevant I think. I'll just say that I just installed linux and onedrive client. I wanted to download content from university of another computer using onedrive before.
Steps to reproduce the behaviour
Install my linux OS normally
Then install onedrive following install.md
Then follow usage.md up to doing the dry run with :
onedrive -s -v -v --dry-run (you may prefer single -v, but I used grep "Skipping" instead )
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
Additional context
No response
The text was updated successfully, but these errors were encountered: