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

Fix conflicts from integration-1.2 to main #353

Merged

Conversation

sacOO7
Copy link
Collaborator

@sacOO7 sacOO7 commented Jul 8, 2021

No description provided.

tcard and others added 3 commits June 3, 2021 12:21
Don't reuse IV between encryptions
# Conflicts:
#	ably/proto/crypto_test.go
#	ably/proto_crypto.go
@sacOO7 sacOO7 requested review from lmars and tcard July 8, 2021 13:44
ably/proto_crypto.go Outdated Show resolved Hide resolved
@lmars
Copy link
Member

lmars commented Jul 8, 2021

I'm struggling to understand what conflict this is resolving, can you clarify?

@sacOO7
Copy link
Collaborator Author

sacOO7 commented Jul 8, 2021

I'm struggling to understand what conflict this is resolving, can you clarify?

Some files changes, deleted and new code added. You can check actual conflicts on active integration-1.2 to main PR

@lmars
Copy link
Member

lmars commented Jul 8, 2021

Some files changes, deleted and new code added. You can check actual conflicts on active integration-1.2 to main PR

Ok, I still don't understand what it's conflicting with, so I'll defer to @tcard.

@lmars lmars removed their request for review July 8, 2021 17:08
@QuintinWillison
Copy link
Contributor

I'm slightly worried that checks failed on this branch, but we need to get the 1.2 integration branch ready to land so I'll land this PR there now so we can assess its impact on resolving the conflicts with main.

@QuintinWillison QuintinWillison merged commit 4d1f24e into integration/1.2 Jul 8, 2021
@QuintinWillison QuintinWillison deleted the fix/conflict-crypto-integration-1.2 branch July 8, 2021 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants