ipsilon

#584 Recovered: debug call_location is using wrong stack frame
Closed: Fixed by t0xic0der. Opened by t0xic0der.

Closed: Fixed
Reopen Issue

In ipsilon/util/log.py the function call_location() is returning the wrong information. The debug output is supposed to show the file and line number where the debug message was emitted from. It appears one call level got added somehow (e.g. now there is one extra stack frame).

    frame = inspect.stack()[2]

needs to be changed to 

    frame = inspect.stack()[3]

This is important to fix because when debugging it's really helpful to match a debug message to the code location that emitted it.

This issue ticket was originally removed from the tracker as it clashed with the pull request.
See upstream ticket for migration details.

Metadata Update from @t0xic0der:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.