From f89582a939a08d4ba9d31a09199c59ea6692c076 Mon Sep 17 00:00:00 2001 From: John Parent Date: Tue, 22 Oct 2024 16:00:17 -0400 Subject: [PATCH] Fix spellcheck --- gpt4all-updater/README | 4 ++-- gpt4all-updater/src/Download.cxx.in | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/gpt4all-updater/README b/gpt4all-updater/README index dd845cf08ebb..e017b472c89b 100644 --- a/gpt4all-updater/README +++ b/gpt4all-updater/README @@ -11,11 +11,11 @@ There are two modes, offline and online, each is tested differently: The online updater workflow takes a url endpoint (for early testing, this will be a file url) that points to a manifest file, a sample of which has been provided under the `tmp` directory relative to this README. The manifest file includes, amount other things specified in the updater RFC, another file URL to a gpt4all installer. -The first thing testing this will require is a manual update of that file url in the mainfest xml file to point to the DMG on MacOS or exe on Windows, of an existing online Gpt4All installer, as well as a corresponding sha256 sum of the given installer. The manifest is filled with other stub info for testing, you're welcome to leave it as is or fill it out correctly for each testing iteration. +The first thing testing this will require is a manual update of that file url in the manifest xml file to point to the DMG on MacOS or exe on Windows, of an existing online Gpt4All installer, as well as a corresponding sha256 sum of the given installer. The manifest is filled with other stub info for testing, you're welcome to leave it as is or fill it out correctly for each testing iteration. That is all that is required for configuration. Now simply build this project via CMake, using standard CMake build practices. CMake will build the online installer by default, so no extra arguments are required. -One argument is required for the online installer, the url where the updater should expect the mainfest file to be. This can be any url accessible to your system, but for simplicity and testing reasons, its usually best to use a file url. +One argument is required for the online installer, the url where the updater should expect the manifest file to be. This can be any url accessible to your system, but for simplicity and testing reasons, its usually best to use a file url. This is provided via the cmake command line argument `-DGPT4ALL_MANIFEST_ENDPOINT=`. Now configure and build the updater with CMake. diff --git a/gpt4all-updater/src/Download.cxx.in b/gpt4all-updater/src/Download.cxx.in index 40c1fdea1bac..af29674a376d 100644 --- a/gpt4all-updater/src/Download.cxx.in +++ b/gpt4all-updater/src/Download.cxx.in @@ -69,7 +69,7 @@ void Download::installInstaller(QString &expected, QFile *temp, QNetworkReply *i this->downloadPath = new QFile(saveFilePath); #endif temp->deleteLater(); - // Extraction is not requried on Windows because we download an exe directly + // Extraction is not required on Windows because we download an exe directly gpt4all::state::Gpt4AllState::getInstance().setInstaller(this->downloadPath); } @@ -84,7 +84,7 @@ QNetworkReply * Download::downloadInMemory(QUrl &url) return nullptr; } if (reply->error() != QNetworkReply::NoError) { - qWarning() << "Error: network error occured while downloading the release manifest:" << reply->errorString(); + qWarning() << "Error: network error occurred while downloading the release manifest:" << reply->errorString(); reply->deleteLater(); } return reply;