Has anyone seen an issue where 'Fetching logs...' on the run page just keeps spinning and spinning?
Keep seeing below in the postgres logs:
could not receive data from client: An existing connection was forcibly closed by the remote host.
03/28/2022, 6:50 PM
03/28/2022, 8:59 PM
Seeing this in the browser:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'nonce-2aca708bb7ff4404be605559c62ec8eb'". Either the 'unsafe-inline' keyword, a hash ('sha256-HqbZ8UK+5BW3a1ynHfiXDhsgSAkyNowYYEHHddL+mqA='), or a nonce ('nonce-...') is required to enable inline execution.
03/28/2022, 9:31 PM
hm I’m skeptical thats related but probably good to fix
does this happen for all runs or just for live monitoring of a fresh run ?
03/29/2022, 11:30 PM
it happens for active runs as well as completed runs