Closed EthanThatOneKid closed 11 months ago
Background: The events described in this historical account occurred on October 14th and 15th, 2023 taking place on Discord. The time zone for the activities mentioned is Pacific Standard Time (PST).
October 14th:
2:00 PM: Ethan (he/Webmaster) initiates a task to complete the "secrets doc," a confidential document hosted on Google Docs.
3:25 PM: Ethan (he/Webmaster) begins a series of actions related to the QA database, including an attempt to register in the QA database. This registration is successful under the Leetcode username "LC-Dailies."
3:34 PM: Ethan successfully submits a Leetcode solution for the current season.
3:36 PM: Ethan comments on the process of setting up a QA environment, describing it as not too complex but potentially tedious for multiple environments.
3:50 PM: Ethan mentions testing the QA sync subcommand, suggesting ongoing efforts to ensure the bot's functionality.
6:40 PM: Casual greetings are exchanged between participants, including "sǝʌ⅄sʍollɐH" and "evan j."
October 15th:
12:11 PM: Ethan skips a manual test related to syncing without any new submissions.
12:12 PM: Ethan initiates Manual Test 2, involving syncing with an empty season and one new submission. The bot confirms synchronization of "Season 01HC69AT007FQ3YW2RMKD6B5JM."
3:07 PM: Justin inquires about the ongoing activity.
4:15 PM: Ethan explains that the testing is related to a bot used in the "algo-chat" channel and expresses concerns about bot notifications affecting everyone.
4:16 PM: Karni suggests that Justin might not have muted the channel, leading to his curiosity.
4:19 PM: Ethan elaborates on the bot's purpose, describing it as a system that splits daily Leetcode challenges by week and calculates weekly scores for registered players. He mentions that it is hosted on Deno Deploy.
8:35 PM: The bot reports a successful synchronization of "Season 01HCRA3V00MS135M8MZ9BJG5QC," with a user named Ethanthatonekid receiving 90 points.
8:39 PM: Ethan concludes Manual Test 2 with a positive outcome, stating that the sync subcommand is working as intended, and the new submission appears in the latest season object.
9:56 PM: Ethan solves the daily Leetcode question, provides a link to the solution, and announces plans to execute a POST request.
10:38 PM: Ethan encounters an error but fixes it, attributing the problem to sending the fetch request in the wrong browser tab.
10:48 PM: Ethan explains that the new daily Leetcode question embed allows automatic synchronization of the season with Leetcode, signaling that the latest season has been synced.
10:51 PM: Ethan confirms that his earlier submission had automatically synced to the database without requiring a manual command.
10:52 PM: Ethan notes the matching submission ID with lc-dailies-qa and an accurate synced_at timestamp with lc-dailies-qa.
10:58 PM: Ethan notes the success of Manual Test 3, highlighting the readiness of a specific URL or repository (https://oss.acmcsuf.com/lc-dailies/pull/41) associated with the project. This test demonstrates the effectiveness of the bot's daily synchronization process.
Resolves #34.