aboutsummaryrefslogtreecommitdiff
path: root/package.json
diff options
context:
space:
mode:
author0neGal <mail@0negal.com>2024-01-29 17:45:17 +0100
committer0neGal <mail@0negal.com>2024-01-29 17:45:17 +0100
commit66afc000c07d8cf30caaff4439b57d1bd1a4b386 (patch)
tree922ebb8dad31e42388d6f74a56f6c4c3a59f01c5 /package.json
parent6de175f28f3cc818333db10fe164ec9a8b24e8d5 (diff)
downloadViper-66afc000c07d8cf30caaff4439b57d1bd1a4b386.tar.gz
Viper-66afc000c07d8cf30caaff4439b57d1bd1a4b386.zip
prevent multiple updates running simultaneously
We're the renderer to request for an update multiple times, then it'd simply start both updates, at the same time, causing all kinds of issues. This was only really realistically possible to happen if you were to manually check for updates whilst an update automatically were to be checked from right before then. As an example, when Viper starts up, it'll by default check for updates for itself, then Northstar, if you within that time frame checked for updates manually, it'll run both. Now however, we check if an existing update is occurring, and do nothing if so, this is both for Viper and Northstar updates.
Diffstat (limited to 'package.json')
0 files changed, 0 insertions, 0 deletions