[
https://issues.apache.org/jira/browse/BEAM-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Hulette updated BEAM-11588:
---------------------------------
Status: Open (was: Triage Needed)
> beam_PreCommit_PythonDocs_Cron failing
> --------------------------------------
>
> Key: BEAM-11588
> URL: https://issues.apache.org/jira/browse/BEAM-11588
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Ahmet Altay
> Assignee: Ning Kang
> Priority: P0
>
> Error: 04:13:26 jupyter-client 6.1.10 has requirement jedi<=0.17.2, but you
> have jedi 0.18.0.
> Example Log:
> https://ci-beam.apache.org/job/beam_PreCommit_PythonDocs_Cron/584/console
> It seems like this happened due to a new version of jupyter-client released
> and it is not compatible with jedi 0.18.0 (more here:
> https://github.com/jupyter/jupyter_client/issues/597)
> Attempting to put an upper limit on jupyter-client did not work
> (https://github.com/apache/beam/pull/13709) Because ipykernel installs latest
> version of the jupyter-client first. Current dependency tree looks like
> (omitting unrelated parts):
> ipykernel==5.4.2
> - ipython [required: >=5.0.0, installed: 7.19.0]
> - jedi [required: >=0.10, installed: 0.17.0]
> - jupyter-client [required: Any, installed: 6.1.10]
> - jedi [required: <=0.17.2, installed: 0.17.0]
> Potential solutions:
> - Force install jedi <= 0.17.2
> - Force install jupyter-client <= 6.1.7
> Alos, we can probably remove jupyter-client as an explicit dependency, since
> ipykernel already depends on it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
