The variability in this test case is quite odd. I can run the same command two in a row and receive two different outputs. I just dont understand what is happening nor how it is testing. I have print statements that will voluntarily show and not show. Can someone give me an explanation as how to t…

Alright, guess we can close this thread. Have a good one.

Hey @gimmy1 , there might be multiple issues at play. Here’re the first ones that I encountered: #HD5 (Replication - Multi-replica propagation) [image] Looks like PINGs are being propagated when they shouldn’t be. Deleting this block should fix it: [image] Running tests for Stage #XV6 (Rep…

Closing this thread due to inactivity. If you still need assistance, feel free to reopen or start a new discussion!

Hello @andy1li Appreciate your response. Can you please explain how the master, through your tests, invoke this command? I would like to re-create the flow locally without running the tests. How the master is triggered to send a REPLCONF GETACK 1 Is there a way to test one test instead of the sui…

@gimmy1 There is no guarantee that a single read from a TCP connection will contain just one command. Your replica should be able to handle multiple commands received in a single read: [image] Can you please explain how the master, through your tests, invoke this command? Here’s the tester c…

[image] andy1li: @gimmy1 There is no guarantee that a single read from a TCP connection will contain just one command. Hey man, i’m not confused whether or not there will be multiple commands or a single command within one read. I’m more confused on the consistency of the test and what I can …

@gimmy1 Glad to hear it’s working now! :tada: Sorry if I misunderstood earlier. AFAIK, the only inconsistency or non-deterministic behavior is that a single read may or may not contain multiple commands. For example, in my code i have an initial handshake code which sends the 4 commands and ignor…

@gimmy1 Just a heads-up: your recent submissions didn’t pass our flaky test, which meant the results were still non-deterministic. [image] Suggestion: Use our CLI to test against previous stages by running: codecrafters test --previous You might need to run it multiple times to catch an unluck…

Just FYI: Lucky run [image] Unlucky run [image]

Redis Challenge #YD3

Challenges

Topic		Replies	Views
#YG4 and #XV6 Replica cannot read the message sent by master Challenges challenge:redis	5	162	March 25, 2025
#xv6 failed test! I have passed some test, but other test failed! Challenges challenge:redis	9	234	July 18, 2025
Go trouble with replica processing commands Challenges challenge:redis	1	73	February 9, 2025
Incorrect test for Replication #TU8 Challenges challenge:redis	13	456	June 4, 2024
Flaky tests for Stage #YD3 (Replication - ACKs with commands) Challenges challenge:redis	1	72	July 20, 2025

Redis Challenge #YD3

Related topics