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

[Push] Sync subscriptions #915

Merged
merged 6 commits into from
Jun 29, 2023
Merged

[Push] Sync subscriptions #915

merged 6 commits into from
Jun 29, 2023

Conversation

flypaper0
Copy link
Contributor

Description

Resolves # (issue)

How Has This Been Tested?

Due Dilligence

  • Breaking change
  • Requires a documentation update

@flypaper0 flypaper0 temporarily deployed to internal June 16, 2023 12:20 — with GitHub Actions Inactive
Copy link
Contributor

@llbartekll llbartekll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking a look at it so fast 🙏
I understand that this adds sync store for threads but we also need to sync thread keys
and do the same for messages, correct?

@flypaper0 flypaper0 temporarily deployed to internal June 19, 2023 12:37 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 20, 2023 11:15 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 20, 2023 11:38 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 20, 2023 17:14 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 21, 2023 07:40 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 21, 2023 13:28 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 22, 2023 12:17 — with GitHub Actions Inactive
@flypaper0
Copy link
Contributor Author

I understand that this adds sync store for threads but we also need to sync thread keys

yes, we're discussing keys sync here: https://github.com/WalletConnect/walletconnect-docs/pull/773/files

@flypaper0 flypaper0 marked this pull request as ready for review June 22, 2023 13:22
@flypaper0 flypaper0 temporarily deployed to internal June 23, 2023 12:46 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 23, 2023 13:18 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 26, 2023 13:52 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 26, 2023 14:31 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 27, 2023 16:18 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 28, 2023 14:24 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 28, 2023 14:55 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 28, 2023 15:28 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 29, 2023 07:49 — with GitHub Actions Inactive
@flypaper0 flypaper0 temporarily deployed to internal June 29, 2023 08:12 — with GitHub Actions Inactive
@@ -21,10 +23,19 @@ final class PushTests: XCTestCase {

var pairingStorage: PairingStorage!

let pk = try! EthereumPrivateKey()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sometimes we re running those tests against prod cast and prod gm dapp. Can we use some fixed entropy here for deriving the private key? to not pollute their DBs

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why we can pollute db's? I think there will be same amount of relay messages in both cases (random and derived private key)

@flypaper0 flypaper0 merged commit e98a05f into develop Jun 29, 2023
8 checks passed
@flypaper0 flypaper0 deleted the feature/sync-subscriptions branch June 29, 2023 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants