-
Notifications
You must be signed in to change notification settings - Fork 115
UI using Windows (Chrome/Firefox) doesn't load job results. #133
Comments
Hi there! We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created. The current status is as follows:
This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes. |
I am also experiencing this issue. I think I've narrowed it down somewhat. First, some background: At my workplace, each machine is accessible as I can GET both http://localhost:8080/teams/main/pipelines/hello-world/jobs/hello-world/builds/2 and http://mycompany.griffy:8080/teams/main/pipelines/hello-world/jobs/hello-world/builds/2 in my browsers (Chrome/Firefox) on Windows. I can also GET the relevant To make things more interesting, my coworker who uses a Mac is able to GET http://mycompany.griffy:8080/api/v1/builds/2/events with no issues. The problem seems to happen solely on Windows browsers only when not accessing the event-stream via localhost. Finally, there is one more interesting bit to all of this: If I ssh into the VM and It's as if the interrupt is triggering some kind of flush, but where in the stack that flush is happening I'm not sure... |
I have confirmed the behavior we are experiencing at my workplace is not a bug with For people who might come across this issue looking for solutions, what we ended up doing as a quick workaround was running a simple proxy server (https://github.com/nodejitsu/node-http-proxy) on our Windows boxes that proxies traffic from 127.0.0.1 to the concourse web server so that the browsers will see a loopback address and be "fooled" into working correctly. If someone finds a better solution or is able to pinpoint the true issue, please let me know! |
Moved to concourse/concourse#1125 |
Running the ATC on linux 64bit using standalone binary.
Web UI hangs loading job status using both Firefox and Chrome from Windows systems.
The text was updated successfully, but these errors were encountered: