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

Emikat calculation trigger sometimes causes CSIS to crash #166

Open
patrickkaleta opened this issue Jun 23, 2020 · 7 comments
Open

Emikat calculation trigger sometimes causes CSIS to crash #166

patrickkaleta opened this issue Jun 23, 2020 · 7 comments
Assignees
Labels

Comments

@patrickkaleta
Copy link

patrickkaleta commented Jun 23, 2020

Following the CSIS acceptance tests, there were reports (1, 2) of an error after clicking the "Trigger calculations" button for the first time, which resulted in a WSOD.

Cause: Unclear yet. It doesn't happen for all studies. Users who run into this error, can still be able to successfully trigger the calculations in another study.

@patrickkaleta patrickkaleta self-assigned this Jun 23, 2020
@patrickkaleta
Copy link
Author

Since the csis_helpers module is involved in the triggering, I will first look into the module.

@p-a-s-c-a-l
Copy link
Member

Can we close this issue?

@DenoBeno
Copy link

DenoBeno commented Aug 8, 2020

I have never encountered this issue. At least not lately...

@patrickkaleta
Copy link
Author

AFAIK this happened only twice (once to Drazen and once to Julia during the AIT testing sessions). It's a severe error (EmikatID doesn't get stored in CSIS even though it is created in Emikat), which renders the complete Study useless. But I haven't been able to reproduce this issue.

@patrickkaleta
Copy link
Author

Since the csis_helpers module is involved in the triggering, I will first look into the module.

The csis helpers module doesn't seem to be responsible for this one.

@patrickkaleta
Copy link
Author

Closing this issue, since we were unable to reproduce this error.

@patrickkaleta
Copy link
Author

Happened again yesterday to @claudiahahn in Study 212. Reason for this issue remains unclear.

Fixed for this particular Study by manually adding the missing Szenario ID.

@patrickkaleta patrickkaleta reopened this Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants