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

Parser error when 'Check all is answered' is run [bug] [EMC] #732

Open
avanoostrum opened this issue Jul 21, 2022 · 4 comments
Open

Parser error when 'Check all is answered' is run [bug] [EMC] #732

avanoostrum opened this issue Jul 21, 2022 · 4 comments

Comments

@avanoostrum
Copy link

In the EMC test installation on the test server clicking check all is answered for all sources generates the following error:

Communication error
parsererror
00000{"current":"3.82","max":100,"percent":3.82,"timeTaken":1369,"timeRemaining":34469,"text":"Checked 1740 tokens.","finished":false}

Project version 1.9.1p7
EMC version 1.8.7
EMC build 20190909
Gems version 1.9.1p7
Gems build 67
@avanoostrum avanoostrum changed the title Parser error when 'Check all is answered' is run Parser error when 'Check all is answered' is run [bug] [EMC] Jul 21, 2022
@roelfaber
Copy link
Contributor

The error is only shown in test, not in production. This leads to incomplete updates of assigned tracks without any notice. Workaround: running the recalculation again and again until no further updates are reported.

@roelfaber
Copy link
Contributor

roelfaber commented Jul 21, 2022

Due to sometimes very complicated track logic this might be unavoidable, but at least it should be reported that recalculation was incomplete and needs to be rerun until no further changes are reported.

@mddejong
Copy link
Member

Is this a problem for every installation? My test installation can not even start this process as there are to many answers.

@roelfaber
Copy link
Contributor

The problem is actually that this process fails without a notice or log entry when in production mode. No way to detect if the process has finished or not. It happens regularly in current more complex production projects.
The status finished: false should generate a flag or button to restart this calculation until the status finished: true is reached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants