From 2a48d0838b46963b134b4351d4da0dd352cbd8bf Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Tue, 26 Sep 2023 16:01:35 +0000 Subject: deploy: 88ba67eb91215a708f321e16559fe3c2c0d0a407 --- latest/development/contributing_guide.html | 2 +- latest/development/synapse_architecture/faster_joins.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'latest/development') 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.

Using Docker

The easiest way to do so is to run Postgres via a docker container. In one terminal:

-
docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgress -p 5432:5432 postgres:14
+
docker run --rm -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_USER=postgres -e POSTGRES_DB=postgres -p 5432:5432 postgres:14
 

 
If you see an error like

 
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.

 
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 "Missed" events after the resync but... painful to work out what they shuld have seen if they joined/left.
+Could imagine sending out the "Missed" 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.(?)

 
    
 
  • Don't do this currently.
    • 
-- 
cgit 1.5.1