Skip to content

Commit f89582a

Browse files
committed
Fix spellcheck
1 parent 37b264c commit f89582a

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

gpt4all-updater/README

+2-2
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ There are two modes, offline and online, each is tested differently:
1111

1212
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.
1313

14-
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.
14+
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.
1515

1616
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.
1717

18-
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.
18+
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.
1919
This is provided via the cmake command line argument `-DGPT4ALL_MANIFEST_ENDPOINT=<url>`.
2020

2121
Now configure and build the updater with CMake.

gpt4all-updater/src/Download.cxx.in

+2-2
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ void Download::installInstaller(QString &expected, QFile *temp, QNetworkReply *i
6969
this->downloadPath = new QFile(saveFilePath);
7070
#endif
7171
temp->deleteLater();
72-
// Extraction is not requried on Windows because we download an exe directly
72+
// Extraction is not required on Windows because we download an exe directly
7373
gpt4all::state::Gpt4AllState::getInstance().setInstaller(this->downloadPath);
7474
}
7575

@@ -84,7 +84,7 @@ QNetworkReply * Download::downloadInMemory(QUrl &url)
8484
return nullptr;
8585
}
8686
if (reply->error() != QNetworkReply::NoError) {
87-
qWarning() << "Error: network error occured while downloading the release manifest:" << reply->errorString();
87+
qWarning() << "Error: network error occurred while downloading the release manifest:" << reply->errorString();
8888
reply->deleteLater();
8989
}
9090
return reply;

0 commit comments

Comments
 (0)