Fiddlesticks when trying to view a log file
- Target version set to Bug Triage
- Target version changed from Bug Triage to Arvados Future Sprints
This is probably an effective duplicate of #7008. Workbench's log viewer code assumes it gets back a collection with something in it. If it stops doing that, it will handle all kinds of corner cases: no permissions, collection is gone, and more.
Last comment seems misinformed. The job log record indicates that it wrote a real log with real contents. qr1hi just doesn't have a collection with that content address. It might've been modified after the fact? That'd be unusual, but definitely possible.
- Status changed from New to Closed
Also available in: Atom