summary refs log tree commit diff
path: root/latest/development
diff options
context:
space:
mode:
Diffstat (limited to 'latest/development')
-rw-r--r--latest/development/contributing_guide.html2
-rw-r--r--latest/development/synapse_architecture/faster_joins.html2
2 files changed, 2 insertions, 2 deletions
diff --git a/latest/development/contributing_guide.html b/latest/development/contributing_guide.html

index b328bba158..1bf8403da6 100644 --- a/latest/development/contributing_guide.html +++ b/latest/development/contributing_guide.html
@@ -317,7 +317,7 @@ useful to reproduce this locally.</p> <h4 id="using-docker"><a class="header" href="#using-docker">Using Docker</a></h4> <p>The easiest way to do so is to run Postgres via a docker container. In one terminal:</p> -<pre><code class="language-shell">docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgress -p 5432:5432 postgres:14 +<pre><code class="language-shell">docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgres -p 5432:5432 postgres:14 </code></pre> <p>If you see an error like</p> <pre><code>docker: Error response from daemon: driver failed programming external connectivity on endpoint nice_ride (b57bbe2e251b70015518d00c9981e8cb8346b5c785250341a6c53e3c899875f1): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use. diff --git a/latest/development/synapse_architecture/faster_joins.html b/latest/development/synapse_architecture/faster_joins.html
index d60c159d11..dcb761384f 100644 --- a/latest/development/synapse_architecture/faster_joins.html +++ b/latest/development/synapse_architecture/faster_joins.html
@@ -382,7 +382,7 @@ But don't want to send out sensitive data in other HS's events in this way.</p> <p>Suppose we discover after resync that we shouldn't have sent out one our events (not a prev_event) to a target HS. Not much we can do. What about if we didn't send them an event but shouldn't've? E.g. what if someone joined from a new HS shortly after you did? We wouldn't talk to them. -Could imagine sending out the &quot;Missed&quot; events after the resync but... painful to work out what they shuld have seen if they joined/left. +Could imagine sending out the &quot;Missed&quot; events after the resync but... painful to work out what they should have seen if they joined/left. Instead, just send them the latest event (if they're still in the room after resync) and let them backfill.(?)</p> <ul> <li>Don't do this currently.</li>