Fix crash when a slice object is called

[zenlyj]

Type of Changes

	Type
✓	🐛 Bug fix
	✨ New feature
	🔨 Refactoring
	📜 Docs

Description

Add a runtime type guard before accessing qname() on inferred called function for both prefer-typing-namedtuple and consider-math-not-float checks.

Closes #10708

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.98%. Comparing base (133681e) to head (d9988c0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #10715   +/-   ##
=======================================
  Coverage   95.98%   95.98%           
=======================================
  Files         176      176           
  Lines       19540    19540           
=======================================
  Hits        18755    18755           
  Misses        785      785           

Files with missing lines	Coverage Δ
pylint/extensions/code_style.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Pierre-Sassoulas]

I think it's okay to pre-filter, maybe we don't have to filter anymore after that ? (It's not the first crash that the fuzzing caught by using slice instead of functiondev/classdef, maybe we can anticipate other instances of that without waiting for "random luck"). Maybe by creating a safe_infer_call function ?

[Pierre-Sassoulas]

Suggested change

	if not called:
	return
	if not (called and isinstance(called, (nodes.FunctionDef, nodes.ClassDef))):
	return

[zenlyj]

Good point with the safe_infer_call, it seems that there are a number of usages where we infer call and access qname. I will put out a separate PR for that change.

[Pierre-Sassoulas]

Great !

[github-actions]

🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉

This comment was generated for commit d9988c0