What cog is this bug report for?

stattrack

What versions are you running?

           Your Version    Latest version    Up to date?

This Cog 1.7.1 1.7.1 🟢
Bundled Utils 0c6bf04 0c6bf04 🟢
Red 3.4.14 3.4.16 🔴

Describe the bug

Just a small thing. Noticed that when you are using the help command on channels, it shows dnd / online / idle as examples. But they won't work as they are meant for users.

If there's an error, paste it here

That's not a valid graph. See ~help stattrack channels for a list of valid types and some examples.

Also, should be enhancement.. Not a bug. Sorry about that.

Feature request

This is probably the most self-explanatory request there can be. Add NVIDA Status service. https://status.geforcenow.com/

Bug report

Error In:
[p]statusset remove discord #discord-status

Traceback:

Traceback (most recent call last):
  File "/root/redenv/lib/python3.8/site-packages/discord/ext/commands/core.py", line 85, in wrapped
    ret = await coro(*args, **kwargs)
  File "/root/.local/share/Red-DiscordBot/data/cogtesting/cogs/CogManager/cogs/status/status.py", line 509, in statusset_remove
    sr[service].remove(channel.id)
KeyError: 'discord'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/root/redenv/lib/python3.8/site-packages/discord/ext/commands/bot.py", line 902, in invoke
    await ctx.command.invoke(ctx)
  File "/root/redenv/lib/python3.8/site-packages/redbot/core/commands/commands.py", line 832, in invoke
    await super().invoke(ctx)
  File "/root/redenv/lib/python3.8/site-packages/discord/ext/commands/core.py", line 1340, in invoke
    await ctx.invoked_subcommand.invoke(ctx)
  File "/root/redenv/lib/python3.8/site-packages/discord/ext/commands/core.py", line 864, in invoke
    await injected(*ctx.args, **ctx.kwargs)
  File "/root/redenv/lib/python3.8/site-packages/discord/ext/commands/core.py", line 94, in wrapped
    raise CommandInvokeError(exc) from exc
discord.ext.commands.errors.CommandInvokeError: Command raised an exception: KeyError: 'discord'

What cog is this feature request for?

stattrack

Describe the feature request in as much detail as possible

It's awesome you can see the amount of messages in the entire guild. But would it be possible to see it per channel as well? Such as:

[p]stattrack messages timespan [metrics = channel ID(s)]

eg:

[p]stattrack messages all 849473399213916190 818085665265680424 818085665265680424

So you can see the messages per channel, and have a number & channel overview in the metrics to see which channels are doing great and which ones barely have any activity rather than showing the numbers & time alone.

To allow the for an easy way to clear a channel of all status services, the command [p]statusset clear should be added.

What cog is this bug report for?

stattrack

What versions are you running?

           Your Version    Latest version    Up to date?

This Cog 1.8.0 1.8.0 🟢
Bundled Utils 0c6bf04 0c6bf04 🟢
Red 3.4.13 3.4.16 🔴

Describe the bug

I just updated to 1.8.0, and checked the status metrics (all). And I noticed a drop to 0 due to I assume the update / reload of the cog:

Not sure if this is intended as I am not sure if it should use previous data (or skip the missing data on the metrics) before the reload. Making a issue about it just in case.

If there's an error, paste it here

No response

What cog is this feature request for?

CmdLog

Describe the feature request in as much detail as possible

A way to log every command used in a text channel, easy to check, so we don't have to go to the logs to see who used it.

When [p]stattrackinfo is ran before the loop starts, self.last_loop_time is unbound and this causes an exception. This should be gracefully handled.

What cog is this feature request for?

StatTrack

Describe the feature request in as much detail as possible

The group commands status, users and channels should be a single command where the specific metrics wanted are chosen with arguments (after the optional timespan).

Informational - 1.3.0 Release

This release has two minor user-facing changes. However, behind the scenes there's a bit more.

• Field embed limits are now respected
• Scheduled updates will now show when they're scheduled for in a nicer way

Internal:

• All update checking logic has been moved to a new file
• A simpler and not over-engineered method to check if it's a real update has been implemented
• The above means the bot will not attempt to "catch up" on missed updates if they are over 5 minutes old (I may change this value in the future)
• A refactoring of how different feeds are parsed and reversed (Statuspage ones)
• Some object changes to pave the way for further updates

