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

Allow to configure if pushkey should be converted to hex before sending to APNs #344

Merged
merged 6 commits into from
Nov 30, 2023

Conversation

danbim
Copy link
Contributor

@danbim danbim commented Aug 17, 2023

I ran into the same problem as #301 and decided to instead make this configurable in Sygnal. Not sure if this is the right approach, happy for feedback and adopting to something else :)

Signed-off-by: Daniel Bimschas [email protected] / [email protected]

@danbim danbim requested a review from a team as a code owner August 17, 2023 11:30
Copy link
Contributor

@reivilibre reivilibre left a comment

Choose a reason for hiding this comment

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

Happy with the idea of the change but just the option seems to be called the opposite of what it should be, if it's me being stupid then do say :)

sygnal.yaml.sample Outdated Show resolved Hide resolved
@clokep clokep requested a review from a team November 27, 2023 21:20
sygnal/apnspushkin.py Outdated Show resolved Hide resolved
clokep
clokep previously approved these changes Nov 30, 2023
@clokep
Copy link
Member

clokep commented Nov 30, 2023

Would you mind adding a newsfile?

changelog.d/344.feature Outdated Show resolved Hide resolved
@clokep
Copy link
Member

clokep commented Nov 30, 2023

@danbim Ah, sorry can you sign-off on your changes? Should be good to go if CI passes! 🎉

@danbim
Copy link
Contributor Author

danbim commented Nov 30, 2023

@clokep Haven't used this mechanism before. Should I rewrite history for this or is adding an empty commit with sign off sufficient?

@clokep
Copy link
Member

clokep commented Nov 30, 2023

@clokep Haven't used this mechanism before. Should I rewrite history for this or is adding an empty commit with sign off sufficient?

The easiest thing is usually to edit the PR description and manually add the text. Adding an empty commit to the PR is fine too.

@danbim
Copy link
Contributor Author

danbim commented Nov 30, 2023

@clokep Haven't used this mechanism before. Should I rewrite history for this or is adding an empty commit with sign off sufficient?

The easiest thing is usually to edit the PR description and manually add the text. Adding an empty commit to the PR is fine too.

Done. Added my private email as the commits were accidentally signed with my old employers email address 🙈

@clokep clokep merged commit e2eaa5c into matrix-org:main Nov 30, 2023
5 checks passed
@clokep
Copy link
Member

clokep commented Nov 30, 2023

Thank you!

@danbim danbim deleted the v0.12.0_pushkey_fix branch November 30, 2023 16:21
@danbim
Copy link
Contributor Author

danbim commented Dec 8, 2023

@clokep Out of egoistic personal interest to remove my patched fork to simplify my deployment: any plans when to have a new release including this MR? :)

@clokep
Copy link
Member

clokep commented Dec 8, 2023

Will need to ask @matrix-org/synapse-core id they have another release planned soon.

@danbim
Copy link
Contributor Author

danbim commented Jan 24, 2024

@clokep Do you maybe have any update on the question of a release? I have seen this project might move to element-hq due to the license change but so far I can't find it there. Cheers!

@clokep
Copy link
Member

clokep commented Jan 24, 2024

@danbim You'll need to ask the current team -- maybe @erikjohnston or @reivilibre would know.

@Half-Shot
Copy link
Contributor

This appears to have now happened -> https://github.com/matrix-org/sygnal/releases/tag/v0.14.0

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.

4 participants