[
https://issues.apache.org/jira/browse/BEAM-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121871#comment-17121871
]
Kenneth Knowles commented on BEAM-8322:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Log when artifacts can't be fetched on startup
> ----------------------------------------------
>
> Key: BEAM-8322
> URL: https://issues.apache.org/jira/browse/BEAM-8322
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-harness
> Reporter: Kyle Weaver
> Assignee: Kyle Weaver
> Priority: P3
> Labels: stale-assigned
>
> I noticed when I was testing my new artifact retrieval service:
> While I'm sure artifact retrieval is the cause of error, there is nothing in
> the logs at all to indicate that.
>
> EDIT: I realized the root cause might be because I wasn't returning an
> artifact response, making the client wait forever. There should probably be
> timeouts for that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
