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

"Server Error!" but no details #28

Open
mr-c opened this issue Dec 11, 2023 · 3 comments
Open

"Server Error!" but no details #28

mr-c opened this issue Dec 11, 2023 · 3 comments

Comments

@mr-c
Copy link

mr-c commented Dec 11, 2023

Workflow run fails without actionable error message, just "Server Error!"

To Reproduce

  1. Go to https://krini.rahtiapp.fi/run
  2. Workflow URL: https://github.com/common-workflow-language/common-workflow-language/raw/main/v1.0/v1.0/conflict-wf.cwl
  3. Workflow parameters
{
  "input_1" : "Hello World",
  "input_2" : "How are you?"
}
  1. Submit

Expected behavior
Success, or at least a helpful error message

Desktop (please complete the following information):

  • OS: Debian GNU/Linux
  • Browser: Firefox
  • Version: 120.0.1 (64-bit)
@mr-c
Copy link
Author

mr-c commented Dec 11, 2023

Checking https://krini.rahtiapp.fi/manage also results in "Server error!" and no details

image

@uniqueg
Copy link
Member

uniqueg commented Dec 11, 2023

Thanks for reporting, @mr-c. Just FYI, I think we are right in the middle of a rewrite and didn't really think people would currently use it. But we should at least put a banner to mention this.

@git-anurag-hub: Could you please put a banner on Krini to inform people that Krini is very experimental and may not work or may stop working at any time, at this point? Not sure how best to do that, given that it is really a deployment-specific banner, rather than something that should be made available in the code base. Do you have any ideas?

Also, we should make sure that the WES and TES components give the best possible error messages (although I'm afraid we will be limited by what the specs give us here, which is basically just SYSTEM_ERROR or EXECUTION_ERROR - possibly optionally more, if the implementations further specify that).

@anuragxxd
Copy link
Member

Sure @uniqueg, will look into it!

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

No branches or pull requests

3 participants