Skip to content

fs cp -r: keep going past failed files - #7712

Draft
yuanjieding-db wants to merge 1 commit into
yuanjieding-db/testserver-fault-headersfrom
yuanjieding-db/fs-cp-keep-going
Draft

yuanjieding-db wants to merge 1 commit into
yuanjieding-db/testserver-fault-headersfrom
yuanjieding-db/fs-cp-keep-going

Conversation

@yuanjieding-db

@yuanjieding-db yuanjieding-db commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Stack. Each PR is based on the one before it, so its diff shows only its own change.

PR
1 #7711 Skip the per-file parent-directory check in fs cp -r
2 #7784 testserver: optional response headers on fault rules
3 #7712 fs cp -r: keep going past failed files (validation results are here)
4 #7785 fs cp -r: stop when files keep failing for 5 minutes
5 #7786 fs cp -r: back off during failure bursts
6 #7787 fs cp -r: retry transient directory errors

This is part 3.

Changes

fs cp -r used to stop at its first failed file. This PR replaces the errgroup with a copy that runs up to --concurrency files at a time and keeps going:

  • Retryable failures are deferred: 408, 429, any 5xx (including an empty or non-JSON body), or a network error, after the filer's own retries. After the walk, each deferred file gets one more full attempt with its source reopened.
  • Other failures (400, 404, ...) fail only that file.
  • 401, 403, a cancelled context, or a failure to print stop the copy. Files in flight are cancelled and reported as failed ("cancelled: the copy stopped before this file finished"), since on DBFS they may be partial. The walk then only counts the files left, and reports them as not attempted.
  • A retry without --overwrite that finds the target already there skips it only if the sizes match. A failed DBFS write can leave a truncated file, so a different size, or a failed Stat, fails the file with a hint to rerun with --overwrite. The retry never overwrites: a proxy 5xx can come before the server's existence check, so overwriting could replace a file the user asked to keep. A partial file of the same size isn't detected. That's acceptable because a failed DBFS write leaves a truncated prefix, which is shorter unless the failure came after the last block.
  • The summary goes to stderr. A complete copy prints Copied N files. (plus any skipped), which JSON output leaves out. Otherwise the summary lists the counts, the reason the copy stopped (if it did), and the first 10 failures with their HTTP status. The command then exits 1. Per-file lines on stdout are unchanged.
  • Debug logging has a line for each deferred file and each failed retry.

Why

A copy of many small files sends hundreds of thousands of requests, so a few transient errors are expected. One of them used to end the whole copy: a 10,000-file copy died after about 2,500 files on a single 503. The filer's per-call retries absorb short throttling. This change handles what gets past them, starting with a 500, which the filer doesn't retry.

Validation

These are staging runs on kartik-test: 123,404 files × 150 KiB, 124 directories, default --concurrency 8. They used the full stack before it was split (da7174822), with the same behavior. Both builds carried the same validation-only patch that logs Files API requests.

This stack, upload This stack, download v1.26.0, upload
Exit code 0 0 1
Wall time 2:15:24 2:27:16 27:56 (stopped)
Files copied 123,404 123,404 15,497
Transient errors 3 × HTTP 500, each deferred and copied on its retry 3 × HTTP 503, absorbed by the filer's retries 1 × HTTP 500, which ended the copy
HEAD /fs/directories (per-file check, removed in #7711) 0 2 15,505
Download matches the source manifest n/a yes, 0 mismatches n/a

The breaker, the stall timeout and the directory retries never triggered on staging. Unit and acceptance tests in #7785 to #7787 cover them.

Smaller end-to-end checks on the top-of-stack build, against a new throwaway Volume on kartik-test (since deleted):

  • Re-upload without --overwrite: all 200 files skipped, Copied 0 files, skipped 200 that already existed., exit 0.
  • Re-upload with --overwrite: all 200 copied, exit 0.
  • Volume to Volume: exit 0, and the downloaded copy matches the source manifest.
  • DBFS root to Volume: not runnable on kartik-test. The workspace sets disable_legacy_dbfs, so every dbfs:/tmp access is denied, and the released v1.26.0 gets the same error. CI integration tests cover DBFS-root sources.
  • A single 200 MiB file: unchanged. One output line, and with multipart upload in a terminal, the progress bar. The download is byte-identical.
  • Ctrl-C during a 2,000-file upload: see the known limits below.
  • Three 200 MiB files at --concurrency 1 with a 5s stall timeout: the upload succeeds both before and after the stall fix in fs cp -r: stop when files keep failing for 5 minutes #7785 (exit 0, 67s and 70s). Downloading that directory at the default --concurrency 8 fails: see the known limits.

Known limits

  • A real Ctrl-C ends the process immediately, with exit code 130 and no summary. On kartik-test that happened after 304 of 2,000 files. fs cp installs no signal handler, and adding one would change the exit code CLI-wide, so it's left out of this stack. The "Stopped: the copy was cancelled." summary appears only when the caller cancels the command's context, which a Ctrl-C in a terminal doesn't do today. A rerun without --overwrite skips the files that were already copied.
  • A partial file of the same size as the source isn't detected (see the size-check bullet above).
  • Concurrent downloads of large files from this Volume were cut mid-stream (unexpected EOF after 12 to 14 MB of each 200 MiB file). The released v1.26.0 fails the same way and leaves the same partial files. This stack retries each file once, finds the partial local file, and reports it with the size-check message, so the fix is a rerun with --overwrite, or at --concurrency 1, which succeeded with all checksums matching. Downloads stream straight into the target, with no temp file and no resume, which is out of scope here.
  • Multipart uploads aren't checked for partial files. That path is behind DATABRICKS_EXPERIMENTAL_MULTIPART_UPLOAD, which is off by default.

Tests

  • TestRecursiveCopy: one table that checks the exact stderr summary of each scenario:
    • a complete copy, one file, JSON output, a skipped file;
    • a 500 retried after the walk, a file still failing on its retry, a 404, a 401, the 10-failure limit, schemes;
    • each outcome of the size check;
    • a cancelled copy, including on a deferred file;
    • a broken stdout, a failed Mkdir.
  • TestClassifyError and TestDescribeError.
  • Acceptance: cmd/fs/cp-r-keep-going/single-500 (one 500, retried) and persistent-500 (a non-JSON 500 on every upload of one file). The old fail-fast unit test in cp_test.go is replaced by the table.

Self-review

Isaac review: no findings.

/code-review (medium), 9 findings, all answered, none changed:

  • A file cancelled mid-write is counted as not attempted, but may have left a partial DBFS target that a rerun without --overwrite skips. Fixed (also raised by the orchestrator): such a file is now reported as failed ("cancelled: the copy stopped before this file finished"). A rerun without --overwrite can still skip its partial target, as before this change.
  • A transient Mkdir error stops the copy. Fixed in fs cp -r: retry transient directory errors #7787.
  • Deferred files are retried right after the walk, with no backoff. The filer already backs off on 408, 429 and 502 to 504 for each call, and fs cp -r: back off during failure bursts #7786 adds a breaker for bursts.
  • A total network outage goes through every file twice. fs cp -r: stop when files keep failing for 5 minutes #7785's stall timeout bounds it.
  • A retry that finds its own landed upload reports the file as skipped, not copied. That's intentional. The file is complete, and the second attempt didn't write it.
  • A retryable source-read failure, followed by an existing target of another size, fails the file instead of skipping it. That's conservative on purpose: the copy can't tell its own partial file from someone else's file, and the message says how to resolve it. It's also rare, because the filer retries source reads first.
  • A cancellation after the last file finishes reports "cancelled". That's accurate, and it shows 0 not attempted.
  • 501 and 505 are retried. That's one extra attempt per file, not worth a special case.
  • The size check stats the source again. That happens only on the rare path where a retry finds an existing target.

This pull request and its description were written by Isaac.

yuanjieding-db added a commit that referenced this pull request Nov 17, 2026
Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Commit: 7d8cf4b44 | Workflow run

Regression test report

Selected 4 changed tests (limit=20, 0 not selected)

4 tests: regression=4 unreleased=0 coverage=0 failing=0
test branch main (4e503ea) latest (v1.26.0)
TestAccept/cmd/fs/cp-r-keep-going/persistent-500 ✅ ❌ ❌
TestAccept/cmd/fs/cp-r-keep-going/single-500 ✅ ❌ ❌
TestAccept/cmd/fs/cp-r-requests ✅ ❌ ❌
TestAccept/cmd/fs/cp/dir-to-dir ✅ ❌ ❌
TestAccept/cmd/fs/cp-r-keep-going/persistent-500: branch ✅ | main (4e503ea) ❌ | latest (v1.26.0) ❌

main (4e503ea):

acceptance_test.go:1380: Diff:
        --- cmd/fs/cp-r-keep-going/persistent-500/output.txt
        +++ /tmp/TestAcceptcmdfscp-r-keep-goingpersistent-5002019155526/002/output.txt
        @@ -1,20 +1,12 @@
         
         >>> cp_r localdir dbfs:/Volumes/main/default/keep-going/dst --concurrency 2
        -Copy incomplete: 3 copied, 0 skipped (already existed), 1 failed, 0 not attempted.
        -Failed:
        -  localdir/f3.txt -> dbfs:/Volumes/main/default/keep-going/dst/f3.txt: HTTP 500 Internal Server Error
        -Error: 1 file was not copied
        -localdir/f1.txt -> dbfs:/Volumes/main/default/keep-going/dst/f1.txt
        +Error: databricks-api error: 
         localdir/f2.txt -> dbfs:/Volumes/main/default/keep-going/dst/f2.txt
        -localdir/f4.txt -> dbfs:/Volumes/main/default/keep-going/dst/f4.txt
         
         Exit code: 1
         
         === Four uploads plus one retry of f3.txt
         
         >>> print_requests.py --summary --sort //api/2.0/fs/files/
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f1.txt overwrite=false
         PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f2.txt overwrite=false
         PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f4.txt overwrite=false

latest (v1.26.0):

acceptance_test.go:1380: Diff:
        --- cmd/fs/cp-r-keep-going/persistent-500/output.txt
        +++ /tmp/TestAcceptcmdfscp-r-keep-goingpersistent-5004137232665/002/output.txt
        @@ -1,12 +1,8 @@
         
         >>> cp_r localdir dbfs:/Volumes/main/default/keep-going/dst --concurrency 2
        -Copy incomplete: 3 copied, 0 skipped (already existed), 1 failed, 0 not attempted.
        -Failed:
        -  localdir/f3.txt -> dbfs:/Volumes/main/default/keep-going/dst/f3.txt: HTTP 500 Internal Server Error
        -Error: 1 file was not copied
        +Error: databricks-api error: 
         localdir/f1.txt -> dbfs:/Volumes/main/default/keep-going/dst/f1.txt
         localdir/f2.txt -> dbfs:/Volumes/main/default/keep-going/dst/f2.txt
        -localdir/f4.txt -> dbfs:/Volumes/main/default/keep-going/dst/f4.txt
         
         Exit code: 1
         
        @@ -16,5 +10,3 @@
         PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f1.txt overwrite=false
         PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f2.txt overwrite=false
         PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f4.txt overwrite=false
TestAccept/cmd/fs/cp-r-keep-going/single-500: branch ✅ | main (4e503ea) ❌ | latest (v1.26.0) ❌

main (4e503ea):

acceptance_test.go:1380: Diff:
        --- cmd/fs/cp-r-keep-going/single-500/output.txt
        +++ /tmp/TestAcceptcmdfscp-r-keep-goingsingle-500795614563/002/output.txt
        @@ -1,20 +1,7 @@
         
         >>> cp_r localdir dbfs:/Volumes/main/default/keep-going/dst --concurrency 2
        -Copied 6 files.
        +Error: databricks-api error: Fault injected by test.
         localdir/f1.txt -> dbfs:/Volumes/main/default/keep-going/dst/f1.txt
         localdir/f2.txt -> dbfs:/Volumes/main/default/keep-going/dst/f2.txt
        -localdir/f3.txt -> dbfs:/Volumes/main/default/keep-going/dst/f3.txt
        -localdir/f4.txt -> dbfs:/Volumes/main/default/keep-going/dst/f4.txt
        -localdir/f5.txt -> dbfs:/Volumes/main/default/keep-going/dst/f5.txt
        -localdir/f6.txt -> dbfs:/Volumes/main/default/keep-going/dst/f6.txt
         
        -=== Six uploads plus one retry
        -
        ->>> print_requests.py --summary --sort //api/2.0/fs/files/
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f1.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f2.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f4.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f5.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f6.txt overwrite=false
        +Exit code: 1
        
FAIL

latest (v1.26.0):

acceptance_test.go:1380: Diff:
        --- cmd/fs/cp-r-keep-going/single-500/output.txt
        +++ /tmp/TestAcceptcmdfscp-r-keep-goingsingle-5004153507032/002/output.txt
        @@ -1,20 +1,8 @@
         
         >>> cp_r localdir dbfs:/Volumes/main/default/keep-going/dst --concurrency 2
        -Copied 6 files.
        +Error: databricks-api error: Fault injected by test.
         localdir/f1.txt -> dbfs:/Volumes/main/default/keep-going/dst/f1.txt
         localdir/f2.txt -> dbfs:/Volumes/main/default/keep-going/dst/f2.txt
        -localdir/f3.txt -> dbfs:/Volumes/main/default/keep-going/dst/f3.txt
         localdir/f4.txt -> dbfs:/Volumes/main/default/keep-going/dst/f4.txt
        -localdir/f5.txt -> dbfs:/Volumes/main/default/keep-going/dst/f5.txt
        -localdir/f6.txt -> dbfs:/Volumes/main/default/keep-going/dst/f6.txt
         
        -=== Six uploads plus one retry
        -
        ->>> print_requests.py --summary --sort //api/2.0/fs/files/
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f1.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f2.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f3.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f4.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f5.txt overwrite=false
        -PUT /api/2.0/fs/files/Volumes/main/default/keep-going/dst/f6.txt overwrite=false
        +Exit code: 1
        
FAIL
TestAccept/cmd/fs/cp-r-requests: branch ✅ | main (4e503ea) ❌ | latest (v1.26.0) ❌

main (4e503ea):

acceptance_test.go:1380: Diff:
        --- cmd/fs/cp-r-requests/output.txt
        +++ /tmp/TestAcceptcmdfscp-r-requests1213364925/002/output.txt
        @@ -1,6 +1,5 @@
         
         >>> [CLI] fs cp -r localdir dbfs:/Volumes/main/default/fs-cp-r-requests/dst
        -Copied 3 files.
         localdir/a.txt -> dbfs:/Volumes/main/default/fs-cp-r-requests/dst/a.txt
         localdir/b.txt -> dbfs:/Volumes/main/default/fs-cp-r-requests/dst/b.txt
         localdir/sub/c.txt -> dbfs:/Volumes/main/default/fs-cp-r-requests/dst/sub/c.txt
        @@ -8,6 +7,9 @@
         === Recursive copy: a directory PUT per directory, a file PUT per file, no directory HEAD per file
         
         >>> print_requests.py --sort //api/2.0/fs/
        +{"method":"HEAD","path":"/api/2.0/fs/directories/Volumes/main/default/fs-cp-r-requests/dst"}
        +{"method":"HEAD","path":"/api/2.0/fs/directories/Volumes/main/default/fs-cp-r-requests/dst"}
        +{"method":"HEAD","path":"/api/2.0/fs/directories/Volumes/main/default/fs-cp-r-requests/dst/sub"}
         {"method":"PUT","path":"/api/2.0/fs/directories/Volumes/main/default/fs-cp-r-requests/dst"}
         {"method":"PUT","path":"/api/2.0/fs/directories/Volumes/main/default/fs-cp-r-requests/dst/sub"}
         {"method":"PUT","path":"/api/2.0/fs/files/Volumes/main/default/fs-cp-r-requests/dst/a.txt"}

latest (v1.26.0): same output as main (4e503ea)

TestAccept/cmd/fs/cp/dir-to-dir: branch ✅ | main (4e503ea) ❌ | latest (v1.26.0) ❌

main (4e503ea):

acceptance_test.go:1380: 
        	Error Trace:	/home/runner/work/cli/cli/libs/testdiff/testdiff.go:22
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:1380
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:1121
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:666
        	Error:      	Not equal: 
        	            	expected: "\n>>> [CLI] fs cp -r localdir dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir\nCopied 2 files.\nlocaldir/file1.txt -> dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file1.txt\nlocaldir/file2.txt -> dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file2.txt\n\n>>> [CLI] fs cat dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file1.txt\nfile1 content\n\n>>> [CLI] fs cat dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file2.txt\nfile2 content\n"
        	            	actual  : "\n>>> [CLI] fs cp -r localdir dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir\nlocaldir/file1.txt -> dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file1.txt\nlocaldir/file2.txt -> dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file2.txt\n\n>>> [CLI] fs cat dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file1.txt\nfile1 content\n\n>>> [CLI] fs cat dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file2.txt\nfile2 content\n"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -2,3 +2,2 @@
        	            	 >>> [CLI] fs cp -r localdir dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir
        	            	-Copied 2 files.
        	            	 localdir/file1.txt -> dbfs:/Volumes/main/default/fs-cp-test-[UNIQUE_NAME]/uploaded-dir/file1.txt
        	Test:       	TestAccept/cmd/fs/cp/dir-to-dir
        	Messages:   	cmd/fs/cp/dir-to-dir/output.txt vs /tmp/TestAcceptcmdfscpdir-to-dir3125102800/002/output.txt

latest (v1.26.0): same output as main (4e503ea)

@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: 7d8cf4b

Run: 44383012549

Env 🔄​flaky 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 271 18 10:48
💚​ aws-windows-latest-4core-16gb 1 273 16 4:36
💚​ azure linux-2core-8gb 1 270 18 9:35
🔄​ azure-windows-latest-4core-16gb 1 1 271 16 5:35
💚​ gcp linux-2core-8gb 1 271 18 10:38
🔄​ gcp-windows-latest-4core-16gb 3 1 270 16 6:51
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure linux-2core-8gb azure-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
💚​ TestAccept 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
🔄​ TestFsLsWithAbsolutePaths ✅​p ✅​p ✅​p ✅​p ✅​p 🔄​f
🔄​ TestFsLsWithAbsolutePaths/uc-volumes ✅​p ✅​p ✅​p ✅​p ✅​p 🔄​f
🔄​ TestSyncIncrementalFileSync ✅​p ✅​p ✅​p ✅​p ✅​p 🔄​f
🔄​ TestSyncIncrementalSyncPythonNotebookDelete ✅​p ✅​p ✅​p 🔄​f ✅​p ✅​p
Top 5 slowest tests (at least 2 minutes):
duration env testname
3:55 aws linux-2core-8gb TestAccept
3:54 gcp linux-2core-8gb TestAccept
3:45 azure linux-2core-8gb TestAccept
2:34 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsRead
2:15 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir

@yuanjieding-db
yuanjieding-db force-pushed the yuanjieding-db/fs-cp-keep-going branch from da71748 to 4767c2b Compare November 18, 2026 18:12
@yuanjieding-db yuanjieding-db changed the title Keep going past failed files in fs cp -r fs cp -r: keep going past failed files Nov 18, 2026
@yuanjieding-db
yuanjieding-db changed the base branch from yuanjieding-db/fs-cp-skip-parent-check to yuanjieding-db/testserver-fault-headers November 18, 2026 18:13
@yuanjieding-db
yuanjieding-db force-pushed the yuanjieding-db/testserver-fault-headers branch from 99ea713 to 3dd7522 Compare November 18, 2026 19:02
@yuanjieding-db
yuanjieding-db force-pushed the yuanjieding-db/fs-cp-keep-going branch from 4767c2b to 17ad766 Compare November 18, 2026 19:02
fs cp -r used to stop at the first failed file: one transient 500 or 503
in a copy of many small files ended the whole copy.

The errgroup is replaced by a copy that runs up to --concurrency files at
a time and keeps going:

- A retryable failure (408, 429, any 5xx including a non-JSON body, or a
  network error, after the filer's own retries) defers the file. After
  the walk, each deferred file gets one more full attempt.
- 400, 404 and other errors fail only that file.
- 401, 403, cancellation and a failure to print stop the copy. The walk
  then only counts the files left, reported as not attempted.
- A retry without --overwrite that finds the target already there skips
  it only if the sizes match: a failed DBFS write can leave a truncated
  file. A different size or a failed Stat fails the file.
- The run ends with a summary on stderr and exits 1 if any file was not
  copied.

Co-authored-by: Isaac <no-reply@databricks.com>
@yuanjieding-db
yuanjieding-db force-pushed the yuanjieding-db/fs-cp-keep-going branch from 17ad766 to 7d8cf4b Compare November 18, 2026 19:37

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants