7 kyu
Fizz Buzz Cuckoo Clock
938 of 4,225tachyonlabs
Loading description...
Fundamentals
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
python new test framework is required. updated in this fork
Approved
Oh fnargh that's one annoying clock. I would've thrown it out the window within 1 hour.
chai/assert) should be enabledSo I keep getting the following error on the scala solution:
Test Failed "...Cuckoo Cuckoo Cuckoo[]" did not equal "...Cuckoo Cuckoo Cuckoo[ Cuckoo]"
Doesn't seem to matter how I build my string. Any ideas about what's going on?
It seems your cuckoos are one cuckoo short. I just solved the kata in Scala nad encountered no problems with it.
I am going to close this one as not a kata issue, because tests seem to be correct. If you have any doubts, post your code or ask for help on Codewars Discord.
Scala translation kumited. Please review and approve. Thanks, suic
Thank you! I'm on a bus to an event right now, but will take a look tonight or in the morning depending on how late I get home.
No hurry. :) Enjoy the event. Regards, suic
I just approved it, thanks again! I don't have any Scala experience, but it all looks reasonable to me and passes the tests, and I'm assuming you know what you're doing.
Thanks :)
Groovy translation kumited. Please review and approve. Thanks, suic
Thanks, I will check it out! I had done Groovy versions of my piano katas a while back when I was playing around with Groovy a little, but didn't do them for any of my others.
I just approved it, thank you again!
.
This comment has been hidden.
[JAVA] Firstly, really enjoyable kata. Help needed to understand why my solution doesn't pass muster.
When I run the 'Attempt' tests it tells me that they passed but maintains a red border around the output box. Doesn't allow me to submit either. Sample tests are fine.
Time: 3423ms Passed: 2 Failed: 0 Test Results: SomeBasicTimesTests(TestCases) (1 of 1 Assertions) SomeRandomTimesTests(TestCases) (1 of 1 Assertions) Completed in 93.732186 ms
Currently Codewars platform is experiencing issues.
https://github.com/Codewars/codewars.com/issues/893
Thanks Voile.
Yeah, there was a general CodeWars bug preventing any katas from being completed/submitted. It is fixed now, so go ahead and resubmit!
I keep getting, Expected: 'Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo', instead got: 'Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo Cuckoo'
I cant see a difference?
Yeah, me neither. Which language were you using, and did you get that with the example tests or the full tests?
Javascript. Both i think, whenever it is on the hour apart from 00.00 I havent figured that bit out yet. I am fairly new to this and probably not doing it the right way.
On one hand, there have been 99 JavaScript completions so far, so I assume the test cases are working, but on the other hand the error message you posted is perplexing, and new bugs can always be discovered in addition to occasionally turning up as side effects of Codewars site updates. My first guess was that you were returning the string with a trailing space, and for some reason it was getting stripped when the error message was displayed, but when I tried triggering that myself, then I did see the trailing space in the error message, so it's not that. Can you post your code so I can test it and see what is going on here?
Is there a trailing space? I had that issue on my first attempt
CoffeeScript Translation
Great, thank you!
One of the few interesting fizz buzz katas, so it deserved a fun solution as well :) Thank you!
Thanks!
Good story
Thanks!
As per a suggestion from @JohanWiltink below, I just added "00:00" and "12:00" to the fixed tests for both the example tests and the full test suites for all the languages. Unfortunately this broke a lot of people's solutions, which I had not been expecting. :-( I am sorry! I don't know if this is something people get notified about when it happens, but if so, hopefully people will read this comment and know what happened.
Very nice kata. It was fun to solve and translate. Regards, suic
Haskell translation kumited! Please review and approve. Thanks, suic
Thank you! I will check it out when I get home later today.
Wow, Haskell looks very different from everything I am used to, I can't even tell how many random tests you are doing. One thing, though -- as per a suggestion from @JohanWiltink below, I just added "00:00" and "12:00" to the fixed tests for both the example tests and the full test suites, for Java, JavaScript, Python, and Ruby, and unfortunately this broke a lot of people's solutions, which I wasn't expecting. :-( Can you add the following to the end of the "Example Tests" sections in both the example tests and the full test suite?
Hi,
thanks for the review :) I've added those two tests. As I know QuickCheck generates 100 random tests by default but I'm not 100% sure.
Regards,
suic
Thanks! I have one more thing to ask about, though: Yesterday when I had added those two test cases and also added a PHP version, I updated the "Some examples" section of the kata description to include those two test cases as well, and removed the line "PHP version tomorrow!" at the end -- if you go to https://www.codewars.com/kata/fizz-buzz-cuckoo-clock you will see this. But when I look at your translation now, although I am seeing the added test cases, the description shown is still the previous version of the description, without those changes, and when I tried to approve your translation, I got the error message "Description cannot be approved, recent changes from related record must be merged first."
So I guess that description merge is something you need to do, and then I should be able to approve it.
Please try one of these two: 1, 2. Thanks, suic
OK, this is weird, but I got it to work: #1's description had the updates, but I got the same "Description cannot be approved, recent changes from related record must be merged first." error message when I tried to approve it. #2 still had the previous description, but I was able to approve it with no problems. Then when I looked at the kata I saw that the description had gone back to the previous (no 00:00 or 12:00 examples, yes PHP tomorrow reference) version, so I put the description updates back in myself, republished, and now it looks fine. Thanks again, and who knows what is up with these odd behaviors ...
Thanks! Sorry for the issues. Sharing the descriptions sometimes causes headaches :(
Regards,
suic
Very good kata. But you make me think if I'd be able to bear so noisy clock at gome. :)
Thanks! I did have a cuckoo clock at my previous house that went off on the hour and half hour at least, but it was between the kitchen and living room rather than in a bedroom.
Could do with fixed test for 0:00 or 12:00.
On one hand, sure, but on the other hand, Codewars is a little screwed up right now -- I did a Java version of this kata earlier this afternoon, and now the listing for it on https://www.codewars.com/kata/my-languages is showing five Java logos, and if you go to the kata and click the language dropdown, it has five entries for Java -- so I probably should wait until that is cleared up before making and more changes.
OK, I just added "00:00" and "12:00" to the fixed tests for both the example tests and the full test suites, for Java, JavaScript, Python, and Ruby. Unfortunately this broke a lot of people's solutions, which I had not been expecting. :-( I don't know if this is something people get notified about when it happens, but I guess I will post this as its own comment above as well.
Loved this Kata, easy and familiar but original with an interesting twist. Keep up the good work :D
Thank you, glad you liked it!