This has resulted in some changes to the events:

• Fields will no longer potentially need reversing, they will be in chronological order

• The UpdateField object has new attributes:

  • group_id, which will be different for each field unless a field has been split to comply with embed limits in which case the split fields will have the same ID
  • time, which is the time of that field's update

• The FeedDict object has a new attribute, actual_update, which is the estimated time the feed was actually updated. This is mainly internal and I don't foresee a use of it for event listeners.

For detailed documentation on new attributes, check out https://vex-cogs.readthedocs.io/en/latest/statusdev.html#custom-objects

Release

I expect this to be released in the next few days, likely over the weekend or potentially next week.

What cog is this feature request for?

Beautify

Describe the feature request in as much detail as possible

Add a per-channel setting to try and automatically beautify JSON. The bot should try to beautify every single message and silently fail if it is not JSON, otherwise post the beautified version.

This is one of my Hacktoberfest issues, which anyone may take without needing to ask me directly, and if not done I will get around to doing them in the coming months.

What cog is this feature request for?

StatTrack and BetterUptime

Describe the feature request in as much detail as possible

Potentially Move to https://plotly.com/python as per Kowlin's inadvertent suggestion.

I feel there was a reason I didn't use it but I don't remember it.

An option for status to send updates in a thread. The behaviour will be that the user will give the master channel and the bot will create a thread from that "master" channel that will be dedicated to that service.

Depending on discord.py's implementation (which I have not looked at), users should be able to choose a thread the same way as a channel if they want to provide one not made by the bot.

Dependant on discord.py's 2.0 release and subsequent release of that into Red.

What cog is this feature request for?

birthdays

Describe the feature request in as much detail as possible

Ability to convert data from Zes cog if possible

What cog is this feature request for?

Birthday

Describe the feature request in as much detail as possible

Would be nice to have a setting for users to add their start of midnight.
So the announcement starts when it's the right time for them instead of UTC or whatever is set by the admin.

birthday set <birthday> [hour] [timezone]
birthday set 9-24 12 AM EST

Or something similar. You get what I mean.

What cog is this bug report for?

caseinsensitive

What versions are you running?

Your Version    Latest version    Up to date?
-------------  --------------  ----------------  -------------
This Cog       1.0.2           1.0.2             🟢
Bundled Utils  ede8ed9         ede8ed9           🟢
Red            3.4.13          3.4.16            🔴

Describe the bug

Caseinsensitive is working lovely on single type commands, but doesn't appear to work on sub-commands. It returns the help command (if applicable) of the main command.

If there's an error, paste it here

No response

Feature request

Self explanatory.

What cog is this bug report for?

AnotherPingCog

What versions are you running?

Version 1.1.6

Describe the bug

Just run [p]ping, and an error will show up.

If there's an error, paste it here

Exception in command 'ping'
Traceback (most recent call last):
  File "C:\Users\Jefferson Jr. Shim\saki\lib\site-packages\discord\ext\commands\core.py", line 85, in wrapped
    ret = await coro(*args, **kwargs)
  File "D:\saki izumo\data\cogs\CogManager\cogs\anotherpingcog\anotherpingcog.py", line 153, in ping
    settings = self.cache
AttributeError: 'AnotherPingCog' object has no attribute 'cache'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:\Users\Jefferson Jr. Shim\saki\lib\site-packages\discord\ext\commands\bot.py", line 939, in invoke
    await ctx.command.invoke(ctx)
  File "C:\Users\Jefferson Jr. Shim\saki\lib\site-packages\discord\ext\commands\core.py", line 863, in invoke
    await injected(*ctx.args, **ctx.kwargs)
  File "C:\Users\Jefferson Jr. Shim\saki\lib\site-packages\discord\ext\commands\core.py", line 94, in wrapped
    raise CommandInvokeError(exc) from exc
discord.ext.commands.errors.CommandInvokeError: Command raised an exception: AttributeError: 'AnotherPingCog' object has no attribute 'cache'

What cog is this bug report for?

Birthday

What versions are you running?

Versions                      
                ╷         ╷         ╷              
                │ Current │ Latest  │ Up to date?  
╶───────────────┼─────────┼─────────┼─────────────╴
  This Cog      │ 1.1.0   │ 1.1.0   │ 🟢           
  Bundled Utils │ 04f5f63 │ 04f5f63 │ 🟢           
  Red           │ 3.4.16  │ 3.4.16  │ 🟢           
                ╵         ╵         ╵

Describe the bug

When running !bday upcoming 365 all birthdays showing in the next year show the age people become this year.

Suggested possible fix would be to check the date to see if the year increments, show the year change in output and increment all ages of that year with the year difference compared to current date year.

Example:

<date>
<person> turns <year>

2022
<date>
<person> turns <year+1>

If there's an error, paste it here

No response

What cog is this feature request for?

StatTrack

Describe the feature request in as much detail as possible

The total loop time (total_time variable in stattrack.py) should also be stored. I guess the best way to go about doing this is to store it in something like self.raw_loop_time at the end of each loop, then write that to the database in the next loop along with the other data. If I remember correctly, no special migration is needed to add a new data point. Make sure to also add a new command.

This is one of my Hacktoberfest issues, which anyone may take without needing to ask me directly, and if not done I will get around to doing them in the coming months.

Status is getting ugly

It was originally made to simply post a new update (in the equivalent of the current all mode) to a specific channel in a guild. It only supported Discord, GitHub and Cloudflare.

It's grown a lot since then, with multiple modes, multiple channels and a lot more services.
And soon (at least as of writing), I'll be releasing a new command for all users: status. This will let anyone see the status of any service (well, service I've coded in) on-demand. Released.

Doing this I've realised how much of a mess this cog is. Yes, I've done a lot to improve it, but there are still some core issues that I think just need a proper rewrite. As this was my first cog, I've learnt a lot since its beginnings so there's a lot to improve if I start from scratch (though I'm happy with how config is used so I'll keep the same config structure).

I'm also mindful that Discord might come out with threads at some point, and I really don't want to add a new mode with the current state of the cog.

So, what next?

