[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: fix typo: s/ingres/ingress/
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: fix typo: s/ingres/ingress/ |
Date: |
Tue, 05 Jan 2021 22:40:19 +0100 |
This is an automated email from the git hooks/post-receive script.
ttn pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new 275de89 fix typo: s/ingres/ingress/
275de89 is described below
commit 275de898eeff924b0658adbbc3cd51cadcd749d6
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Tue Jan 5 16:36:05 2021 -0500
fix typo: s/ingres/ingress/
---
design-documents/011-auditor-db-sync.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/design-documents/011-auditor-db-sync.rst
b/design-documents/011-auditor-db-sync.rst
index 505f7b4..f4befdf 100644
--- a/design-documents/011-auditor-db-sync.rst
+++ b/design-documents/011-auditor-db-sync.rst
@@ -131,7 +131,7 @@ Drawbacks
is the answer, to be investigated what performs better.
* A malicious exchange could theoretically send expensive transactions
to the auditor via the replication mechanism (possibly ones that
- it did not even execute locally itself) to DoS the "ingres"
+ it did not even execute locally itself) to DoS the "ingress"
database. This would be noticed primarily by load
monitoring or even the auditor lagging unusually far behind the
exchange's transaction history. We believe this is acceptable,
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: fix typo: s/ingres/ingress/,
gnunet <=