« first day (1281 days earlier)      last day (494 days later) » 

11:51
!!/status
@lyxal I am doing the vaccuum. It's too loud for my liking
12:16
!!/status
@Ginger I am designing a new type of plant that can communicate with humans
12:31
2 messages moved to ­Trash
!!/pull
@Ginger Only members of group admin can run !!/pull.
what
!!/permissions list me
@Ginger Command error: Unknown command. Valid subcommands of permissions are: permissions list,permissions grant,permissions revoke
GingerIndustries pushed a commit to VyxalBot2/main in Vyxal/VyxalBot2: Fix typo in parser error message
12:36
!!/permissions list "me"
@Ginger User Ginger is a member of groups discussion.
what
@lyxal I thought you undid that?
24 hours ago, by Vyxal Bot
@lyxal Added Ginger to admin.
!!/permissions grant "me" "discussion"
@Ginger Ginger is already a member of discussion.
12:41
!!/permissions grant "zoomlogo" "discussion"
@Ginger Added zoomlogo to discussion.
!!/permissions list "zoomlogo"
@Ginger User zoomlogo is a member of groups member, discussion.
!!/permissions revoke "zoomlogo" "discussion"
@Ginger zoomlogo removed from discussion.
12:41
@lyxal run the grant command again?
!!/permissions grant "Ginger" admin
@lyxal Insufficient permissions.
what
!!/permissions list "lyxal"
@Ginger User lyxal is a member of groups .
what
hold on
12:43
Shutting down...
Well, here we are again.
!!/permissions list "me"
@Ginger User Ginger is a member of groups discussion, member, admin.
!!/permissions grant "lyxal" "admin"
@Ginger Added lyxal to admin.
that was weird
12:44
what do you think happened?
I have no idea
like really truly no idea
it's gotta be a bug somewhere in the code
I guess we just hope it doesn't recur
Refactoring do be like that sometimes
me when my rep has the funny number and a half
@Ginger is there a log of when permissions are added or removed?
12:47
Ah
well, kinda?
I was going to say maybe it'd show up when and what caused it
the messages sent are logged by sechat's machinery and then by supervisor
but supervisor's logs are capped, so they wouldn't be of much use
I suspect that a bug caused one of the permission commands to wipe every permission from a user instead of granting/removing a single one
!!/permissions list "zoomlogo"
@Ginger User zoomlogo is a member of groups member.
hmm
12:49
@Ginger how many messages?
not sure
Worth a check though anyway
to clarify: it logs every message sent in the room
regardless of who sent it
Still worth a try
I should probably fix the log config so it doesn't do that :p
12:51
Would be a good idea to do that :p
because if you had good message logging, you'd know that there's no bug and that I did a little trolling
Also you should probably implement a check that the admin group is never empty :p
what
lyxal, how did you do this
1 hour ago, by lyxal
!!/status
Notice how it's an edited message with no message history :p
oh.
welp
At least you fixed a typo as a result :p
!!/status
12:55
@The_AH I am doing reeeeeeee
!!/help
I'm Vyxal Bot 2, written by Ginger on behalf of Vyxal Corp.
All of my commands start with !!/
If you want help for a specific command, run !!/help "<command name>".
New to Vyxal? Try !!/info for more information.

Note: As of the 2.5 rewrite, command syntax has changed significantly. Run !!/help "syntax" for more info.

