I solved challenge 001 of codeabbey using hy language, however, I can’t get past the Job /test/policy and Job /solutions/haxe, it gave me some error messages, including “ValueError: ‘hack’ is not in list” in the policy. In the past, I was solving hacking challenges but when I started with programming challenges, I got this new fail.
What do you understand or find about that problem
First I thought the complexity was incorrect, but it’s the lowest complexity, corresponding to one. Maybe the failure at Job /solutions/haxe be for the same reason of first job failure.
Did you try any workaround? What did you do?
I searched at the forum for similar problems, but I could not find a similar one
About the job solutions/haxe, you can just re-run it. Sometimes some jobs fail because of an external error, in this case, a communication error between the git client and the GitLab server.
Thanks for changing the policy, it solves my issue with the job /test/policy. But the other issue with /test/generic/pre_commit job continues (This is my commit). I read all other posts with the same issue, but in all cases, they have other “failed” cases before, however, I only have one failed case that is this:
I tried adding and removing a new line after the last line in the YAML file, but don’t work. Also, I compared my YAML file with another YAML file uploaded by another person on the repository recently, nevertheless, I didn’t find differences (including with spaces and new lines). I compared that in an online page:
*Left is my YAML file and right is another partner’s YAML file that Merges Request successfully in the repository
I solved that by removing the YAML and creating that again with the same content. It worked to solve this error:
(https://gitlab.com/autonomicjump/challenges/-/jobs/2213646416#L1074) 1:10 error wrong new line character: expected \n (new-lines)
And the warning missing document start “—” there isn’t a problem with that, is just a warning. Thanks to all for helping me.
Additionally, I think the error got because I created the YAML in VSCode in windows OS, and it changed the format of the file, then I passed those files to my Linux OS, removed the YAML, and created it again. It works for me.
Hello how are you? :
The solution to the “—” warning is to leave a blank line at the end of the document. That makes that warning disappear, in some programs like vscode it does it automatically or in Geany it also does it automatically.