Closed nathannli closed 1 month ago
sorry please put this bug on hold. I think it may have to do with passwordless login...
So this is a bad regression with v2.5.1 due to #2813 fix.
Please use v2.5.0 to auth then upgrade.
I am in position to fix this until Monday 30th AEST
sorry please put this bug on hold. I think it may have to do with passwordless login...
nothing to do with the passwordless login, same issue persists. Likely is the one you linked.
I couldn't get it to work using my previous authorization on 2.5.1, so going to sit on 2.5.0 for now. thanks for fast response. feel free to close the issue if it makes sense.
@abraunegg version 2.5.1 was working fine for me, but today Pop_Os! updated it to version v2.5.1 and I'm also getting the same error as OP.
I've downgraded it for now.
Microsoft started sending the ISO date with the fractional part of the second, which is missing in the REGEX that checks the date format.
I'm having the same issue here. The program just immediately enters a crash loop whenever I boot up either of my computers (both running mint 22). Log output is largely the same as what nathannli was seeing.
To all
I will be fixing this issue tomorrow when I am in a location where I have access to do so.
Please hold fire on any more commentary and or raising questions regarding this issue.
Just removing the regex checking timestamps is sufficient to fix this locally. SysTime.fromISOExtString will validate the format for you anyway. Here's a patch if anyone wants to fix it themselves before the official fix is available. No warranties :)
diff --git a/src/util.d b/src/util.d
index 3bfa707..f5868e9 100644
--- a/src/util.d
+++ b/src/util.d
@@ -535,12 +535,6 @@ bool isValidUTCDateTime(string dateTimeString) {
addLogEntry("BAD TIMESTAMP (UTF-8 FAIL): " ~ dateTimeString);
return false;
}
-
- // First, check if the string matches the pattern
- if (!match(dateTimeString, pattern)) {
- addLogEntry("BAD TIMESTAMP (REGEX FAIL): " ~ dateTimeString);
- return false;
- }
// Attempt to parse the string into a DateTime object
try {
@sdt16 This will be fixed tomorrow AEST as per my comment above ...
Fixed ahead of time due importance of fix
Describe the bug
When trying to start the initial sync, it will prompt you to authenticate by clicking the onedrive URL, signing in, and then pasting the resulting URL into the terminal. The resulting URL causes the error "Bad Timestamp"
Operating System Details
What is your 'curl' version
Where is your 'sync_dir' located
Local
What are all your system 'mount points'
What are all your local file system partition types
How do you use 'onedrive'
personal use, basic sync open files here and there for write, upload. Nothing complicated.
This was just an upgrade where the previous verison has been purged (including .config files)
Steps to reproduce the behaviour
1) onedrive --sync 2) sign in on browser 3) paste code from browser into terminal
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
No response
Additional context
No response