mzntori pushed to master at mzntori/order 2025-01-14 13:22:25 -05:00
6c6ab00929 Initial Commit
mzntori created branch master in mzntori/order 2025-01-14 13:22:25 -05:00
mzntori created repository mzntori/order 2025-01-14 13:18:48 -05:00
mzntori created repository mzntori/nyehehehhe 2024-08-17 18:16:19 -04:00
mzntori created branch master in mzntori/DeepdipBot 2024-05-15 10:51:49 -04:00
mzntori pushed to master at mzntori/DeepdipBot 2024-05-15 10:51:49 -04:00
fd6ff84d18 Initial commit
mzntori created repository mzntori/DeepdipBot 2024-05-15 10:51:24 -04:00
mzntori commented on issue modulatingforce/forcebot_rs#77 2024-04-09 15:21:12 -04:00
More intuitive calls to BotLock

I thought harus idea was to put this whole block of replying to someone into a method for params. Just returning the lock won't really make it easier to use.

mzntori commented on pull request modulatingforce/forcebot_rs#52 2024-04-03 15:38:13 -04:00
Retrieve Reply information from ExecBodyParams

SayInReplyTo((S, S), S) is very unintuitive, either remove the tuple or make it something like SayInReplyTo{channel: S, message_id: S, message: S}. As for the method params for `say_in_reply_t…

mzntori created pull request modulatingforce/forcebot_rs#55 2024-04-01 14:21:45 -04:00
WIP: issue-routine-lock-idea1
mzntori created branch issue-routine-lock-idea1 in modulatingforce/forcebot_rs 2024-04-01 12:39:21 -04:00
mzntori pushed to issue-routine-lock-idea1 at modulatingforce/forcebot_rs 2024-04-01 12:39:21 -04:00
7db048937b call loopbody on a read lock
mzntori pushed to retrieve-reply-details at modulatingforce/forcebot_rs 2024-03-29 20:47:44 -04:00
a048003e93 oops forgot to add the use statement
mzntori commented on pull request modulatingforce/forcebot_rs#52 2024-03-29 20:42:58 -04:00
Retrieve Reply information from ExecBodyParams

Does this work how you wanted it?

mzntori pushed to retrieve-reply-details at modulatingforce/forcebot_rs 2024-03-29 20:42:29 -04:00
f2893791b9 add reply parent functionality
mzntori commented on pull request modulatingforce/forcebot_rs#51 2024-03-29 16:13:18 -04:00
WIP: Routine Unresponsive due to Deadlock

Second commit isn't necessary btw you can roll that back if you want, but it just has a bunch of debug implementations that might help debugging stuff like this in the future.

mzntori commented on pull request modulatingforce/forcebot_rs#51 2024-03-29 16:11:58 -04:00
WIP: Routine Unresponsive due to Deadlock

The Routine that you want to read lock in the execution body is the routine that is used to call that execution body, making it so the execution body waits for itself to end. No idea how you would…

mzntori pushed to issue-routine-lock at modulatingforce/forcebot_rs 2024-03-29 16:08:12 -04:00
fcf4f3f7cf add debug implementations that helped (kinda)
9d94328cd6 mark call that locks execbody from using that routine
Compare 2 commits »
mzntori pushed to main at mzntori/lol 2024-03-28 16:10:01 -04:00
a57ba2348c test 3
mzntori pushed to main at mzntori/lol 2024-03-28 15:56:17 -04:00
660b0eeb04 test 2