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

Information about errors on benchmarking is not printed anywhere except the console. #158

Open
VirtualAkseli opened this issue Apr 30, 2021 · 0 comments
Labels
Tech debt Technical debt

Comments

@VirtualAkseli
Copy link
Collaborator

VirtualAkseli commented Apr 30, 2021

Technical debt table
Description The only place where errors are printed, if e.g. the molecule has been created incorrectly, is the console. This information is vital to the user, if the user can not be sure about what configurations work and what do not.
Alternatives Creating a separate view for handling errors and fetching possible error messages to django messages -system .
Rationale If the user does not understand the initialization of molecules, the syntax might pass, but the benchmark will not. In other words, the web-application lets one make error causing mistakes.
@VirtualAkseli VirtualAkseli added the Tech debt Technical debt label May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tech debt Technical debt
Projects
None yet
Development

No branches or pull requests

1 participant