Skip to content

Issues: turt2live/synapse-netcore-workers

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.

Sign up for GitHub

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

25 Open 14 Closed
25 Open 14 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Upgrade to dotnet 3.0
#60 opened Oct 13, 2019 by soyflourbread
Federation sender ended up using 6.8G of memory
#59 opened Aug 28, 2019 by Half-Shot
Mention currently supported synapse version in the README.md docs Stuff that needs to be documented
#51 opened Apr 1, 2019 by Half-Shot
Document common setup instructions for reverse proxying docs Stuff that needs to be documented
#50 opened Apr 1, 2019 by Half-Shot
We don't link to synapse in the README docs Stuff that needs to be documented
#49 opened Mar 27, 2019 by Half-Shot
The specified value is not a valid 'Host' header string bug Something isn't working p1 Should be worked on before p2 stuff worker:fed_sender Issues relating to the federation sender
#39 opened Mar 11, 2019 by Half-Shot
Add example grafana dashboard docs Stuff that needs to be documented enhancement New feature or request p2 Should be worked on before p3 stuff
#37 opened Mar 5, 2019 by Half-Shot
What do we do with federation transactions that never succeed? p3 Community help recommended question Further information is requested worker:fed_sender Issues relating to the federation sender
#36 opened Mar 5, 2019 by Half-Shot
There is a low amount of federation transactions that do not sign correctly. bug Something isn't working help wanted Extra attention is needed p1 Should be worked on before p2 stuff worker:fed_sender Issues relating to the federation sender
#35 opened Mar 5, 2019 by Half-Shot
1
DNS isn't rate limited bug Something isn't working p1 Should be worked on before p2 stuff worker:fed_sender Issues relating to the federation sender
#34 opened Mar 5, 2019 by Half-Shot
We waste time sending federation traffic to dead hosts bug Something isn't working p2 Should be worked on before p3 stuff worker:fed_sender Issues relating to the federation sender
#33 opened Mar 5, 2019 by Half-Shot
Federation Sender should check room membership at the time of the event, rather than the current membership enhancement New feature or request p1 Should be worked on before p2 stuff worker:fed_sender Issues relating to the federation sender
#32 opened Mar 5, 2019 by Half-Shot
1
MSC1309: Authorization component:appsvc_mgmt Relates to appservice management enhancement New feature or request p1 Should be worked on before p2 stuff worker:appsvc_sender Issues relating to the appservice sender
#31 opened Mar 4, 2019 by turt2live
MSC1309: List and get information about rooms component:appsvc_mgmt Relates to appservice management enhancement New feature or request p2 Should be worked on before p3 stuff worker:appsvc_sender Issues relating to the appservice sender
#30 opened Mar 4, 2019 by turt2live
MSC1309: List users component:appsvc_mgmt Relates to appservice management enhancement New feature or request p2 Should be worked on before p3 stuff worker:appsvc_sender Issues relating to the appservice sender
#29 opened Mar 4, 2019 by turt2live
MSC1309: Delete appservice component:appsvc_mgmt Relates to appservice management enhancement New feature or request p2 Should be worked on before p3 stuff worker:appsvc_sender Issues relating to the appservice sender
#28 opened Mar 4, 2019 by turt2live
Restore and persist appservice sender stream position instead of relying on zero downtime enhancement New feature or request p1 Should be worked on before p2 stuff worker:appsvc_sender Issues relating to the appservice sender
#27 opened Mar 4, 2019 by turt2live
Persist appservice transactions enhancement New feature or request p1 Should be worked on before p2 stuff worker:appsvc_sender Issues relating to the appservice sender
#26 opened Mar 4, 2019 by turt2live
Smarter room checks for appservice interests enhancement New feature or request p2 Should be worked on before p3 stuff worker:appsvc_sender Issues relating to the appservice sender
#25 opened Mar 4, 2019 by turt2live
Check if any member of the room is interesting to the appservice enhancement New feature or request p1 Should be worked on before p2 stuff worker:appsvc_sender Issues relating to the appservice sender
#24 opened Mar 4, 2019 by turt2live
Update appservice management when appservices change enhancement New feature or request p1 Should be worked on before p2 stuff worker:appsvc_sender Issues relating to the appservice sender
#23 opened Mar 4, 2019 by turt2live
Fall back to legacy routes upon send failure enhancement New feature or request p1 Should be worked on before p2 stuff worker:appsvc_sender Issues relating to the appservice sender
#22 opened Mar 4, 2019 by turt2live
Federation sender can send transactions to wrong hosts bug Something isn't working p1 Should be worked on before p2 stuff worker:fed_sender Issues relating to the federation sender
#21 opened Mar 3, 2019 by Half-Shot
SRV load balancing / failover enhancement New feature or request p3 Community help recommended worker:fed_sender Issues relating to the federation sender
#19 opened Mar 3, 2019 by Half-Shot
Support IPv6 for Replication component:replication Relates to replication with Synapse enhancement New feature or request help wanted Extra attention is needed p3 Community help recommended
#14 opened Mar 2, 2019 by Half-Shot
ProTip! Find all open issues with in progress development work with linked:pr.