Digitaljs_online sometimes stops responding
PythonLinks opened this issue · 6 comments
It will not synthesize my code, nor your examples.
I am at a stage where it would be very interesting if your demo would also say how large a circuit is.
Ideally luts, or even transistors would be helpful.
Chris
I have the same issue.
If I load one example (SR Latch for example) and click "Synthetize and simulate!", nothing happens.
Opening the brower network panel, It seems that the target api url is wrong.
HTTP/1.1 502 Bad Gateway
Server: nginx/1.18.0
Date: Sat, 05 Aug 2023 22:20:12 GMT
Content-Type: text/html
Content-Length: 157
Connection: keep-alive
Strict-Transport-Security: max-age=31536000
Restarted the service again. It looks like someone is abusing the service and triggering the OOM killer.
I am at a stage where it would be very interesting if your demo would also say how large a circuit is.
Ideally luts, or even transistors would be helpful.
This is technology-dependent, and DigitalJS doesn't work at that level right now.
Reopening as it would be good if the site was able to survive Yosys death.
I'm experiencing same issue now.
I have the same issue.
If I load one example (SR Latch for example) and click "Synthetize and simulate!", nothing happens.
Opening the brower network panel, It seems that the target api url is wrong.
HTTP/1.1 502 Bad Gateway Server: nginx/1.18.0 Date: Sat, 05 Aug 2023 22:20:12 GMT Content-Type: text/html Content-Length: 157 Connection: keep-alive Strict-Transport-Security: max-age=31536000
For now, I have added auto-restarting in the systemd configuration. Hope it helps.
I've now introduced a request limit (per IP) and a connection limit (for the entire server). This might reduce the service's responsiveness, but it may help with the lockups. The root cause of the lockups is still unknown.