[
https://issues.apache.org/jira/browse/BEAM-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Weaver updated BEAM-8322:
------------------------------
Description:
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.
was:
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.
> 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: Minor
>
> 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)
