The testcase failure logs: [tester::#YD3] [test] master: > REPLCONF GETACK * [tester::#YD3] Received: "" (no content received) [tester::#YD3] ^ error But when I run my code there clearly is some content. Also I’ve used “sudo tcpdump -i lo0 -X port 6379 or port 6380” to check the TCP tra…

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

I’ll take a look by the end of the week.

Hi @danilovict2 , I tried running your code against the previous stages, but it’s no longer passing Stage #YG4 (Replication - Command Processing). [image] Suggestions: Use our CLI to test against previous stages by running: codecrafters test --previous Focus on fixing the early stages first,…

[image] andy1li: codecrafters test --previous Hi, I’ve fixed the previous tests you mentioned, but now previous tests fail on #hd5 and the current tests still mismatch the output I have with my on #hd5 are: [tester::#HD5] Expected command to be “set”, got “ping” [tester::#HD5] Test failed …

Test cases on this extension are very inconsistent. I’m currently stuck on stage #YD3 and last time I asked this admin or whoever the guy is told me to make previous stages pass. This, however, is impossible because every time I run the code I get different outputs from the tests. When I run codec…

Hi @danilovict2 , the issue is likely caused by race conditions, which can result in inconsistent outputs across multiple runs. One common cause of race conditions for replicas is when handshaking with the master overlaps with accepting client connections simultaneously: [image] Could you try ens…

i am facing the same issue, [image] #YG4 Command not reaching to the replica General CodeCarfters tester output: remote: ------------------------------------------------------------------------ remote: remote: remote: ___ _ ___ __ …

[image] andy1li: One common cause of race conditions for replicas is when handshaking with the master overlaps with accepting client connections simultaneously Could you enlighten me on how exactly I should do that?

Sure! Just a heads-up—I’m also a beginner in Go, so take my suggestions with a grain of salt. s.connectToMaster should NOT be run as a goroutine. Once the handshake is complete, you can run the listener for the connection to the master as a goroutine. Make other necessary adjustments to your code. …

Tried that and it didn’t work

@danilovict2 Are you still encountering the same issue, or do the logs indicate something different now?

Problem with a testcase in #YD3

Challenges

wigiwee November 30, 2024, 4:54am 11

i am facing the same issue,

Topic		Replies	Views
Redis Challenge #YD3 Challenges challenge:redis	9	251	July 8, 2025
Huge problem with tests on Replication Stage Challenges challenge:redis	1	124	December 4, 2024
#YG4 Command not reaching to the replica Challenges challenge:redis	14	217	December 15, 2024
Replica doesn't get replication command - #YG4 test Challenges challenge:redis	2	108	March 29, 2025
#YG4 and #XV6 Replica cannot read the message sent by master Challenges challenge:redis	5	164	March 25, 2025

Problem with a testcase in #YD3

Related topics