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

Report information about the bot itself #135

Open
AlexDaniel opened this issue Apr 25, 2017 · 2 comments
Open

Report information about the bot itself #135

AlexDaniel opened this issue Apr 25, 2017 · 2 comments
Labels
testneeded Issue is generally resolved but tests were not written yet whateverable Issues affecting the bot framework (and therefore all of the bots)

Comments

@AlexDaniel
Copy link
Member

It would be nice to have some universal command for all bots that would give information like:

  • What rakudo version this bot is running on
  • Uptime?
  • Memory usage?

What would be the best name for the command? status? info? what's up?
@AlexDaniel AlexDaniel added the whateverable Issues affecting the bot framework (and therefore all of the bots) label Apr 25, 2017
AlexDaniel added a commit that referenced this issue May 13, 2017
@AlexDaniel
Add uptime command
b2bd371 
One step towards resolving issue #135
@AlexDaniel
Copy link
Member Author

So we have uptime command now, what else do we need? We also have dc4ac48 which implemented gists that include the output of git diff HEAD.

@AlexDaniel
Copy link
Member Author

I don't think there were any requests for more info to be printed. Here's what it says now:

<AlexDaniel> unicodable6: uptime
<unicodable6> AlexDaniel, 1 week, 1 day, 23 hours, 29 minutes, and 38 seconds, 469.183594MiB maxrss. This is Rakudo version 2018.04.1-118-g2f4b2f428 built on MoarVM version 2018.04.1-121-gd634d24cf implementing Perl 6.c.

I think we simply need a test for uptime. It should go somewhere around here (so that all bots are tested).

@AlexDaniel AlexDaniel added the testneeded Issue is generally resolved but tests were not written yet label Jun 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
testneeded Issue is generally resolved but tests were not written yet whateverable Issues affecting the bot framework (and therefore all of the bots)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlexDaniel