When you request the job log of a running job, you get the log as of that moment. However, when you close that log and re-open it, it seems to open the same log as before. This happens even when the job is further down the line.
It kind of makes it impossible to follow along with a build.
I think VS Code is caching the read-only document, even after closing it. This can probably be circumvented by adding a timestamp to the internal URI, but there might also be some functions to refresh the page.
Maybe it would even be possible to refresh the page automatically, though that would be a feature request taking more effort.
When you request the job log of a running job, you get the log as of that moment. However, when you close that log and re-open it, it seems to open the same log as before. This happens even when the job is further down the line.
It kind of makes it impossible to follow along with a build.
I think VS Code is caching the read-only document, even after closing it. This can probably be circumvented by adding a timestamp to the internal URI, but there might also be some functions to refresh the page.
Maybe it would even be possible to refresh the page automatically, though that would be a feature request taking more effort.