autour_de_minuit/blender-asset-tracer
8
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

3 Releases 40 Tags

RSS Feed
  • 1.23 61aa7d34d6

    1.23 Stable

    joseph.henry released this 2026-04-28 15:29:02 +02:00 | 0 commits to main since this release

    What's new

    Every .zip produced by blender_asset_tracer.pack.zipped.ZipPacker now contains a top-level bat-debug.log capturing the full DEBUG-level trace of the pack run. Archives are self-describing — you no longer need terminal output to debug what BAT found, where it rewrote paths to, which files were missing, or which references resolved to where.

    What's captured

    • Banner: BAT version, UTC timestamp, blend file(s), project root, target, noop / relative_only / keep_hierarchy flags, sys.argv, Python version, platform.
    • Trace phase: every block expansion, every Resolved / Resolving line, every Missing file warning, library load failures.
    • Pack phase: every ZIP src → dst line for files copied (compressed and stored), every path-rewrite update inside blend files.
    • Closing: a BAT Pack closing; flushing debug log to bat-debug.log line confirming the buffer was flushed cleanly.

    Usage

    # After producing a pack
unzip -p mypack.zip bat-debug.log | less

# Or extract just the log
unzip -p mypack.zip bat-debug.log > pack.log

    Notes

    • The capture is independent of CLI verbosity — -q still keeps the terminal quiet while the in-zip log stays at DEBUG. No flag needed; it's always on for zip targets.
    • noop mode skips the log embedding (no zip is written).
    • KeyboardInterrupt and FileTransferError paths still flush whatever was logged up to the abort point.
    • Adds ~10–15 MB to a typical production pack; negligible vs. the multi-GB asset payload.
    • Only ZipPacker is affected — filesystem, S3, and Shaman packers are unchanged.
    Downloads