amthorn / qutex Goto Github PK

Describe the bug
The pun command doesn't work

To Reproduce
Steps to reproduce the behavior:

1. send "pun" to Qutex bot

Expected behavior
A pun should be returned

Additional context
Response from the bot:

TRACE ID: 876f64c1-95ee-4434-9fca-09626b15e8c8
Error: Request failed with status code 503
    at createError (/app/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/app/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/app/node_modules/axios/lib/adapters/http.js:260:11)
    at IncomingMessage.emit (node:events:406:35)
    at endReadableNT (node:internal/streams/readable:1329:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

Creating admins and getting queue length history are erroring

Send users a DM when they are saved as a new record in the DB for the first time for a given project. This must contain a link to the privacy policy and a short description of what data was collected. It also should contain a link to purge their data from the database.

get queue name_of_non_default_queue
add me to name_of_non_default_queue
how long on name_of_non_default_queue
etc...

also possible syntax:
get queue | name_of_non_default_queue
add me | name_of_non_default_queue
how long | name_of_non_default_queue
etc...

For the latter, need to make sure we don't collide with the | debug option

Is your feature request related to a problem? Please describe.
It's not very helpful when commands that error only tell me that the command is invalid. It would be nice to have an error message that can tell me if the command is simply invalid or if the parameter itself is not found. Additionally, it would be nice to see what the closest command match is.

Describe the solution you'd like
A clear and concise description of what you want to happen.
When a command is not found, tell me why? Is it because of the command syntax isn't valid? Or because the parameter itself is bad.

Describe alternatives you've considered
N/A

Additional context
N/A

Describe the bug
An user joined Webex with the name "Pedro" and added himself to the queue. Then, changed the name to "Pedro Cabral" -- at which point that he could no longer remove himself from the queue. Nor can an admin or a super-admin.

However he can add himself a 2nd time to the queue (which cannot be removed either)

To Reproduce
Steps to reproduce the behavior:

1. Create webex space
2. Join with a name
3. Add self to queue
4. change name

Expected behavior
A-minima, it would be expected that an admin/super-admin can remove entries. In this case, that doesn't seem to be the case.

If you want to see "in vivo" then let me know and I can share the space ID over some sort of private communications.

Screenshots
If applicable, add screenshots to help explain your problem.

Debug (please complete the following information):

• Please run any commands that are causing issue with " | debug" on the end. Paste any relevant or helpful information you receive here

Additional context
Add any other context about the problem here.

• new project created
• new user talking with qutex
• project deleted

Add the following statistics:

1. show most active users (Using inQueueCount)
2. show quickest users (using atHeadSeconds)
3. show (average|max|min) (queue depth|flush time) by (hour|day)

I should be able to add items (free form text such as "eggs") alongside people. Similar statistics should be calculable for these items (case insensitive)