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

Error handling #8

Open
TNanukem opened this issue Mar 31, 2020 · 1 comment · Fixed by #14
Open

Error handling #8

TNanukem opened this issue Mar 31, 2020 · 1 comment · Fixed by #14
Assignees
Labels
enhancement New feature or request

Comments

@TNanukem
Copy link
Owner

The platform should delete algorithms that generate an error in order to keep the file system clean. Also, there are improvements to be made on how to show the researcher that an error happened.

@TNanukem TNanukem added the enhancement New feature or request label Jun 7, 2020
@TNanukem TNanukem self-assigned this Jun 7, 2020
@TNanukem TNanukem reopened this Jul 1, 2020
@TNanukem
Copy link
Owner Author

TNanukem commented Jul 1, 2020

The algorithm still not deleted because by some reason, when the error algorithm achieves the feature phase, even tough the correct algorithm took the semaphore and is running, the correct algorithm throws an error because of the name of the archive that ends up with an extra .java in it.

I'm not sure why this error happen, since this .java only appears when the error algorithm has it's auxList made before the semaphore is taken. Maybe blocking the entire for loop, not only the simulation would solve it, however, this seems overly complicated to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant