| Commit message (Collapse) | Author | Age | Lines | |
|---|---|---|---|---|
| * | Merge pull request #1491 from python-discord/fix/dmrelay | 2021-03-30 | -13/+9 | |
| |\ | ||||
| | * | Merge branch 'main' into fix/dmrelay | 2021-03-30 | -345/+490 | |
| | |\ | |/ |/| | ||||
| * | | Merge pull request #1470 from python-discord/help-channel-closing-delay-changes | 2021-03-30 | -345/+490 | |
| |\ \ | | | | | | | Extend close time logic to differentiate between the claimant and other users | |||
| | * | | Fix copy & paste error in closing reason enum | 2021-03-30 | -1/+1 | |
| | | | | ||||
| | * | | Change to an Enum for possible closing reasons | 2021-03-30 | -20/+32 | |
| | | | | ||||
| | * | | Enumerate all possible values for closed_on in docstring | 2021-03-30 | -1/+4 | |
| | | | | ||||
| | * | | HelpChannels: refactor get_closing_time | 2021-03-30 | -43/+43 | |
| | | | | ||||
| | * | | HelpChannels: use aware datetimes everywhere | 2021-03-30 | -27/+34 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix issues converting timestamps to datetimes and vice-versa. The main culprit id `datetime.timestamp()`, which always assumes naïve objects are in local time. That behaviour conflicts with discord.py, which returns naïve objects in UTC rather than local time. Switching from `utcfromtimestamp` to `fromtimestamp` was incorrect since the latter also assumes the timestamp is in local time. | |||
| | * | | Update arrow to 1.0.3 | 2021-03-30 | -267/+336 | |
| | | | | | | | | | | | | | | | | It has some API changes, so it's best to update now before the project starts using the library more. | |||
| | * | | Switch to datetime.fromtimestamp() to avoid over-compensation | 2021-03-26 | -3/+3 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we were using `utcfromtimestamp()` which would compensate the timestamp when converting to UTC even though the timestamp itself was in UTC: >>> datetime.utcnow() datetime.datetime(2021, 3, 26, 22, 8, 47, 441603) >>> a = datetime.utcnow().timestamp() 1616821624.207364 >>> a = datetime.utcfromtimestamp(a) datetime.datetime(2021, 3, 27, 5, 7, 4, 207364) By switching to `fromtimestamp()` this avoids that behaviour. | |||
| | * | | Use correct constant for each type of help session user | 2021-03-26 | -5/+5 | |
| | | | | ||||
| | * | | Add 1 second due to POSIX timestamps being lower resolution than datetime ↵ | 2021-03-26 | -3/+5 | |
| | | | | | | | | | | | | | objects. | |||
| | * | | Fix error when converting non claimant message | 2021-03-26 | -7/+10 | |
| | | | | | | | | | | | | | | | | | | | datetime.min cannot be converted to a timestamp as it's pre-epoch. Instead wait until we actuall need it and then create the correct datetime object depending on teh cache contents. | |||
| | * | | Convert to timestamp before posting to redis | 2021-03-25 | -2/+2 | |
| | | | | ||||
| | * | | Reset a channel's non-claimant cache on claim, to indicate that the session ↵ | 2021-03-25 | -7/+9 | |
| | | | | | | | | | | | | | has yet to be answered. | |||
| | * | | Refactor if block within help channel system to be more readable | 2021-03-25 | -6/+7 | |
| | | | | ||||
| | * | | Refactor help channel update message cache function for clearer flow | 2021-03-25 | -9/+8 | |
| | | | | ||||
| | * | | Create utc datetime objects from timestamps | 2021-03-25 | -4/+4 | |
| | | | | ||||
| | * | | Change help channel caching logic to use timezone naive stamps | 2021-03-25 | -3/+3 | |
| | | | | ||||
| | * | | Only fetch claimant id once | 2021-03-25 | -2/+3 | |
| | | | | ||||
| | * | | update help channel on_message docstring to reflect unchanged responsibility | 2021-03-25 | -6/+1 | |
| | | | | ||||
| | * | | Schedule channels just opened using claimant configured idle time | 2021-03-25 | -1/+1 | |
| | | | | ||||
| | * | | Check for close on command explictly. | 2021-03-25 | -1/+1 | |
| | | | | ||||
| | * | | Remove unneeded cache clearing | 2021-03-25 | -8/+0 | |
| | | | | ||||
| | * | | Change help channel logic to use timezone naive stamps | 2021-03-25 | -8/+6 | |
| | | | | ||||
| | * | | Don't prepend command closes with auto | 2021-03-25 | -2/+3 | |
| | | | | ||||
| | * | | Add back seperation whitespace | 2021-03-24 | -0/+1 | |
| | | | | ||||
| | * | | Use claiment idle time as default idle minutes. | 2021-03-24 | -1/+1 | |
| | | | | ||||
| | * | | Use fallback behaviour during cog init | 2021-03-24 | -5/+8 | |
| | | | | ||||
| | * | | Merge pull request #1476 from laundmo/help-channel-closing-delay-changes | 2021-03-20 | -27/+45 | |
| | |\ \ | | | | | | | | | reset cache on bot start, stats for different close reasons | |||
| | | * | | run precommit with all deps | 2021-03-20 | -1/+1 | |
| | | | | | ||||
| | | * | | passing pre-commit | 2021-03-20 | -4/+11 | |
| | | | | | ||||
| | | * | | reset cache on bot start, stats for different close reasons | 2021-03-19 | -28/+39 | |
| | |/ / | ||||
| | * | | More descriptive comment for when an if block is entered | 2021-03-18 | -1/+1 | |
| | | | | ||||
| | * | | Determine closing time from last message if either cache is empty, rather ↵ | 2021-03-18 | -2/+2 | |
| | | | | | | | | | | | | | than if both are empty | |||
| | * | | If the channel is empty, determine closing time based on last message. | 2021-03-18 | -4/+5 | |
| | | | | ||||
| | * | | Move return behaviour comments to in-line rather than docstring. | 2021-03-18 | -8/+4 | |
| | | | | ||||
| | * | | Delete cached claimant message time. | 2021-03-18 | -0/+1 | |
| | | | | ||||
| | * | | Update function name to describe new behaviour. | 2021-03-18 | -3/+3 | |
| | | | | | | | | | | | | | Also updates the doc string to reflect this new behaviour. | |||
| | * | | Repurpose unanswered cache for storing non-claimant last message times | 2021-03-18 | -59/+48 | |
| | | | | | | | | | | | | | | | | | | | | | | The unanswered cache was previously just a boolen of whether a non-claimant every replied to a help channel. With us now needing to know the time at which a non-claimant messaged in a given channel, we infer the answered status from this cache instead. | |||
| | * | | Improve docs strings and variable names within the help channel system | 2021-03-17 | -20/+20 | |
| | | | | ||||
| | * | | Improve availible channel embed footer | 2021-03-17 | -1/+1 | |
| | | | | ||||
| | * | | Improve trace message. | 2021-03-16 | -1/+1 | |
| | | | | ||||
| | * | | Extend close time logic to differentiate between the claimant and other users. | 2021-03-16 | -29/+75 | |
| | | | | ||||
| | * | | Update help availible footer | 2021-03-16 | -1/+1 | |
| | | | | | | | | | | | | | | | | As we have complicated this logic, we now don't specify exactly how long until the channel will close. | |||
| | * | | Set a reasonable default for `idle_minutes_others`. | 2021-03-16 | -1/+1 | |
| | | | | ||||
| | * | | Split out help channel idle time constants | 2021-03-16 | -3/+8 | |
| | | | | | | | | | | | | | | | | This allows us to configure the idle time allowed for claiments seperate from tohers. | |||
| | | * | Removed user event announcements from the config. | 2021-03-30 | -4/+0 | |
| | | | | ||||
| | | * | Gracefully handle failure to upload to hastebin in `!dmrelay`. | 2021-03-30 | -0/+5 | |
| | | | | ||||
| | | * | Replace usage of `textwrap.dedent` with a cleaner method. | 2021-03-30 | -5/+4 | |
| | | | | ||||