[Bug]

[caseyjlaw]

🐞 Bug Report

Describe the bug

Submitting to the transient upload feature produces a 500 error

---

Is this a regression?

I believe this worked for me, but have not used the service for some time. Perhaps related: My account was modified yesterday to use a new authentication system.

---

To Reproduce

1. Go to "Upload Transients" page
2. Enter a row, such as SE01_AT2020arh, 359.7390417, 18.21551389, None, None (for a simple RA, Dec transient)
3. 500 error

---

Expected behaviour

• It should submit the job to a queue, presumably?

---

Media prove

---

Your environment

• OS: OSX
• Browser name and version: Firefox 139

[manning-ncsa]

Thanks for reporting this. Your identity provider switch is coincidental. A 500 error nearly always indicates a problem with the server itself. In this case, it appears to be another failure related to an ongoing networking issue on our computing host platform (Jetstream2). We are in the process of finding a permanent resolution to this issue, but until we do, we expect to experience random service disruptions. I will report back when service has been restored.
(By the way, I moved the issue to a discussion because this is not an issue with the Blast application per se).

[manning-ncsa]

@caseyjlaw Services are back online, and so you should try adding your transient again. The Jetstream2 admin that has been working with us on this issue believes he has identified the underlying cause. He has applied a patch that will hopefully prevent this from recurring, and he also submitted a bug report to the upstream software project uncovered by this situation. This is a great example of how open source software gets better 👍

@djones1040

[djones1040]

thanks Andrew! note: if it still doesn't work, remove the spaces (and lmk if that was the issue)

[caseyjlaw]

Thanks. I resubmitted and still saw a 500 error. I removed the spaces and it worked. Are spaces not allowed in csv?

[manning-ncsa]

So the networking problems were just coincidental? That's funny.

CSV is not a strictly defined format, but we should handle common variations like surrounding whitespace. Looks like this warrants an issue after all! I'll create one about improving the CSV parsing.

[manning-ncsa]

#337