Pre-release commit

Anything below this first part is definitely me being astounded
This is the commit where it is in a working state that isn't exactly
primitive, but it's not comprehensive, fully fleshed out, or polished
either. But I like where it's going

You wouldn't believe it.
I came back to this after a MASSIVE crash out with how HUGE and CLUNKY
trying to use the AWS SDK was.
Well
Guess what
GUESS
Literally I just went to test it this morning and I freaking KID YOU NOT
it just worked.
no changes.
it just worked.
YOU WANNA KNOW HOW I CAN TELL?
Look at this FREAKING COMMIT and see that ALL THAT CHANGED was the
todo.md FILE
literally
what
the
fart

I shouldn't complain but OH MY GOODNESS
I spent SO LONG working on it and it turned out it WASN'T all for naught
because I guess something was just...stuck. Bad credentials somehow? I
don't know anymore.
I'm just glad it's over.
This commit is contained in:
ForeverPyrite
2025-09-19 21:02:12 -04:00
parent 8b3cc6cb3e
commit 76cc06d7e1
10 changed files with 252 additions and 605 deletions

View File

@@ -1,4 +1,3 @@
use std::env;
use std::fs;
use std::io::Write;
@@ -63,7 +62,6 @@ mod sync_tests {
// Cleanup
fs::remove_file(local_upload_path).unwrap();
fs::remove_file(local_download_path).unwrap();
// NOTE: The test file on R2 is not deleted as there is no delete API yet.
}
}
@@ -132,6 +130,8 @@ mod async_tests {
// Cleanup
fs::remove_file(local_upload_path).unwrap();
fs::remove_file(local_download_path).unwrap();
// NOTE: The test file on R2 is not deleted as there is no delete API yet.
// 6. Delete file
bucket.delete_file(r2_file_key).await.unwrap();
}
}