Has anyone seen an issue where 'Fetching logs...' ...
# ask-community
b
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.
a
what version?
b
0.14.6
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.
a
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 ?
b
it happens for active runs as well as completed runs
a
hmmmmm
Can you download a debug file successfully for the run? Here is a new tracking issue, if you could add details about your set-up https://github.com/dagster-io/dagster/issues/7240