aws / aws/graph-notebook

[BUG] Error in 01-SBOM-Dependency-Analysis when installing nodestream-plugin-neptune

Open
#588 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Jupyter Notebook
Stars
819
Forks
179
PR merge metrics
No merged PRs in 30d

Description

**Community Note**
* Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
* If you are interested in working on this issue or have submitted a pull request, please leave a comment.

**Describe the bug**
Running the new SBOM notebooks on a Notebook (using Python 3 kernel) created on April 15th, I received the following errors on `01-SBOM-Dependency-Analysis`:
```
!pip install -q pyyaml nodestream-plugin-neptune nodestream_plugin_sbom

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
autovizwidget 0.21.0 requires pandas<2.0.0,>=0.20.1, but you have pandas 2.2.2 which is incompatible.
awscli 1.32.78 requires botocore==1.34.78, but you have botocore 1.34.51 which is incompatible.
graph-notebook 4.2.0 requires pandas<=1.5.3,>=1.3.5, but you have pandas 2.2.2 which is incompatible.
hdijupyterutils 0.21.0 requires pandas<2.0.0,>=0.17.1, but you have pandas 2.2.2 which is incompatible.
sparkmagic 0.21.0 requires pandas<2.0.0,>=0.17.1, but you have pandas 2.2.2 which is incompatible.
```
- OS: [e.g. Amazon Linux 2]
- Browser: Google Chrome
- Graph Notebook Version: 4.2.0
- Graph Database & Version: Amazon Neptune Analytics (v1.1.1712198926)

**To Reproduce**
Steps to reproduce the behavior:
1. Open the SBOM notebooks on a freshly created Notebook
2. Run the `!pip install -q pyyaml nodestream-plugin-neptune nodestream_plugin_sbom` command
3. See error

**Expected behavior**
The command should complete successfully.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.