Fix pylint issues in azure-eventhub-checkpointstoreblob

[Copilot]

This PR addresses pylint warnings in the azure-eventhub-checkpointstoreblob library when running with pylint 3.3.6. The changes focus on proper exception logging practices according to the Azure SDK guidelines.

The following issues were fixed:

1. C4766 (do-not-log-exceptions-if-not-debug) - Changed log level from warning to debug in two locations:

   • In _claim_one_partition method to ensure exceptions are only logged at debug level
   • In list_ownership method to prevent potentially sensitive information from being logged at higher levels

2. C4762 (do-not-log-raised-errors) - Fixed in list_ownership method:

   • Changed log level for the re-raised exception from warning to debug

These changes reduce the chance of exposing sensitive information in logs and follow the best practices as described in the Python logging sensitive information documentation.

Fixes #40744.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[l0lawrence]

I'm not sure do-not-log-raised-errors is resolved

[Copilot]

I'm not sure do-not-log-raised-errors is resolved

Good catch! I've fixed the issue by removing the logging statement before re-raising the exception in the list_ownership method, which properly addresses the C4762 (do-not-log-raised-errors) rule. Commit f831d8f includes this fix.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• azure.github.io
  • Triggering command: curl -s REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

[swathipil]

would it be better to make this a debug log rather than removing it altogether?

[Copilot]

Good suggestion! I've restored the debug logging for exceptions in the list_ownership method while still maintaining compliance with the C4762 rule (do-not-log-raised-errors) by using the debug level. You can see this change in commit e516b70.