sqlalchemy / sqlalchemy/dogpile.cache
better debug logging ?
Open
Nobody has claimed this yet.
feature
low priority
- Dominant language
- Python
- Stars
- 299
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Migrated issue, originally created by jvanasco (jvanasco)
this is really about dogpile/core/dogpile.py , but i figured i'd ask here for the context...
my dev logs look like this:
#!python
2013-02-01 13:29:35,728 DEBUG [dogpile.core.dogpile][Dummy-2] NeedRegenerationException
2013-02-01 13:29:35,728 DEBUG [dogpile.core.dogpile][Dummy-2] no value, waiting for create lock
2013-02-01 13:29:35,728 DEBUG [dogpile.core.dogpile][Dummy-2] value creation lock <dogpile.cache.util.KeyReentrantMutex object at 0x3897fb0> acquired
2013-02-01 13:29:35,728 DEBUG [dogpile.core.dogpile][Dummy-2] Calling creation function
that's great... but it's not helpful.
could the debug calls be extended to include :
- the name of the key ( region would be great too, but i don't think that's as easy )
- the name of the creation function
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in dogpile/core/dogpile.py and inspect the debug calls shown in the issue, along with the surrounding key and creation-function handling. Trace what context is available at each log point, then verify that the debug output identifies the cache key and creation function without losing the existing lock and regeneration messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100