Add example for duplicate-bases message documentation

[gunungpw]

Co-authored-by: Vladyslav Krylasov vladyslav.krylasov@gmail.com

• Write a good description on what the PR does.
• If you used multiple emails or multiple names when contributing, add your mails
  and preferred name in script/.contributors_aliases.json

Type of Changes

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

Description

add code example for duplicate-bases
add python traceback error message
add Issue Tracker link

Ref #5953

[DanielNoord]

Thanks again @gunungpw

[gunungpw]

Any advice why Checks / documentation (pull_request) fail? I am new to programing and Github 😄

[coveralls]

Pull Request Test Coverage Report for Build 2076268437

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.308%

---

Totals
Change from base Build 2072955906:	0.0%
Covered Lines:	15459
Relevant Lines:	16392

---

💛 - Coveralls

[DanielNoord]

@gunungpw I'm scared it might be due to #6060.

If you want to fix it you would likely need to look for the add_message calls that have "duplicate-bases" as their first argument. Then figure it by which visit_... or leave_... method (I guess visit_classdef) they get called and check if duplicate-bases is in their check_messages decorator. I know that is quite a lot so if you have trouble figuring this out let me know and I can take a look myself!

[gunungpw]

@gunungpw I'm scared it might be due to #6060.

If you want to fix it you would likely need to look for the add_message calls that have "duplicate-bases" as their first argument. Then figure it by which visit_... or leave_... method (I guess visit_classdef) they get called and check if duplicate-bases is in their check_messages decorator. I know that is quite a lot so if you have trouble figuring this out let me know and I can take a look myself!

I learned a lot today, the issue may be a bit too complex for me.
Hope you have a nice day

[DanielNoord]

@gunungpw I'm scared it might be due to #6060.
If you want to fix it you would likely need to look for the add_message calls that have "duplicate-bases" as their first argument. Then figure it by which visit_... or leave_... method (I guess visit_classdef) they get called and check if duplicate-bases is in their check_messages decorator. I know that is quite a lot so if you have trouble figuring this out let me know and I can take a look myself!

I learned a lot today, the issue may be a bit too complex for me. Hope you have a nice day

@Pierre-Sassoulas Actually already fixed it by adding the comment. 😄

[Pierre-Sassoulas]

Thank you for the contribution @gunungpw , and congratulation on becoming a contributor !