avi_mathur In Scala the line
println ( list + "\n" )
must be removed.
xavier_guihot yes, since the result is then outputed twice, making the tests fail
civilizeddev Yes, but you can change the return type of the function
ftoStringinstead.dzmitry75 lol I tried to fix that by inserting
println(s"[${list.mkString(", ")}]")
instead :) Thanks for the hint
u_suke_goto seems broken on elixir as well
mobileka Confirmed.
It passes when I run the code, but fails all the tests when I submit it.
AllisonP I'm able to pass in Elixir. Do you want to try it again and see if you're still having an issue? Make sure you're printing a space/comma/semicolon-separated list.
mobileka Looks like test cases #1 and #2 are still broken. These cases expect an integer number as an output but it has to be a list instead.
HuShifang Confirmed this -- my code passes all the test cases but #1 and #2, and when I "purchase" test case #2, it indicates that the input and output should both be the integer X -- not a list of length X.
rossiheron Still broken
arseny_info Still broken, and it's broken for 2 years now :(
A1ex_l Still broken for elixir.
luislhsc It passed for me
diego_viniegra Still broken for elixir!!
landonwilkins IO.inspect's default limit is 50
1..90 |> Enum.to_list |> IO.inspect [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, ...]
1..90 |> Enum.to_list |> IO.inspect(limit: :infinity) [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90]
diegogl1312 Thank you very much! It worked for me on Elixir now!!
idabmat Sorry something still seems weird. Testcase 1 passes when "running" the code, but then it fails when "submitting" it.
ricoh Still broken!! Seems like the internal mechanism is counting the number of items in the list, which it uses to assert the test results. So output should be a list so it counts the number of elements. Purchased all test cases and for some wierd reason, even though testcase #1 and #2 fail, seems like #3 and #4 pass, and the output is an integer (total number of elements in the list) just like in the first 2.
ricoh ...was using
IO.inspectwithout options, thats why it was failing, sinceinspectdoes not show the whole list if its too long, passinglimit: :infinityto the inspect function's options fixed it. Nice!
luislhsc I was able to pass all tests cases as well
dillonredding I'm getting the following compile message in Scala, regardless of how I write it:
warning: there was one deprecation warning; re-run with -deprecation for details one warning found
hpedrorodrigues I had the same message.
saberwang Me, too. I think it's a bug in python scripts that run on Server . Foget my Bad English
saberwang def f(num:Int) : List[Int] = if(num==0) List() else num::f(num-1)
I'm sure that's right
AllisonP Sorry about this, Scala is fixed now.
sethia_arun I am getting this error , I don't see any issue here in scala code
val list:List[Int]=(0 until num).toList
It will give f(2) will be List(0,1,2)
warning: there was one deprecation warning; re-run with -deprecation for details one warning found
sbacarob Could you check for Elixir? Test case #1 and Test case #2 have a wrong expected output
liborio7 I had the same problem with Test case #1 and #2. In my case the problem was the IO.inspect function. I solved it limiting to infinity the output: IO.inspect(list, limit: :infinity)
rossiheron Thanks, it worked for me.
ivorpaul Worked for me as well. Thanks!
LuisLC Issue is with the readInt method.I get the following when running the same program locally, using the the -deprecation tag:
/home/lcampos/Development/learn-scala/Solution.scala:7: warning: method readInt in trait DeprecatedPredef is deprecated (since 2.11.0): use the method in `scala.io.StdIn` println(f(readInt))
Ok, so the last line of code should be:
println(f(scala.io.StdIn.readInt))
balintant Haskell
fn n = [1..n]
petertheking Is the checker broken for clojure? Input is 10, expected output is 10?
davcamer I believe expected output is a list of ten elements. This is unclear in the problem statement, but a list of ten elements satisfies the checker for Scala.
Nondv It's not broken. More than that, there's a one-word solution on Clojure ;D
petertheking Thanks all. I solved it the first time using one of the one-word solutions in Clojure the first time around, although I think it defeats the spirit of some of these questions.
itissera Seems that there is a problem in the checker for Scala. Same issue reported by other users. The output checked is not what I get in my scala REPL.
sidproquoAsked to answer Agreed. I just checked with my previously submitted code (which had cleared all test cases). The same code is failing now. It's broken, yeah.
krauszraphael Me too!
Argh... I've done this exercise 5 times in 5 different ways - all marked wrong, but all right in my REPL.
bi_myname same
Elegba Looks like noone reads our complains :(
gciuloaica it is still broken for both run code and submit, for scala
AllisonP This is fixed. Sorry!
gciuloaica yep. it works. Thanks
rmrhr If you are using Elixir and
IO.inspectto output the list, make sure to addlimit: :infinityin the options.
http://elixir-lang.org/docs/stable/elixir/Inspect.Opts.html
tejakantamneni I tried my code below and looks like it is working fine locally, is the validator missing or my logic at fault?
def f(num:Int) : List[Int] = List.range(0, num)
adamlabbe The test runner appears broken, anything solution I try results in this Python error:
Traceback (most recent call last): File "/custom-ztciEr8Zbx3aAXhveWH4/solution.py", line 94, in score, testcase_status = process(data) File "/custom-ztciEr8Zbx3aAXhveWH4/solution.py", line 56, in process is_code_works, scores, testcase_statuses = check_inputs(testcase_input, testcase_output, user_output) File "/custom-ztciEr8Zbx3aAXhveWH4/solution.py", line 46, in check_inputs raise("check") TypeError: exceptions must be old-style classes or derived from BaseException, not str
savanni_dgerinel Seeing this, too. I am providing a correct Haskell solution (tested in the REPL), and it is not actually even running my solution.
nuno_mvrodrigue1 Admins , the tests are not working for haskell , i test the same function here and on ghc and here it gives a wrong output
hololeap [deleted]AllisonP I'm wasn't having any issues passing with Haskell, but I made changes to the checker and code stubs. Try resubmitting and see if it helps.
mnoronha For some reason, the haskell checker rejects [1..n], but accepts [1..(n)]
brynmurrell97 Not for me
f n = [1..n]
worked fine for me
Sort 108 Discussions, By:
Please Login in order to post a comment