-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spelling #31
Spelling #31
Changes from all commits
4a61dbf
44b55fe
2ceb277
0d7395b
8f470b3
ab58fe2
b499f42
0043494
305d12a
de9870b
289f51c
c17a818
b3f26c7
7f5625d
4cedfcc
b9268f6
e54d6a0
2ffd32c
76df6c0
9fa8c48
1edf4c2
88e4076
474ab3e
f801df5
0c1123d
eff2855
4046934
c9565c7
823ac35
93f391e
c2c67f1
8e35902
3338249
5601cbd
39460a6
f1877dc
7393887
51be994
911ee81
79d2972
55692cc
abc996b
6759e9b
1306d02
3823170
6c581d5
5fcd280
c0dca7d
5074cca
837873b
302d2f1
d94a886
71c3cf6
256de31
1da3abf
8b14d09
e5d6d33
7684741
310fcef
ffaf979
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,7 +29,7 @@ | |
<!-- Every session runs within a dedicated process. | ||
|
||
This mode guarantees kernel-level session privacy, but as every | ||
session requires a seperate process, it is also an easy target | ||
session requires a separate process, it is also an easy target | ||
for DoS attacks if not shielded by access control. | ||
|
||
It is also a convenient mode during development, as it is easy | ||
|
@@ -56,7 +56,7 @@ | |
session will kill all of the sessions in the same process. You | ||
should debug extensively using valgrind. Also, it is your | ||
responsibility to keep session state not interfering and | ||
seperated. | ||
separated. | ||
|
||
On the other hand, sessions are inexpensive, and this mode | ||
suffers far less from DoS attacks than dedicated-process mode. | ||
|
@@ -116,7 +116,7 @@ | |
will be started for every shared process, or for every session | ||
which has ?debug appended to the command line. | ||
|
||
The variable is slighly misnamed. Not only a path can be set, | ||
The variable is slightly misnamed. Not only a path can be set, | ||
but also options, like for example: | ||
|
||
/usr/bin/valgrind - -leak-check=full | ||
|
@@ -135,7 +135,7 @@ | |
want to change this value if you would like to support | ||
reentrant event loops, where you block one event loop | ||
using WDialog::exec() or related static | ||
methods. Everytime you enter such an event loop, one | ||
methods. Every time you enter such an event loop, one | ||
thread is blocked, and therefore the total number of | ||
sessions that reliably can do this is limited to the | ||
number of thread you have (minus one to unblock). | ||
|
@@ -169,7 +169,7 @@ | |
You may want to change this value if you would like to | ||
support more reentrant event loops, where you block one | ||
event loop using WDialog::exec() or related static | ||
methods. Everytime you enter such an event loop, one | ||
methods. Every time you enter such an event loop, one | ||
thread is blocked, and therefore the total number of | ||
sessions that reliably can do this is limited to the | ||
number of thread you have (minus one to unblock). | ||
|
@@ -207,7 +207,7 @@ | |
<max-memory-request-size>1024</max-memory-request-size> | ||
</connector-isapi> | ||
|
||
<!-- Javascript debug options | ||
<!-- JavaScript debug options | ||
|
||
Values: | ||
- true: JavaScript errors are not caught but the browser | ||
|
@@ -281,7 +281,7 @@ | |
how quickly they are generated. | ||
|
||
In rare cases, the scheme may result in unwanted behaviour, | ||
because the client-side is allowed to be slighly out of | ||
because the client-side is allowed to be slightly out of | ||
sync at the time an event is recorded with the server-side | ||
(and more so on high-latency links). The drastic | ||
alternative is to discard events while a response is | ||
|
@@ -336,7 +336,7 @@ | |
|
||
<!-- Whether inline CSS is allowed. | ||
|
||
Some Wt widgets will insert CSS rules in the the inline | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Duplicate words aren't technically misspellings, but spell-checking tools have flagged them for ages, so... |
||
Some Wt widgets will insert CSS rules in the inline | ||
stylesheet when first used. This can be disabled using this | ||
configuration option. | ||
|
||
|
@@ -445,7 +445,7 @@ | |
|
||
<!-- resourcesURL property | ||
|
||
The URL at which the resources/ folder is deploeyd that | ||
The URL at which the resources/ folder is deployed that | ||
comes distributed with Wt and contains auxiliary files | ||
used to primarily for styles and themes. | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -119,7 +119,7 @@ std::pair<QStringList, int> K8sHelper::listNamespaces(void) | |
} | ||
} | ||
|
||
// make request and conncet to the processing handlers | ||
// make request and connect to the processing handlers | ||
QNetworkReply* reply = QNetworkAccessManager::get(req); | ||
connect(reply, SIGNAL(finished()), &m_eventLoop, SLOT(quit())); | ||
connect(reply, SIGNAL(error(QNetworkReply::NetworkError)), this, SLOT(exitEventLoop(QNetworkReply::NetworkError))); | ||
|
@@ -162,7 +162,7 @@ std::pair<QByteArray, int> K8sHelper::requestNamespacedItemsData(const QString& | |
} | ||
} | ||
|
||
// make request and conncet to the processing handlers | ||
// make request and connect to the processing handlers | ||
QNetworkReply* reply = QNetworkAccessManager::get(req); | ||
connect(reply, SIGNAL(finished()), &m_eventLoop, SLOT(quit())); | ||
connect(reply, SIGNAL(error(QNetworkReply::NetworkError)), this, SLOT(exitEventLoop(QNetworkReply::NetworkError))); | ||
|
@@ -212,7 +212,7 @@ std::pair<QStringList, int> K8sHelper::parseNamespaces(const QByteArray& data) | |
|
||
|
||
std::pair<QString, int> K8sHelper::parseNamespacedServices(const QByteArray& in_data, | ||
const QString& in_macthNamespace, | ||
const QString& in_matchNamespace, | ||
QMap<QString, QMap<QString, QString>>& out_selectorMaps, | ||
NodeListT& out_bpnodes) | ||
{ | ||
|
@@ -237,8 +237,8 @@ std::pair<QString, int> K8sHelper::parseNamespacedServices(const QByteArray& in_ | |
auto&& metaData = serviceData["metadata"].toObject(); | ||
auto&& k8sNamespace = metaData["namespace"].toString(); | ||
|
||
// escape service if not matches the given namespac | ||
if (k8sNamespace != in_macthNamespace) { | ||
// escape service if not matches the given namespace | ||
if (k8sNamespace != in_matchNamespace) { | ||
continue; | ||
} | ||
|
||
|
@@ -450,7 +450,7 @@ std::tuple<int, std::string, std::string> K8sHelper::extractStateInfo(const QJs | |
|
||
// default state is "waiting" | ||
// See Kubernetes documentation: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#containerstate-v1-core | ||
return std::make_tuple(ngrt4n::K8sPending, "", QObject::tr("container is wating").toStdString()); | ||
return std::make_tuple(ngrt4n::K8sPending, "", QObject::tr("container is waiting").toStdString()); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This probably breaks translations. There is an There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I'll update the fr translation. |
||
} | ||
|
||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -82,7 +82,7 @@ const IconMapT NodeIcons = { | |
{"Database Server", "images/db-server.png"}, | ||
{"Process", "images/process.png"}, | ||
{"Logfile", "images/log.png"}, | ||
{"Network Bandwith", "images/network-usage.png"}, | ||
{"Network Bandwidth", "images/network-usage.png"}, | ||
{"CPU", "images/cpu.png"}, | ||
{"CPU Load", "images/performance-level.png"}, | ||
{"Memory", "images/memory.png"}, | ||
|
@@ -164,7 +164,7 @@ bool findNode(const NodeListT &nodes, const QString &nodeId, NodeListT::const_it | |
|
||
void setCheckOnError(int status, const QString &msg, CheckT &invalidCheck); | ||
|
||
StringPairT splitDataPointInfo(const QString &info); /* return <[sourcei:]hostaddr, checkid> */ | ||
StringPairT splitDataPointInfo(const QString &info); /* return <[source:]hostaddr, checkid> */ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ?? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a comment for code readability, I think the index of the source is relevant? |
||
|
||
StringPairT splitSourceDataPointInfo(const QString &info); /* return <source, hostaddr> */ | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
brand (matches below...)