#j#dZddlmZddlZddlZddlZddlZddlZddlZddl m Z ddl m Z ddl mZejeZdd Zd d ZGd d eZd dZdZd dZd!dZd"dZd"dZd#d$dZdS)%uManaged uv — one path, no guessing. Hermes owns its own uv binary at ``$HERMES_HOME/bin/uv`` (or ``uv.exe`` on Windows). Every code path that needs uv resolves it from that single location. If the binary is missing, ``ensure_uv()`` bootstraps it via the official standalone installer with ``UV_UNMANAGED_INSTALL`` / ``UV_INSTALL_DIR`` pointed at ``$HERMES_HOME/bin`` so the installer writes directly there — no PATH probing, no conda guards, no multi-location resolution chains. ) annotationsN)Path)Optional)get_hermes_homereturnrclt}tjdkr|dz dz S|dz dz S)uReturn the path where Hermes keeps *its* uv binary. ``$HERMES_HOME/bin/uv`` on POSIX, ``$HERMES_HOME\bin\uv.exe`` on Windows. The directory may not exist yet — callers should use ``ensure_uv()`` to bootstrap it. Windowsbinzuv.exeuv)rplatformsystem)homes :/home/ubuntu/.hermes/hermes-agent/hermes_cli/managed_uv.pymanaged_uv_pathrs@   DI%%e|h&& %<$  Optional[str]ct}|r.tj|tjrt |SdS)ubReturn the managed uv path if it exists, else ``None``. No side effects — pure lookup. N)ris_fileosaccessX_OKstr)ps r resolve_uvr+sD Ayy{{ryBG,,1vv 4rc8eZdZUdZded<d d fd Zd ZxZS) _UvResultu``ensure_uv()`` return value that survives an update boundary. ``ensure_uv()``'s arity has flipped between a single path string and a ``(path, fresh_bootstrap)`` tuple across releases. ``hermes update`` runs the call site from the *old*, already-imported ``hermes_cli.main`` against this *freshly pulled* module, so the two can disagree on how many values ``ensure_uv()`` returns. An install parked on a 2-tuple release runs ``uv_bin, fresh_bootstrap = ensure_uv()`` against the single-value module and crashes the first update: the returned path is a plain ``str``, which is itself iterable, so the 2-target unpack walks its characters and raises ``ValueError: too many values to unpack (expected 2)`` (and on the failure path the ``None`` return raises ``TypeError: cannot unpack non-iterable NoneType``). This wrapper answers to both conventions: uv_bin = ensure_uv() # behaves as the path str ("" when absent) uv_bin, fresh = ensure_uv() # unpacks as (path|None, fresh_bootstrap) Missing uv is the empty string (falsy) instead of ``None`` so legacy 2-target call sites can still unpack a failure without raising, while ``if not uv_bin`` keeps working for single-value callers. POSIX only. This wrapper is **never** returned on Windows — see ``ensure_uv()`` for why the ``__iter__`` override is unsafe there. boolfresh_bootstrapFpathrfreshr '_UvResult'c^t||pd}||_|S)N)super__new__r)clsrr self __class__s rr%z_UvResult.__new__Rs+wwsDJB//$ rcLtt|pd|jfSN)iterrr)r's r__iter__z_UvResult.__iter__Ws%c$ii'4$*>?@@@r)F)rrr rrr!)__name__ __module__ __qualname____doc____annotations__r%r, __classcell__)r(s@rrr6sr2 AAAAAAArrc"t}|r|St}|jddt d|jd t |nE#t $r8}td|t d|Yd}~dSd}~wwxYwt}|rEtj |dgddd j }t d |d nt d |S)zQResolve the managed uv path, installing it if necessary (plain ``str``/``None``).T)parentsexist_oku! → Installing managed uv into z ...zManaged uv install failed: %su$ ✗ Failed to install managed uv: N --versionFcapture_outputtextchecku ✓ Managed uv installed ()uA ✗ Managed uv install appeared to succeed but binary not found) rrparentmkdirprint _install_uv Exceptionloggerwarning subprocessrunstdoutstrip)existingtargetexcresultversions r_ensure_uv_pathrL^sF||H   F Mt444 Afm A A ABBBF 6<<< :S::;;;ttttt \\F S. [ !      7W7778888 QRRR MsA&& B(0-B##B(cnt}tjdkr|St|S)uReturn the managed uv path, installing it first if necessary. On **POSIX** the result is a :class:`_UvResult` (a ``str`` subclass) that is both usable directly as the path *and* unpackable as ``(path, fresh_bootstrap)`` for older call sites parked on a 2-tuple release — see :class:`_UvResult` for the update-boundary rationale. On **Windows** we deliberately return a plain ``str``/``None`` instead. ``subprocess`` there serializes the argv via ``subprocess.list2cmdline``, which iterates every entry *as a string* (``for c in arg``). The dependency installer passes uv straight into the command list (``[uv_bin, "pip", ...]``), so a ``_UvResult`` — whose ``__iter__`` yields ``(path, fresh_bootstrap)`` rather than characters — would inject the bool into the command line and crash the install with ``TypeError: sequence item 1: expected str instance, bool found``. A plain ``str`` matches the historical Windows contract and is subprocess-safe. (A single value cannot satisfy both 2-target unpacking and Windows char-iteration: both use the iterator protocol, with contradictory results.) On failure the result is falsy — never raises — so callers can fall back to pip gracefully. r )rLr r r)rJs r ensure_uvrNs7.  FI%% V  rcLt}|sdStj|ddgddd}|jdkrEtj|dgdddj}t d |d n&td |j|j |S) uRun ``uv self update`` on the managed uv binary. Call this during ``hermes update`` so the managed copy stays current. Returns the managed path on success, ``None`` if uv isn't available or the self-update fails (non-fatal — the old version still works). Nr'updateTFr7rr6u ✓ Managed uv updated (r;z!uv self update failed (rc=%d): %s) rrCrD returncoderErFr>rAdebugstderr)rGrJrKs rupdate_managed_uvrTs||H t ^ 68$  F A. { #      575556666  8&:KV][[[ OrrHNonectj}itjt |jt |jd}|dkrt |dSt|dS)aBootstrap uv into *target* using the official standalone installer. Uses ``UV_UNMANAGED_INSTALL`` (POSIX) or ``UV_INSTALL_DIR`` (Windows) so the astral installer writes the binary directly into ``$HERMES_HOME/bin/`` instead of ``~/.local/bin/``. )UV_UNMANAGED_INSTALLUV_INSTALL_DIRr N)r r renvironrr<_install_uv_windows_install_uv_posix)rHr envs rr?r?s_  F  *  !$FM 2 2fm,,    CC     #rr\dict[str, str]c~tjdd5}|j}dddn #1swxYwY tjdddd|gd d tjd |g|d d  t j|dS#t$rYdSwxYw# t j|w#t$rYwwxYwxYw) zHDownload + sh the POSIX installer (two-stage to avoid curl|sh pitfalls).z.shF)suffixdeleteNcurlz-LsSfzhttps://astral.sh/uv/install.shz-oT)r:r8shr\r:r8)tempfileNamedTemporaryFilenamerCrDrunlinkOSError)r\finstaller_paths rr[r[sI  $E% @ @ @ A                W?~ V     > "       In % % % % %    DD   In % % % %    D sM+//6B.B BBB<B,+B<, B96B<8B99B<cDd}tjdddd|g|dddS) z Invoke the PowerShell installer.z*irm https://astral.sh/uv/install.ps1 | iex powershellz-ExecutionPolicyBypassz-cTrcN)rCrD)r\cmds rrZrZsI 5N )8T3?  r3.11uv_binrvenv_dirpython_versionrcdSr*)rprqrrs r rebuild_venvrusDr)rr)rr)rHrrrU)r\r]rrU)ro)rprrqrrrrrr)r0 __future__rloggingrr shutilrCrdpathlibrtypingrhermes_constantsr getLoggerr-rArrrrrLrNrTr?r[rZrurtrrr}s#"""""  ,,,,,,  8 $ $    %A%A%A%A%A%A%A%APB>H.0           r