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.

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

Jump to bottom

Having too many chat commands will break them all #310

Closed
Cyberboss opened this issue Nov 4, 2017 · 0 comments
Closed

Having too many chat commands will break them all #310

Cyberboss opened this issue Nov 4, 2017 · 0 comments
Labels
Bug Something's fucky Laid to Rest We honestly don't plan to fix this issue but it still represents an active problem with the software V3 Things labelled with this probably won't be fixed ever in suite version 3

Comments

@Cyberboss
Copy link
Member

Cyberboss commented Nov 4, 2017 •
edited
Loading

Since it'll hit the 65535 byte topic limit. Proper way to do it is to have the DMAPI calculate how many commands it can fit into one Topic call, how many calls are required to read them all, and paginate them.
@Cyberboss Cyberboss added the Bug Something's fucky label Nov 4, 2017
@Cyberboss Cyberboss added the Backlog Issue to be scheduled for addressing label Nov 12, 2017
@Cyberboss Cyberboss added the V3 Things labelled with this probably won't be fixed ever in suite version 3 label Aug 29, 2018
@Cyberboss Cyberboss added Laid to Rest We honestly don't plan to fix this issue but it still represents an active problem with the software and removed Backlog Issue to be scheduled for addressing labels Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Something's fucky Laid to Rest We honestly don't plan to fix this issue but it still represents an active problem with the software V3 Things labelled with this probably won't be fixed ever in suite version 3
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Cyberboss