I did quiz exam for dev1 some days back but I didn’t get any feedback though after submission, info was displayed “You will be notified on the talk”. Does it need for me to re-take the quiz or result take quit long to be released
No you don’t need to re-do the quez just be patient it will be worked on.
So I can see that @isamanya finished the test 10/12/2020 2:54:29 (UTC).
I can see in the application logs tried to grant Smart Developer .
[2020-10-13 05:02:30.767] [INFO] grader.js - isamanya granted Smart Developer
Now I have no exception whatoever in the logs. Well, that will be fun.
@burke I tried restarting the app and rerunning it (removing the data from the spreadsheet), and it doesn’t seem to be working anymore. The code looks pretty straightforward, but somehow it’s saying it’s a success and it’s not doing anything.
Seems to be happening since I upgraded talk.
Working through this. Quizgrader is a bit rusty. I managed to get a dev instance to run. Quizgrader is getting a “BAD CSRF” error when invoking the Discourse API. It looks like the problem is coming from this change in Discourse, where API authentication is now done via the header.
I think I’ve got it fixed (and cleaned a little rust off quizgrader along the way). I’ve committed my changes, but don’t know if those will make it into the infrastructure automatically. I’ll try to check on that tomorrow.
So I checked dockerhub, and the build was red (it was configured wrong, pointing to wrong folder). I fixed it.
Then I ran on the machine hosting it to update the image:
I went to the spreadsheet and deleted the grade for @isamanya, and rerun the quizgrader. That seems to have done the trick!!! YEY
@cintiadr, Thanks so much for upgrading Discourse! Since I was touching quizgrader, I added in log entries for any errors coming from Discourse. Hopefully, we won’t need them… but, if we do, the log entries will be more helpful next time.
@cintiadr, @burke and @dkayiwa kind help please! @pasindur2 has done the quiz twice and he has not got any feedback within the 24hrs hours of submission. I kindly request you look into his issue at your convenient time please!
I’ve been looking into this. There were a few issues.
- Some of the earlier problems were because the PR entered did not match the pattern required (i.e., the PR wasn’t to a repository within the OpenMRS org).
- More recently, some of the identifying info (most importantly OpenMRS ID) wasn’t getting copied over by Zapier. I refreshed the Zapier “zap” and it seems to have fixed that problem.
- The quizgrader is unable to reach OpenMRS Talk because it considers Talk’s TLS certificate to be invalid. I think it might be related to this issue and asked @cintiadr her thoughts on how to fix it. It’s possible rebooting that machine might fix the problem.
BTW… our dev1 quiz is woefully outdated and needs attention. I’ve started a Google Form version but haven’t had the time to refactor a new version of quizgrader to make it work. That would both get rid of some of the outdated questions and eliminate the need for SurveyMonkey + Zapier for the dev quiz.
I’ve upgraded the version of
node used by our quizgrader and that seems to have fixed the certificate issue being caused from older versions. @pasindur2 received the Smart Developer badge as expected and should be granted the /dev/1 badge within ~24 hours.
@jwnasambu I finally also attempted the quiz a few days ago however I haven’t had any responses yet Any kind of help is appreciated Thanks !!!
@dbaluku you should’ve gotten the badge after your first attempt; however, something is preventing contact information from being properly populated. So, the quiz grader can see all of your answers and successfully grade the quiz, but it doesn’t have your name, email address, or OpenMRS ID populated for some reason.
I’ll need to do some more troubleshooting. There’s no need for you to take the test again. Once I get it working, you should receive your badge.
@burke Have also tried now for a while so far like two-three times but no response…
Am sorry you had to do the quiz thrice we are deeply sorry for the inconvenience. Just keep pushing code you never know you may be the second after @ibacher from dev null to Dev4.