hpc / hpc/libcircle

Objects processed messages during run

Open
#43 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
100
Forks
33
PR merge metrics
No merged PRs in 30d

Description

I started using libcircle again. When I used this in June 2021 I would get messages like this in the log during a run...

1624401087:0:libcircle/token.c:207:Objects processed: 76456492 ...
1624401099:0:libcircle/token.c:207:Objects processed: 77419312 ...
1624401111:0:libcircle/token.c:207:Objects processed: 78430963 ...
1624401134:0:libcircle/token.c:207:Objects processed: 79577820 ...
1624401146:0:libcircle/token.c:207:Objects processed: 81504253 ...
1624401155:0:libcircle/token.c:207:Objects processed: 82556239 ...
1624401166:0:libcircle/token.c:207:Objects processed: 83496932 ...

These messages are now not appearing. In the code I see they are ate log level INFO. I still get the summary at the end with the number processed for each rank and then the total objects processed. This is also at log level INFO. What do I need to do to get these messages appearing again ? I have a python script that draws a graph of progress over time from these messages which is really useful so really want to get this functionality back.

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.

Research direction

Start at libcircle/token.c:207 and inspect how INFO-level progress messages are emitted and configured, then compare that path with the end-of-run summary logging. Reproduce a run with the current logging settings and verify that periodic “Objects processed” messages appear again so the progress graph can consume them.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.