search

MovingUniverseLab / BAGLE_WebApp

GNU General Public License v3.0
0 stars 0 forks source link

Changing Dec never loads. #2

Open jluastro opened 1 month ago

jluastro commented 1 month ago

Change the declination with the slider to -29 -- things go red and nothing ever loads. And there is no mechanism to see the error messages.

jluastro commented 1 month ago

This was on a PSBL PhotAstrom Param1 with parallax.

Jechen00 commented 1 month ago

This seems to only be a problem on the BAGLE calculator website. I just tried running the webapp locally, and I was able to change the declination slider to -29 without any errors. I did make a couple of pushes to the git repo since the website was deployed, so maybe it needs to be restarted?

Jechen00 commented 1 month ago

This seems to only be a problem on the BAGLE calculator website. I just tried running the webapp locally, and I was able to change the declination slider to -29 without any errors. I did make a couple of pushes to the git repo since the website was deployed, so maybe it needs to be restarted?

We restarted the server that the BAGLE calculator was deployed on and the declination slider seems to be able to go to -29 without any problem now. Although, we weren't able to find out exactly what was causing the error.

Jechen00 commented 1 month ago

This seems to only be a problem on the BAGLE calculator website. I just tried running the webapp locally, and I was able to change the declination slider to -29 without any errors. I did make a couple of pushes to the git repo since the website was deployed, so maybe it needs to be restarted?

We restarted the server that the BAGLE calculator was deployed on and the declination slider seems to be able to go to -29 without any problem now. Although, we weren't able to find out exactly what was causing the error.

The error ended up occurring again and this was what the traceback message looked like in the debug log:

Screenshot 2024-10-04 at 4 05 53 PM

It seems that some time after restart, the machine that the webapp was deployed on had nowhere to send the print messages from BAGLE. We fixed this by directing the stdout into a file, so the error hopefully shouldn't pop up anymore.