NjB SrSSKJr SSKrSSKrSSKJr SSKJr SSK J r J r SSK J r Jr SSKJr S S jr\S S j5rSS jrg)aWrite extraction artifacts to a local directory or an ``s3://`` prefix. `output_sink` is a context manager that hands back a local directory to write into. When the destination is an ``s3://`` URI, everything written there is uploaded to the bucket on exit; local destinations are written in place and never copied. The write-local-then-upload shape exists because the artifact writers (pymupdf for the annotated PDF, the HTML renderer, ``json.dump``) all need a real local filesystem path -- none can stream to S3 directly. Uploads go through cloudpathlib's default client, which resolves AWS credentials from the boto3 chain (env / ``~/.aws`` / IAM role), so no keys are passed explicitly. ) annotationsN)contextmanager)Path)Any Generator)AnyPathS3Path)loggerc4[[U5[5$)zFTrue when ``output_dir`` is an ``s3://`` URI rather than a local path.) isinstancerr ) output_dirs 0/home/mande/repo/quber/src/quber/files/output.pyis_s3rs gj)6 22c#X# [U5n[U[5(a[R"SS9n[ U5nUv Sn[ URS55HrnUR5(dMXRU5R5- nURUSS9 [R"SURU5 US- nMt [R"S XA5 S S S 5 g [ U5nURSSS 9 Uv g !,(df  g =f7f) aYield a local directory to write artifacts into. For a local ``output_dir`` the directory is created and yielded directly, so writes land in their final location. For an ``s3://`` ``output_dir`` a temporary directory is yielded; on clean exit every file written under it is uploaded to the bucket under the same relative path, then the temporary directory is removed. An exception inside the ``with`` block skips the upload and propagates, so a failed run never leaves partial artifacts in the bucket. z quber-out-)prefixr*T)force_overwrite_to_cloudzUploaded {} -> {}zUploaded {} artifact(s) to {}N)parentsexist_ok)rr r tempfileTemporaryDirectoryrsortedrglobis_file relative_toas_posix upload_fromr infonamemkdir)r desttmpworkuploadedftargetlocals r output_sinkr* s : D$  ( ( =9DJHDJJsO,yy{{ d 3 < < >>""1t"D /@A  - KK7 H> =Z  D4 0 > =s5D*B9D0)D* D'#D*c [U5nX1- R[R"US[S9SS9 SSS5 g!,(df  g=f)aWrite a job's completion marker as its own, final upload. The marker's existence tells downstream (the join step that launches fusion) that this job's artifacts are fully in place, so it must be the last object to land. It goes through its own `output_sink` after the artifact sink has closed: a single sink uploads files in sorted order, and a marker name can sort before the artifacts it vouches for. )indentdefaultzutf-8)encodingN)r* write_textjsondumpsstr)r filenamepayloadouts rwrite_completion_markerr7@s= Z C ##DJJwq#$NY`#a ! s +A A)r r3returnbool)r r3r8zGenerator[Path, None, None])r r3r4r3r5zdict[str, Any]r8None)__doc__ __future__rr1r contextlibrpathlibrtypingrr cloudpathlibrr logurur rr*r7rrrCsC # %!(3 > br