GarbageCleaner should log pool names, not Python pool object ids

Open
#175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
observability

Research direction

Start by locating the GarbageCleaner implementation and the log statement that includes the pool object representation. Confirm how the pool name is exposed, then verify that cleanup messages identify pools by name rather than Python object ids using the project's relevant logging or test workflow.

Written by the indexing model from the issue text.

Description

see strings like: <resallocserver.manager.Pool object at 0x7ff5b9dea5f0>

 INFO 2025-07-21 15:37:41,963 PID:996054:140692659631808(GarbageCleaner-<resallocserver.manager.Pool object at 0x7ff5bbb165f0>) Cleaning unused resources in copr_hv_ppc64le_01_dev pool
 INFO 2025-07-21 15:37:42,024 PID:996054:140692651239104(GarbageCleaner-<resallocserver.manager.Pool object at 0x7ff5b9dea5f0>) Cleaning unused resources in copr_hv_ppc64le_02_dev pool
Dominant language
Python
Stars
11
Forks
8
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from praiskup/resalloc

All issues in praiskup/resalloc

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.