Skip to content

chore: resolve pylint unsubscriptable object issue#485

Merged
nathanwn merged 1 commit into
stagingfrom
resolve-pylint-issue
Sep 25, 2023
Merged

chore: resolve pylint unsubscriptable object issue#485
nathanwn merged 1 commit into
stagingfrom
resolve-pylint-issue

Conversation

@nathanwn

Copy link
Copy Markdown
Member

For some reason, pylint suddenly started to report the following issue, which is causing our CI to fail.

src/macaron/slsa_analyzer/checks/provenance_l3_check.py:360:39: E1136: Value 'provenance_payload.statement' is unsubscriptable (unsubscriptable-object)

I am pretty sure this is a false positive. I have simplified the code causing the issue to resolve it.

Signed-off-by: Nathan Nguyen <nathan.nguyen@oracle.com>
@oracle-contributor-agreement oracle-contributor-agreement Bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Sep 24, 2023
@nathanwn nathanwn marked this pull request as ready for review September 24, 2023 23:52

@behnazh-w behnazh-w left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's very strange. Pylint hasn't been updated since July 26th, so I doubt it's related to Pylint itself. Let's merge this PR to allow the CI pipelines work for now. I will look into the root cause separately.

@behnazh-w

Copy link
Copy Markdown
Member

This error seems to be related to a regression in Astroid 2.15.7. See this issue.

@nathanwn nathanwn merged commit 93429e7 into staging Sep 25, 2023
@nathanwn nathanwn deleted the resolve-pylint-issue branch September 25, 2023 23:23
art1f1c3R pushed a commit that referenced this pull request Nov 29, 2024
Signed-off-by: Nathan Nguyen <nathan.nguyen@oracle.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants