opengeospatial/teamengine

Download log Files broken?

Closed this issue · 9 comments

Describe the bug
Download log Files results in a blank page now

To Reproduce
Try to Download log Files from a completed OGC API - Features test
e.g. https://cite.opengeospatial.org/teamengine/downloadLog?session=s0001 in this case

Expected behavior
Downloading the log files.

Thank you for reporting.
I am able to reproduce your problem.
We will do further analysis.

@jerstlouis Can you please check if the problem is still occurring? It might have been related to problems with the environment back then which are solved by now.

@dstenger This issue is still happening.

Clicking https://cite.opengeospatial.org/te2/viewSessionLog.jsp?session=s0004 after being logged in returns a blank file.

@jerstlouis Thank you for reporting back. Is this error occurring with all your sessions? Did you also try out other test suites than OGC API Features tests?

@dstenger Sorry I corrected the link in my last comment, I meant the original link in the issue still returns a blank file.
I do get this problem with all sessions (e.g. https://cite.opengeospatial.org/teamengine/downloadLog?session=s0006) even though that session does work. I don't know if such URLs are still valid now?

However I was now able to Click the "Download log Files" for my session 6 from the viewOldSessionLog URL clicking "detailed old test report". I did not try other test suites.

https://cite.opengeospatial.org/te2/viewOldSessionLog.jsp?session=s0006 also returns a 500 when not logged in instead of a 401 or 404 as it should:

HTTP Status 500 - java.lang.NullPointerException

@dstenger I was able to replicate the 500 error issue on te2. Attempting to access the viewOldSessionLog page returns an HTTP 500 error. This happens on all my sessions too. See the attached screenshot for the error message.

Screenshot 2022-02-15 at 08 02 35

@jerstlouis Today (2022-02-21) we confirmed that the Download Log Files mechanism works. May we close this GitHub issue?

The viewOldSessionLog problems will be reported as separate issues.

Thank you @ghobona and @dstenger . Closing the issue.

I created two new issues as announced by @ghobona: