In this release, significant efforts have been made to resolve the persistent "Bad Request" error.
This error typically occurs when uploading large takeout files. However, there is currently no clear and reproducible way to trigger it with a simple dataset.
The "Bad Request" error is believed to stem from asset upgrades. Previously, the code would delete the lower-quality asset and then upload a higher-quality version. This process has now been simplified by leveraging the API call replaceAsset.
What's Changed
- HTTP errors are now correctly reported in the API-TRACE files
- GPS coordinates are obfuscated in the logs, for a better privacy when sharing the logs
- use
replaceAssetwhen upgrading assets - Fix panic: time: missing Location in call to Time.In when using the archive command by @simulot in #596
- Implement CacheReader and enhance asset handling with tests by @simulot in #597
- A few improvements to the uploads by @simulot in #599
Full Changelog: v0.23.0-RC5...v0.23.0-RC6