hide unneeded logging messages

[pjuergens]

Please confirm that this PR has done the following:

- [ ] Tests Added
- [ ] Documentation Added
- [ ] Name of contributors Added to AUTHORS.rst

• Description in RELEASE_NOTES.md Added

Description of PR

Fixed unnecessary internal logging messages when aggregating recursively, see Issue #545

closes #545

[codecov]

Codecov Report

Merging #546 (b03658f) into main (0989fdd) will increase coverage by 0.0%.
The diff coverage is 100.0%.

@@          Coverage Diff          @@
##            main    #546   +/-   ##
=====================================
  Coverage   93.6%   93.6%           
=====================================
  Files         48      48           
  Lines       5285    5288    +3     
=====================================
+ Hits        4947    4950    +3     
  Misses       338     338           

Impacted Files	Coverage Δ
pyam/aggregation.py	99.1% <100.0%> (ø)
pyam/core.py	92.6% <100.0%> (ø)
pyam/logging.py	59.3% <100.0%> (+2.7%)	⬆️
tests/test_feature_aggregate.py	98.8% <100.0%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0989fdd...b03658f. Read the comment docs.

[danielhuppmann]

Nice work, thanks @pjuergens!

Two requests:

• Please change the description of this PR to use the GitHub-keyword closes, ie add the phrase "closes Warnings in recursive-aggregation #545". Then, GitHub will automatically close the related issue when this PR is merged.
• (optional) Using an underscore in the module name was a bad idea. Could you refactor the module name from _aggregate to aggregation in this PR?

[pjuergens]

Well, most of the work was yours :) I did the refactoring and hope that all the tests will run through now :)

[pjuergens]

@danielhuppmann do you know why some tests are failing now? They seem to be in parts of the code where I didn't change anything

[danielhuppmann]

Well, most of the work was yours :) I did the refactoring and hope that all the tests will run through now :)

Well, I think this is a good mode of operation: you (or other intermediate-expert users) identify an issue, receive some guidance from admins like me, then make a PR fixing this...

About the issue, the IIASA database crashed before lunch, so the unit tests checking the iiasa.Connection module failed. I restarted the tests, everything passes now. Ready for review?

PS: there is a skip-if-IIASA-db-API-fails decorator if it cannot be reached entirely, but I guess this doesn't work when the database times out (rather than being offline)...

pyam/tests/conftest.py

Line 17 in 0989fdd

# verify whether IIASA database API can be reached, skip tests otherwise

[danielhuppmann]

Thanks @pjuergens for doing some clean-up of the codebase beyond your immediate issue!