Blockmap Comparision Fails for AWS S3
See original GitHub issue- Version: 20.19.2
- Target: Windows
I found that when we use S3 as a provider then it fails to compare and check blockmap files at this place. This is the log of fileInfo
, newBlockMapUrl
and oldBlockMapUrl
Object.
Fileinfo :-
{
url: URL{
href: 'https://AWS_S3_HOST//bucket-yashraj/electron%20Setup%2011.0.3.exe',
origin: 'https://AWS_S3_HOST',
protocol: 'https:',
username: '',
password: '',
host: 'AWS_S3_HOST',
hostname: 'AWS_S3_HOST',
port: '',
pathname: '//bucket-yashraj/electron%20Setup%2011.0.3.exe',
search: '',
searchParams: URLSearchParams{
},
hash: ''
},
info: {
url: 'electron Setup 11.0.3.exe',
sha512: 'k3seJ1BoSsaxAxODNJqhf7xUh6vfQUflvU+qu0mXXiuBFb8gpvt0oDS2rJm6gP+4lEilw6Gt8bt7BbimXftVNQ==',
size: 52021199
}
}
newBlockMapUrl :-
{
url: URL{
href: 'https://bucket-yashraj/electron%20Setup%2011.0.3.exe',
origin: 'https://bucket-yashraj',
protocol: 'https:',
username: '',
password: '',
host: 'bucket-yashraj',
hostname: 'bucket-yashraj',
port: '',
pathname: '/electron%20Setup%2011.0.3.exe',
search: '',
searchParams: URLSearchParams{
},
hash: ''
}
}
oldBlockMapUrl :-
{
url: URL{
href: 'https://bucket-yashraj/electron%20Setup%2011.0.3.exe',
origin: 'https://bucket-yashraj',
protocol: 'https:',
username: '',
password: '',
host: 'bucket-yashraj',
hostname: 'bucket-yashraj',
port: '',
pathname: '/electron%20Setup%2011.0.3.exe',
search: '',
searchParams: URLSearchParams{
},
hash: ''
}
}
You can see that AWS_S3_HOST is removed from newBlockMapUrl
and oldBlockMapUrl
objects. So it will never get blockmap files!!.
I have checked with replacing ${fileInfo.url.pathname}
with ${fileInfo.url.href}
and have checked for both provider s3
and general
and it is working fine.
@develar I am also creating PR to get reviewed by you if it is proper solution and to make electron better!! 🙂
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Error Responses - Amazon Simple Storage Service
Error Code Description HTTP Status Code
AccessControlListNotSupported The bucket does not allow ACLs. 400 Bad Request
AccessDenied Access Denied 403 Forbidden
BucketAlreadyOwnedByYou 409 Conflict (in all...
Read more >Monitoring progress with replication metrics and ...
Monitor the progress of replication with S3 Replication metrics by tracking ... Receiving replication failure events with Amazon S3 Event Notifications.
Read more >Blocking public access to your Amazon S3 storage
A guide to using block public access with Amazon S3. ... PUT Bucket acl and PUT Object acl calls fail if the specified...
Read more >How S3 Object Lock works - Amazon Simple Storage Service
Describes the main features of S3 Object Lock, including retention modes, legal holds, and bucket configuration.
Read more >Resilience in Amazon S3 - Amazon Simple Storage Service
Describes AWS architecture for data redundancy and specific Amazon S3 ... that automatically fail over between Availability Zones without interruption.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let me keep it open since it is electron-builder failure to not strip trailing slash. Humans have a right to make mistakes.
@develar It was my bad. It’s just that trailing slash
"/"
in the endpoint 😒 Thanks for the help. 👍 It’s working !!