#985 closed enhancement (fixed)
Misleading metadata processing log message
| Reported by: | Rodrigo Rodrigues da Silva | Owned by: | |
|---|---|---|---|
| Priority: | trivial | Milestone: | 0.8.0 |
| Component: | programming | Keywords: | |
| Cc: | Parent Tickets: |
Description
After some medium is processed one gets the following message:
2014-10-17 10:24:05,320 DEBUG [mediagoblin.tools.processing] No processing callback for <MediaEntry 34: Aula1>
While developing/debugging a plugin I got this message and found it very confusing. Looking at the source code I'm convinced this message should read something like No metadata processing callback for <MediaEntry 34: Aula1>
Patch provided.
Attachments (1)
Change History (4)
by , 11 years ago
| Attachment: | issue_985.patch added |
|---|
comment:1 by , 11 years ago
| Status: | new → review |
|---|
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | review → closed |

I agree, this message wasn't very clear. I merged your patch, then added a bit further clarification. "Processing Metadata" is a bit inconsistent with our later uses of the term metadata, but this happened before then. Basically this was just an indicator of whether or not there's a webhook to call.
Anyway, I adjusted the phrasing to:
_log.debug('No processing callback URL for {0}'.format(entry))and
_log.debug('Sending processing callback for {0} to {1}'.format( entry, url))That should be a lot clearer.