Simply put, I want to rewrite the cog as soon as possible. But it might be a while (compared with this cog's pretty fast update cycle atm).

This cog is my biggest project, and I have little idea how long this will take as I've never done anything like it. So, like basically everything in the Red world, it comes when it comes. That's it.

This means significant new features are unlikely until this is done.

I'm also aware that I have put a lot of my time into Status over the last month, so I may take a break which will make this take longer.

Other stuff

The current version is 1.4.3 1.3.2. 1.4.0 is coming out soon with the status command I mentioned earlier.
It is unlikely there will be more micro updates.

2.0.0, what will be the second major version bump (it was in beta as 0.X.X), will contain the rewrite.

I will rewrite the objects that are sent with events so there will be breaking changes in that respect. Other than that there shouldn't be significant changes to external behaviour, though this could change.

Progress can be seen here: https://github.com/Vexed01/Vex-Cogs/projects/3

Breaking event changes

You can see docs for what I expect the events to look like in 2.0.0 here: https://vex-cogs.readthedocs.io/en/status-rewrite/statusdev.html
Note that these are still subject to change and are not final.

Update (4th April)

Significant progress has been made (see above project link), with very little left to do.

I expect to release on Monday or Tuesday, once I have had a chance to test this with real, live incidents. Release may be later, as I would ideally want to wait for two incidents to happen at the same time for one service (*cough* *cough* Cloudflare).

I have also pushed an initial changelog, though nothing on there is final. See [not ready yet]

Feature request

This would add a mode "Edit" that edits the current message of an incident message whenever an update is posted. This would be efficient in channels along side other feeds so it doesn't spam like "All" & "Latest" would.

Some aesthetics, It'd be cool if the color of the embed corresponded with the different types of statuses Discord uses.

Identified = Red
Monitoring = Orange or Yellow
Resolved = Green

What cog is this feature request for?

stattrack

Describe the feature request in as much detail as possible

I love the metrics! But for some metrics, it would be quite useful to show the total amount eg, messages.

To show for example how much messages were made in a specific time period. And or for eg, commands.

What cog is this feature request for?

AnotherPingCog

Describe the feature request in as much detail as possible

There is a lot of code repetition in pingset red, pingset orange and pingset green in anotherpingcog.py. This could be cleaned up and made easier to maintain by adding a function which is called by all three.

This is one of my Hacktoberfest issues, which anyone may take without needing to ask me directly, and if not done I will get around to doing them in the coming months.

What cog is this feature request for?

status

Describe the feature request in as much detail as possible

Hi, can you add Wikimedia (Official, Atlassian StatusPage-hosted) to the preconfigured status list?

Thanks!

What cog is this feature request for?

TimeChannel

Describe the feature request in as much detail as possible

The bot owner should be able to customise how often timechannels update. A minimum of 5 minutes due to rate limits. The default should remain as it is.

This is one of my Hacktoberfest issues, which anyone may take without needing to ask me directly, and if not done I will get around to doing them in the coming months.

What cog is this bug report for?

testing, pls ignore

What versions are you running?

Your Version    Latest version    Up to date?
-------------  --------------  ----------------  -------------
This Cog       2.4.1           2.4.1             🟢
Bundled Utils  55ecc6d         55ecc6d           🟢
Red            3.5.0.dev1      3.4.16            🟢

Describe the bug

idk sorry

If there's an error, paste it here

No response

Bug report

Currently, double updates can sometimes be sent.

To fix this, I will need to revert to the old update checking method whilst partially keeping the current one for its benefits.
This will prevent edge cases where an update is sent twice.

The original method was removed and simplified when multi-incident support was implemented because it required more time and effort to make work with the new system.

Consequently this is a low priority, but it will be done at some point.

Feature request

Add a new global setting to allow owners to change the emojis, and as embed colour is based on emojis also a setting for embed colour.

What cog is this feature request for?
Birthday

Describe the feature request in as much detail as possible
Add the option to change the time zone the cog checks to match the birthday notification timing.
This option would make it so people living East of the UTC time zone point can have the notification at an earlier time than 12 AM UTC.
Example: Central European users that want a notification at 12 AM CET/CEST can set their time zone to CET/CEST with a notification time at 12 AM, where the bot will act at 10 PM UTC or 11 PM UTC the day before.

What cog is this bug report for?

MadTranslate

What versions are you running?

Versions                       
                ╷            ╷         ╷              
                │ Current    │ Latest  │ Up to date?  
╶───────────────┼────────────┼─────────┼─────────────╴
  This Cog      │ 1.0.2      │ 1.0.2   │ 🟢           
  Bundled Utils │ 6a06288    │ a67d909 │ 🔴           
  Red           │ 3.5.0.dev1 │ 3.4.16  │ 🟢           
                ╵            ╵         ╵

Describe the bug

As soon as you try [p]madtranslate I love food, for example, an error occurs.

If there's an error, paste it here

Exception in command 'madtranslate'
Traceback (most recent call last):
  File "/home/ubuntu/redenv/lib/python3.9/site-packages/discord/ext/commands/core.py", line 85, in wrapped
    ret = await coro(*args, **kwargs)
  File "/home/ubuntu/.local/share/Red-DiscordBot/data/vance/cogs/CogManager/cogs/madtranslate/madtranslate.py", line 109, in madtranslate
    q = await get_translation(ctx, session, sl, tl, q)
  File "/home/ubuntu/.local/share/Red-DiscordBot/data/vance/cogs/CogManager/cogs/madtranslate/madtranslate.py", line 48, in get_translation
    return as_json["sentences"][0]["trans"]
TypeError: list indices must be integers or slices, not str

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/ubuntu/redenv/lib/python3.9/site-packages/discord/ext/commands/bot.py", line 939, in invoke
    await ctx.command.invoke(ctx)
  File "/home/ubuntu/redenv/lib/python3.9/site-packages/discord/ext/commands/core.py", line 863, in invoke
    await injected(*ctx.args, **ctx.kwargs)
  File "/home/ubuntu/redenv/lib/python3.9/site-packages/discord/ext/commands/core.py", line 94, in wrapped
    raise CommandInvokeError(exc) from exc
discord.ext.commands.errors.CommandInvokeError: Command raised an exception: TypeError: list indices must be integers or slices, not str

What cog is this feature request for?

WOL

Describe the feature request in as much detail as possible

Add a command to ping the host computer, and respond to the user whether or not it's online.

The best way to do this would probably be through calling a shell command, though if there's a library then that might be nicer.

This is one of my Hacktoberfest issues, which anyone may take without needing to ask me directly, and if not done I will get around to doing them in the coming months.

What cog is this feature request for?

[caseinsensitive]

Describe the feature request in as much detail as possible

Currently caseinsensitive does not support aliases.

This is a feature request for adding aliases support.

For your Status cog, when adding a service to a channel and being prompted with the mode and webhook, when saying yes for the webhook, should the bot automatically create the webhook when the setup is complete or does it only create it when an issue is posted?

The message reads It looks like I didn't find anything for that user.
It should say It looks like I didn't find anything for that server.

The Vex-Cog-Utils library will be removed and copied into each cog, to allow for different cog versions to have their appropriate utils version.

Traceback (most recent call last):
  File "/home/red/.pyenv/versions/red/lib/python3.8/site-packages/discord/ext/commands/core.py", line 85, in wrapped
    ret = await coro(*args, **kwargs)
  File "/home/red/.local/share/Red-DiscordBot/data/TechBot/cogs/CogManager/cogs/status/commands/statusset_com.py", line 226, in statusset_remove
    sr[service.name].remove(channel.id)
ValueError: list.remove(x): x not in list

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/red/.pyenv/versions/red/lib/python3.8/site-packages/discord/ext/commands/bot.py", line 939, in invoke
    await ctx.command.invoke(ctx)
  File "/home/red/.pyenv/versions/red/lib/python3.8/site-packages/redbot/core/commands/commands.py", line 832, in invoke
    await super().invoke(ctx)
  File "/home/red/.pyenv/versions/red/lib/python3.8/site-packages/discord/ext/commands/core.py", line 1348, in invoke
    await ctx.invoked_subcommand.invoke(ctx)
  File "/home/red/.pyenv/versions/red/lib/python3.8/site-packages/discord/ext/commands/core.py", line 863, in invoke
    await injected(*ctx.args, **ctx.kwargs)
  File "/home/red/.pyenv/versions/red/lib/python3.8/site-packages/discord/ext/commands/core.py", line 94, in wrapped
    raise CommandInvokeError(exc) from exc
discord.ext.commands.errors.CommandInvokeError: Command raised an exception: ValueError: list.remove(x): x not in list

statusset remove cloudflare #coding was formatted correctly.

At the moment, this issue is mainly so I can keep track of ideas. While this cog will come, it's not in active development as of issue creation.

While this will likely change, at the moment Discord's permission system for threads is rather limited. For example, you can't set up a helper role which can archive threads but not delete them - it's all or nothing. As well as this, (while there are rather strict rate limits) members can make multiple threads which might not be wanted in some situations. There are also some other limits, for example if you want everything in threads you can't deny permission for members to send messages in the main channel.

Here is a list of features I would like to see in this cog:

• Allow users to make threads from one where they can't send messages through a button
• Allow for users to be able to create a thread through a command
• Allow for custom archive times where the bot archives it (eg 15 mins or 3 hours)
• Limit to a customisable amount of threads per user
• Add a helper role which can archive threads, without the need for Discord's permission which will also let them delete the thread
• Above with optional ability to lock threads
• Allow for a customisable maximum limit of threads for all users
• Have a message which can be sent on thread create

If there's anything else you can think of, let me know in Discord or comment here.

I will remove Senty shortly for various reasons, including lack of effectiveness after an initial short good period and overhead in maintaining Sentry code, which is a little buggy at the moment.

Bug report

Cog failed to reload due to the following error after an update:

Exception during loading of package
Traceback (most recent call last):
  File "/root/redenv/lib/python3.8/site-packages/redbot/core/core_commands.py", line 171, in _load
    await bot.load_extension(spec)
  File "/root/redenv/lib/python3.8/site-packages/redbot/core/bot.py", line 1355, in load_extension
    lib = spec.loader.load_module()
  File "<frozen importlib._bootstrap_external>", line 462, in _check_name_wrapper
  File "<frozen importlib._bootstrap_external>", line 962, in load_module
  File "<frozen importlib._bootstrap_external>", line 787, in load_module
  File "<frozen importlib._bootstrap>", line 265, in _load_module_shim
  File "<frozen importlib._bootstrap>", line 702, in _load
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/root/.local/share/Red-DiscordBot/data/cybersafe/cogs/CogManager/cogs/status/__init__.py", line 3, in <module>
    from .core.status import Status
  File "/root/.local/share/Red-DiscordBot/data/cybersafe/cogs/CogManager/cogs/status/core/status.py", line 10, in <module>
    from ..commands.status_com import StatusCom
  File "/root/.local/share/Red-DiscordBot/data/cybersafe/cogs/CogManager/cogs/status/commands/status_com.py", line 11, in <module>
    from ..objects.caches import LastChecked, ServiceCooldown, ServiceRestrictionsCache
ModuleNotFoundError: No module named 'status.objects.caches'; 'status.objects' is not a package

GitHub Rewrite

The cog will be rewritten to be focused on buttons. This will happen when I have time to make a wrapper from the buttons API or (more likely) when discord.py and then Red support buttons.

Milestones support will also be added.

The cog will be renamed to ghissues as I was unaware of a naming conflict with obi's cog. At the time they were unapproved and I only searched approved repos for a conflict.

What cog is this feature request for?

CovidGraph

Describe the feature request in as much detail as possible

• Allow for multiple countries to be selected
• Add a 7-day rolling average to cases & deaths
• Allow for viewing of worldwide data

Bug report

These services will always send twice with the current set-up of how duplication checking works.

I know the issue, and I know how to fix it.

What cog is this bug report for?

Birthday

What versions are you running?

Versions                      
                ╷         ╷         ╷              
                │ Current │ Latest  │ Up to date?  
╶───────────────┼─────────┼─────────┼─────────────╴
  This Cog      │ 1.0.11  │ 1.0.10  │ 🟢           
  Bundled Utils │ b9bfa44 │ b9bfa44 │ 🟢           
  Red           │ 3.4.16  │ 3.4.16  │ 🟢           
                ╵         ╵         ╵

Describe the bug

The bot didn't post a message on birthday but role assignment worked.

If there's an error, paste it here

[11:00:27] ERROR    [red.vex.birthday.loop] Something went wrong in the Birthday loop. The loop will try again in an hour. Please report this and the below information to Vexed.
╭───────────────────── Traceback (most recent call last) ──────────────────────╮
│ /app/docker/cogs/CogManager/cogs/birthday/loop.py:118 in birthday_loop       │
│ ❱ 118                 await self._update_birthdays()                         │
│ /app/docker/cogs/CogManager/cogs/birthday/loop.py:207 in _update_birthdays   │
│ ❱ 207                             format_bday_message(all_settings[guild.id] │
│       ], member),                                                            │
│ /app/docker/cogs/CogManager/cogs/birthday/utils.py:26 in format_bday_message │
│ ❱ 26         return message.format(mention=author.mention, name=author.displ │
╰──────────────────────────────────────────────────────────────────────────────╯
KeyError: 'new_age'

What cog is this feature request for?

CmdLog

Describe the feature request in as much detail as possible

Remove the LogMixin object and instead tailor the classes individually. With slash commands included, this Mixin is trying to do too much.

This is one of my Hacktoberfest issues, which anyone may take without needing to ask me directly, and if not done I will get around to doing them in the coming months.

Bug report

The check here (perhaps some other too, I haven't looked) is sending a message:

The command checks should NOT send messages or have any other side effects as they do not only run when the command is run, they also run on things like [p]help, [p]permissions canrun, etc.
In this specific case, you should probably switch to a command before_invoke hook instead.

What cog is this feature request for?

all of them!

Describe the feature request in as much detail as possible

At the moment, the docs are in a pretty sad state with them being out of date. These should be updated again.

Cog docs are in docs/cogs and are generated using my fork of Bobloy's cogguide cog, which you can find here https://github.com/Vexed01/Fox-V3/tree/cogguide_develop. Note the branch is important if you're installing this with Red's downloader.

Where there are formatting conflicts between new and old (there are only like 2 I think, and they will be pretty obvious in the diff), manually edit to favour the old. Otherwise, very few edits to the auto-generated docs should be needed.

This is one of my Hacktoberfest issues, which anyone may take without needing to ask me directly, and if not done I will get around to doing them in the coming months.

BetterUptime needs a rewrite... There's lots of repeated code in the commands which could and should be moved - even some of it on cog load and cached in the pandas Series. And the loop could do with some improvements.

What's the timescale? I have no idea. It gets done when I have time/motivation to touch the sensitive cog.

Bug report

This is fixed locally, mainly making this issue to test out projects and the automation I've set up.
So don't PR a fix.

Bug report

Where it's from

Status

The bug

There's a space missing in the help menu of [p]statusset preview

Other details