Ashutosh Narkar fec62e8522 Update downloader's Etag based on bundle activation ...

Earlier the Etag on the downloader would be updated unconditionally after every attempt to download a bundle. This could lead to a situation wherein a bundle fails to activate and would remain in an unactivated state since any subsequent downloads of the same version of the bundle would not trigger the activation process. This change attempts to resolve the issue by allowing the client to reset the Etag on the downloader incase of downloader errors and bundle activation failures. The drawback now is that we could end up re-downloading the same version of a bundle multiple times till it successfully activates. This situtation is likely to occur when using multiple bundle sources where a bundle may depend on some other. Generally using multiple bundle sources isn't recommended so the extra network traffic as a result of the re-downloads although not ideal may not too harmful.

Fixes #2220
Fixes #2279

Signed-off-by: Ashutosh Narkar <anarkar4387@gmail.com>

2020-04-10 11:17:23 -07:00

..

config_test.go

Run make fmt with new goimports cmd

2019-09-27 09:55:11 -04:00

config.go

Run make fmt with new goimports cmd

2019-09-27 09:55:11 -04:00

plugin_test.go

Update downloader's Etag based on bundle activation

2020-04-10 11:17:23 -07:00

plugin.go

Update downloader's Etag based on bundle activation

2020-04-10 11:17:23 -07:00

status.go

plugins/bundle: Include last successful request timestamp in status

2020-02-07 13:01:21 -05:00