{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":780948955,"defaultBranch":"master","name":"rclone","ownerLogin":"moqmar","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-04-02T13:18:17.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5559994?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1714456635.0","currentOid":""},"activityList":{"items":[{"before":"84d3e8a7b592fa378ac245c42c49c8520ecbbaa9","after":"5555a057c56e525a213dd74f8e0f96174aceef36","ref":"refs/heads/fix-azureblob-writeonly","pushedAt":"2024-06-17T14:00:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"moqmar","name":"Moritz Marquardt","path":"/moqmar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5559994?s=80&v=4"},"commit":{"message":"azureblob: only request 1 result in readMetadataUsingList\n\nThis should be enough given that Microsoft promises list results to be alphanumerically sorted.","shortMessageHtmlLink":"azureblob: only request 1 result in readMetadataUsingList"}},{"before":"839ca0e5c416027094802f4f5fd2f0046ecd527b","after":"84d3e8a7b592fa378ac245c42c49c8520ecbbaa9","ref":"refs/heads/fix-azureblob-writeonly","pushedAt":"2024-06-17T13:18:14.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"moqmar","name":"Moritz Marquardt","path":"/moqmar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5559994?s=80&v=4"},"commit":{"message":"azureblob: only request 1 result in readMetadataUsingList\n\nThis should be enough given that Microsoft promises list results to be alphanumerically sorted.","shortMessageHtmlLink":"azureblob: only request 1 result in readMetadataUsingList"}},{"before":"a42930b300312461acb903df1c89f7cd2a920e67","after":"839ca0e5c416027094802f4f5fd2f0046ecd527b","ref":"refs/heads/fix-azureblob-writeonly","pushedAt":"2024-04-30T06:10:52.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"moqmar","name":"Moritz Marquardt","path":"/moqmar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5559994?s=80&v=4"},"commit":{"message":"azureblob: allow working with only list+create/write permissions (fix no_head_object/add no_read_for_metadata)\n\nThere are three reasons an option why one would avoid HEAD requests on azureblob, with this now mainly implementing the latter one:\n\n- no_head_object: Don't do a HEAD *before* writing to (or reading from) an object, to reduce the number of transactions and thus increase performance. **This already exists in azureblob, a small issue was fixed here where using a prefix would still require a HEAD request to the prefix itself.**\n- no_head: Don't do a HEAD *after* writing to an object, for the same reason but at the cost of \"increasing the chance for undetected upload failures\".  **This is still not implemented for azureblob yet and quite complex, see s3.Object.Update()!**\n- no_read_for_metadata: Instead of doing a HEAD to get metadata, use a list operation, to avoid requiring READ permissions for immutable/append-only applications (this seems to be quite azureblob-specific) - one could also use both no_head_object and no_head together to achieve this, but then uploads wouldn't be verified.\n\nFixes #6162 and #7027","shortMessageHtmlLink":"azureblob: allow working with only list+create/write permissions (fix…"}},{"before":"d1904f0b913ac525d0d4f65330452abc8f60b514","after":"a42930b300312461acb903df1c89f7cd2a920e67","ref":"refs/heads/fix-azureblob-writeonly","pushedAt":"2024-04-30T06:03:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"moqmar","name":"Moritz Marquardt","path":"/moqmar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5559994?s=80&v=4"},"commit":{"message":"azureblob: allow working with only list+create/write permissions (fix no_head_object/add no_read_for_metadata)\n\nThere are three reasons an option why one would avoid HEAD requests on azureblob, with this now implementing the latter one:\n\n- no_head_object: Don't do a HEAD *before* writing to (or reading from) an object, to reduce the number of transactions and thus increase performance. **This is quite complex and thus not implemented here, see s3.Object.Update()!**\n- no_head: Don't do a HEAD *after* writing to an object, for the same reason but at the cost of \"increasing the chance for undetected upload failures\". This already exists in azureblob, a small issue was fixed here.\n- no_read_for_metadata: Instead of doing a HEAD to get metadata, use a list operation, to avoid requiring READ permissions for immutable/append-only applications (this seems to be quite azureblob-specific) - one could also use both no_head_object and no_head together to achieve this, but then uploads wouldn't be verified.\n\nAlso fixes an as of now unreported issue where the --no-head option wouldn't work at all with a prefix set on the remote.\n\nFixes #6162 and #7027","shortMessageHtmlLink":"azureblob: allow working with only list+create/write permissions (fix…"}},{"before":null,"after":"d1904f0b913ac525d0d4f65330452abc8f60b514","ref":"refs/heads/fix-azureblob-writeonly","pushedAt":"2024-04-30T05:57:15.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"moqmar","name":"Moritz Marquardt","path":"/moqmar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5559994?s=80&v=4"},"commit":{"message":"azureblob: allow working with only list+create/write permissions (fix no_head_object/add no_read_for_metadata)\n\nThere are three reasons an option why one would avoid HEAD requests on azureblob, with this now implementing the latter one:\n\n- no_head_object: Don't do a HEAD *before* writing to (or reading from) an object, to reduce the number of transactions and thus increase performance. **This is quite complex and thus not implemented here, see s3.Object.Update()!**\n- no_head: Don't do a HEAD *after* writing to an object, for the same reason but at the cost of \"increasing the chance for undetected upload failures\". This already exists in azureblob, a small issue was fixed here.\n- no_read_for_metadata: Instead of doing a HEAD to get metadata, use a list operation, to avoid requiring READ permissions for immutable/append-only applications (this seems to be quite azureblob-specific) - one could also use both no_head_object and no_head together to achieve this, but then uploads wouldn't be verified.\n\nThis hence fixes #6162 and #7027, as well as an as of now unreported issue where the --no-head option wouldn't work at all with a prefix set on the remote.","shortMessageHtmlLink":"azureblob: allow working with only list+create/write permissions (fix…"}},{"before":"93c960df59497269c93d4751b73dd3e8b89d8d18","after":"9fa610088f00337264a9f4edd57694cfcc0b51ba","ref":"refs/heads/master","pushedAt":"2024-04-30T05:56:17.000Z","pushType":"push","commitsCount":81,"pusher":{"login":"moqmar","name":"Moritz Marquardt","path":"/moqmar","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5559994?s=80&v=4"},"commit":{"message":"docs: add Backblaze as a sponsor","shortMessageHtmlLink":"docs: add Backblaze as a sponsor"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEZ3DMbAA","startCursor":null,"endCursor":null}},"title":"Activity · moqmar/rclone"}