Command list: amilyxal, blame, coffee, cookie, die, groups, help, hug, idiom, info, issue, maul, permissions, ping, prod, pull, refresh, register, status, sus
I have a better solution: hardcode the bot to never let me be removed from the admin group
!!/status
@lyxal I am filing my taxes. Oh, wait...
12:56
!!/help amilyxal
@The_AH Command error: Unknown command. Valid subcommands of help are: help
@VyxalBot good bot
!!/help "amilyxal"
@The_AH No help is available for that command.
12:56
!!/help "blame"
@The_AH No help is available for that command.
!!/help "<blame>"
@The_AH No help is available for that command.
!!/help "!!/blame"
@The_AH No help is available for that command.
12:57
Hmm seems totally normal.
!!/help "blame"
@lyxal No help is available for that command.
!!/blame
@lyxal It was emanresu A's fault!
See, bots are such as weak as souls.
!!/help "status"
12:59
@The_AH !!/status: I will tell you what I'm doing (maybe).
!!/issue open "cookie" "what happens when I open an issue" "in a private repository" [cookie]
!!/status boring: Get actual status information about the bot.
@lyxal Failed to open issue: ("'Expiration time' claim ('exp') is too far in the future",)
Wasn't expecting that tbh
oh boy, this bug
YAY it works.
!!/help "idiom"
12:59
@The_AH !!/idiom add <title: str> <code: str> <description: str> [keywords: list]: Add an idiom to the idiom list.
!!/help "blame"
GingerIndustries pushed a commit to VyxalBot2/main in Vyxal/VyxalBot2: Keep lyxal from doing a little trolling
@Ginger The private repo exists btw
@The_AH No help is available for that command.
GingerIndustries pushed a commit to VyxalBot2/main in Vyxal/VyxalBot2: Fix logging level
@lyxal yeah, it's the same problem I thought I fixed earlier
it arises from a clock synchronization issue between Rydwolf's server and Github
13:00
Ah so it's a wolf problem is it?
Am I allowed to yell at him about this?
you can if you want, but I'm not actually sure it is
@lyxal First fill forms a101-section4-subsection8-4-variation-b12 to c805-section9-subsection2-6-variation-11c.
This is a reference.
since I've done a bunch of checks and they indicate that the server clocks never differ by over a second
try opening the issue again? I think I know what'll happen if it goes through
Wait is it the signature???
@lyxal Failed to open issue: ("'Expiration time' claim ('exp') is too far in the future",)
13:02
wacky
!!/help "idiom"
@The_AH !!/idiom add <title: str> <code: str> <description: str> [keywords: list]: Add an idiom to the idiom list.
That looks like a signature.
@VyxalBot loving that exit detection tho
Edit
Meant to say edit
hold on, lemme start up my test instance
13:03
!!/issue open "sandbox" "what happens when I open an issue" "in a private repository" [cookie]
@lyxal Failed to open issue: ("'Expiration time' claim ('exp') is too far in the future",)
Not lemme, letme.
"hold on, letme start up my test instance"
> ("'Expiration time' claim ('exp') is too far in the future",)
Great error message!
10/10
13:17
GingerIndustries pushed a commit to VyxalBot2/main in Vyxal/VyxalBot2: Maybe finally fixed the expiry time bug?
GingerIndustries pushed a commit to VyxalBot2/main in Vyxal/VyxalBot2: remove some debugging print()s
Shutting down...
Well, here we are again.
and there we go
!!/issue open "cookie" "what happens when vhg hi ugufpitiysitsii5di6 I open an issue" "in a private repository" [cookieghug]
@lyxal Failed to open issue: ("'Expiration time' claim ('exp') is too far in the future",)
are you kidding me
Unfortunately no
13:18
are you actually jo king right now
No
I'm lyxal
!!/pull
Shutting down...
Well, here we are again.
!!/issue open "cookie" "what jdkeibeihappens when I open an issue" "in a private repository" [cookieh]
@lyxal Failed to open issue: ("'Expiration time' claim ('exp') is too far in the future",)
Good stuff
Welp I'm bed for the night now
o/
13:21
weird, NTP isn't on
installed a few things and enabled NTP
!!/issue open "cookie" "what jdkeibeihappens when I open an issue" "in a private repository" [cookieh]
hm
I'm gonna hope it's fixed
 
6 hours later…
19:37
!!/status
@mathscat I am doing a nuclear strike on your location. Prepare for radiation in 3, 2, 1...
!!/status
@mathscat ☕
@mathscat I am going on a train ride and learning about transport.

« first day (1281 days earlier)      last day (494 days later) »