Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] MCQ generation borken #85

Open
manthanabc opened this issue Dec 22, 2024 · 0 comments · May be fixed by #86
Open

[bug] MCQ generation borken #85

manthanabc opened this issue Dec 22, 2024 · 0 comments · May be fixed by #86

Comments

@manthanabc
Copy link

manthanabc commented Dec 22, 2024

Issue Title:

Bug: MCQ generation broken

Issue Description:

Problem:

mcq generation is currently broken, shows an blank page. because of wrong parsing of the response from backend

ERROR
qaPair.answer.filter is not a function
TypeError: qaPair.answer.filter is not a function
    at http://localhost:3000/main.c67f2d856a8237efebf9.hot-update.js:78:41
    at Array.forEach (<anonymous>)
    at http://localhost:3000/main.c67f2d856a8237efebf9.hot-update.js:76:38
    at commitHookEffectListMount (http://localhost:3000/static/js/bundle.js:64502:30)
    at commitPassiveMountOnFiber (http://localhost:3000/static/js/bundle.js:65995:17)
    at commitPassiveMountEffects_complete (http://localhost:3000/static/js/bundle.js:65967:13)
    at commitPassiveMountEffects_begin (http://localhost:3000/static/js/bundle.js:65957:11)
    at commitPassiveMountEffects (http://localhost:3000/static/js/bundle.js:65947:7)
    at flushPassiveEffectsImpl (http://localhost:3000/static/js/bundle.js:67830:7)
    at flushPassiveEffects (http://localhost:3000/static/js/bundle.js:67783:18)
ERROR
qaPair.answer.filter is not a function
TypeError: qaPair.answer.filter is not a function
    at http://localhost:3000/main.c67f2d856a8237efebf9.hot-update.js:78:41
    at Array.forEach (<anonymous>)
    at http://localhost:3000/main.c67f2d856a8237efebf9.hot-update.js:76:38
    at commitHookEffectListMount (http://localhost:3000/static/js/bundle.js:64502:30)
    at commitPassiveMountOnFiber (http://localhost:3000/static/js/bundle.js:65995:17)
    at commitPassiveMountEffects_complete (http://localhost:3000/static/js/bundle.js:65967:13)
    at commitPassiveMountEffects_begin (http://localhost:3000/static/js/bundle.js:65957:11)
    at commitPassiveMountEffects (http://localhost:3000/static/js/bundle.js:65947:7)
    at flushPassiveEffectsImpl (http://localhost:3000/static/js/bundle.js:67830:7)
    at flushPassiveEffects (http://localhost:3000/static/js/bundle.js:67783:18)

Proposed Solution:

Fix the issue by changing output.jsx. to refer to correct property
qaPairs.answer is a type string, while the options are at qaPairs.options,
This could have happened because someone refactored the backend and forgot to change it in the frontend

Expected Behavior:

Should show the output page, similar to the one shown by other pages

Labels:

- Bug
- MCQ generation

edit: used the correct issue template

@manthanabc manthanabc linked a pull request Dec 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant