Skip to content
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

Investigate Matrix 1.0 / Synapse 0.99, 1.0 changes #3387

Closed
ulope opened this issue Feb 2, 2019 · 1 comment · Fixed by #4646
Closed

Investigate Matrix 1.0 / Synapse 0.99, 1.0 changes #3387

ulope opened this issue Feb 2, 2019 · 1 comment · Fixed by #4646
Labels
Component / Transport Transport related issues State / Investigating For issues that are currently being looked into before labeling further State / Meta Meta issue, must be split into smaller issues

Comments

@ulope
Copy link
Collaborator

ulope commented Feb 2, 2019

Problem Definition

As announced during FOSDEM 2019, Matrix has released v1.0 of their spec and also v0.99 of the Synapse homeserver (v1.0 planned for March).

Most notable changes:

  • No more self-signed certificates for S-S federation traffic, everything is Letsencrypt now
  • Rooms "version 3", room ids will change to a base64 encoded content hash

We need to investigate what impact (if any) those changes will have on our use of Matrix:

  • Certificates for local federation used for tests
  • Possible changes in room discovery due to room ID change
  • ???
  • Once the switch has been made the psycopg2 pinning in requirements/requirements-dev.in should be removed.
@ulope ulope added Component / Transport Transport related issues State / Investigating For issues that are currently being looked into before labeling further State / Meta Meta issue, must be split into smaller issues labels Feb 2, 2019
@ulope ulope added the P2 label Feb 18, 2019
@konradkonrad
Copy link
Contributor

I have a couple flaky tests in an unrelated PR since after the upgrade to 0.99:

ulope added a commit to ulope/raiden that referenced this issue Aug 19, 2019
(Not mergable currently because of raiden-network#4634. Temporarily uses the base64
solution mentioned in the issue.)

This updates our testing dependency to matrix-synapse 1.2.1.

The Synapse config files generated by the integration tests have been
updated to align with new / changed options.

Additionally this no longer uses local TLS certificates speeding up
tests.

Fixes: raiden-network#3387
Required for: raiden-network#4292
ulope added a commit to ulope/raiden that referenced this issue Sep 30, 2019
(Not mergable currently because of raiden-network#4634. Temporarily uses the base64
solution mentioned in the issue.)

This updates our testing dependency to matrix-synapse 1.2.1.

The Synapse config files generated by the integration tests have been
updated to align with new / changed options.

Additionally this no longer uses local TLS certificates speeding up
tests.

Fixes: raiden-network#3387
Required for: raiden-network#4292
LefterisJP pushed a commit that referenced this issue Oct 1, 2019
(Not mergable currently because of #4634. Temporarily uses the base64
solution mentioned in the issue.)

This updates our testing dependency to matrix-synapse 1.2.1.

The Synapse config files generated by the integration tests have been
updated to align with new / changed options.

Additionally this no longer uses local TLS certificates speeding up
tests.

Fixes: #3387
Required for: #4292
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component / Transport Transport related issues State / Investigating For issues that are currently being looked into before labeling further State / Meta Meta issue, must be split into smaller issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants