so-close-vote-reviewers/socvr-slack-statbot

Searches through the transcript for a given day and reports back the slack room.

socvr-slack-statbot's Issues

Have the program stop on a Sigterm command from linux

When docker wants to stop a container its sends a SIGTERM command to the root process in the container. If the container does not exit within 10 seconds it will send a SIGKILL to the container's kernel.

Right now the program can catch Control+c, or SIGINT. This is the "polite" way to stop a program, but won't cut it for docker. I'd like to have the bot exit cleanly.

So far the closest I've gotten is this SO post and this source code file, but I can't get it to compile nor can I effectively debug it.

Add a Stop Command

used as a just-in-case, there should be a "stop bot" command. This will shut down the program and the hosting docker container.

Scrape through other chat rooms for additional messages

Messages are moved to other rooms, like the CV graveyard. We need to search through that room as well to get the complete list of CV requests and other stats.

I will need some help on this, mostly about "how do I get moved messages from a particular day."

Add actual error handling

If you type in some garbage values the bot will break.

And by "break", I mean shuts down.

We need to add some actual error handling. The bot should always try to output to slack, and always try to remain running.

Help finish up the ParseMessage method

So I need your help @ArcticEcho:

I've been doing a lot of re-working on the reorg branch.

What I need help with is the ParseMessage method in ChatScraper. There are other methods in the class which you can ignore (unless they are being used by the ParseMessage method).

This is the workflow of the method:

1. Pass in the messageId and roomId you would like to get information about
2. The method downloads the html for the message's history page.
3. The method parses through all the information and saves it to a ParsedMessageData object, which it then returns when done.

I've got about half of the work done, but you're the better html parser so if you can help me clean it up that would be awesome. The only thing you should need to write is within the ParseMessage method.

I've set up unit tests for all the return values. Make sure you have the Nunit3 test runner installed as a VS extension and you'll be able to run the unit tests. Once all the tests turn green then we're done (except for revisions).

I'll be in chat tomorrow if you've got questions.