You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an extension version is deleted, the last_updated_date of its extension database entry is not updated. This causes the mirror to be out-of-sync with upstream.
For example:
Extension Ext has 2 versions ExtV0.0.1 and ExtV0.0.2. Then the last_udpated_date will be the published date of ExtV0.0.2.
For some reason ExtV0.0.1 is deleted, but the last updated time is not changed.
Thus, the mirror wont update the metadata on its end.
This issue causes the mirror to throw an error when its trying to remove some out-of-date extensions.
The text was updated successfully, but these errors were encountered:
Currently, the last-updated-date is only updated when a new extension version
is published. This causes the mirror to be out-of-sync with upstream whenever
an extension version is deleted.
This commit updates the last-updated-date whenever an extension is changed,
including the scenario above.
Fixeseclipse#955.
Signed-off-by: Hoang Thuan Pham <[email protected]>
When an extension version is deleted, the
last_updated_date
of its extension database entry is not updated. This causes the mirror to be out-of-sync with upstream.For example:
ExtV0.0.1
andExtV0.0.2
. Then thelast_udpated_date
will be the published date ofExtV0.0.2
.ExtV0.0.1
is deleted, but the last updated time is not changed.This issue causes the mirror to throw an error when its trying to remove some out-of-date extensions.
The text was updated successfully, but these errors were encountered: