all-in-one batch file with select menu to:
- check for updates only
- check and git pull updates
- fix broken updates/branch
- hard reset/wipe (removes: tracked, untracked, modified, discard staged, not pushed commits, .gitignore)
- info about current stage: what is modified, untracked and ignored
-no pager for long git outputs to prevent breaking
- reworked and combined build tools and msvc checks
- removed PATH check for msvc tools, not mandatory for triton
- removed split suffix/prefix search, causes false positives
- simplified search via vswhere for build tools and vs components
-prints build tools version same as before, but no msvc info,
unless req. component is missing, that includes; cmake tools, clang compiler, msvc build tools, windows sdk
## Summary
Fixed incorrect type hint syntax in `MotionEncoder_tc.__init__()` parameter list.
## Changes
- Line 647: Changed `num_heads=int` to `num_heads: int`
- This corrects the parameter annotation from a default value assignment to proper type hint syntax
## Details
The parameter was using assignment syntax (`=`) instead of type annotation syntax (`:`), which would incorrectly set the default value to the `int` class itself rather than annotating the expected type.
If this suffers an exception (such as a VRAM oom) it will leave the
encode() and decode() methods which skips the cleanup of the WAN
feature cache. The comfy node cache then ultimately keeps a reference
this object which is in turn reffing large tensors from the failed
execution.
The feature cache is currently setup at a class variable on the
encoder/decoder however, the encode and decode functions always clear
it on both entry and exit of normal execution.
Its likely the design intent is this is usable as a streaming encoder
where the input comes in batches, however the functions as they are
today don't support that.
So simplify by bringing the cache back to local variable, so that if
it does VRAM OOM the cache itself is properly garbage when the
encode()/decode() functions dissappear from the stack.
When the VAE catches this VRAM OOM, it launches the fallback logic
straight from the exception context.
Python however refs the entire call stack that caused the exception
including any local variables for the sake of exception report and
debugging. In the case of tensors, this can hold on the references
to GBs of VRAM and inhibit the VRAM allocated from freeing them.
So dump the except context completely before going back to the VAE
via the tiler by getting out of the except block with nothing but
a flag.
The greately increases the reliability of the tiler fallback,
especially on low VRAM cards, as with the bug, if the leak randomly
leaked more than the headroom needed for a single tile, the tiler
would fallback would OOM and fail the flow.
prints "HIP_PATH" at the very top,
and all defined "HIP_PATH_xx" paths
optional print under Build Tools with check for MSVC in PATH,
assuming default path:
<drive>\<program files>\Microsoft Visual Studio\<year>\BuildTools\VC\Tools\MSVC\<version>\bin\Hostx64\x64
