You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: CLI cp file test creates a directory and keeps integration CI red #4662
Took this one — the fix is up in #4672: the test now creates a real file with ov write --mode create (the conftest ov_write helper already passes --wait --timeout), keeps the non-recursive form so file-copy coverage is preserved (no -r), and drops the now-unneeded local temp file. Also confirmed create is the right server-side write mode (openviking/storage/content_write.py), same call shape as tests/cli/test_cli_snapshot.py.
Verified fixed on current main: 94a1031 (merged 2026-09-04 via #4589) rewrote test_cp_file_json_and_human_output to copy the existing test_file_uri fixture (a real file inside the pack) instead of ov_add_resource on a temp .txt path, so the non-recursive file-copy path is covered again instead of hitting the isDir=true FAILED_PRECONDITION. The 06. API & CLI Integration Tests job is green on main at 0c5147c (run 34003645461) after being red since f6d9dec. Closing #4672 was the right call — superseded by the fixture rewrite above. This looks closable; happy to reopen if the same signature reappears.
This looks fixed on current main and can probably be closed:
The offending staging (ov_add_resource creating a directory source for the non-recursive ov cp file test) is gone — fix: watch task status #4589 (94a11313b) rewrote test_cp_file_json_and_human_output to take its source from the test_file_uri fixture, which resolves to a real file inside a pack, so the FAILED_PRECONDITION path no longer exists in tests/cli/test_cli_filesystem.py.
Activity
now-ing commentedon Sep 3, 2026
Took this one — the fix is up in #4672: the test now creates a real file with
ov write --mode create(the conftestov_writehelper already passes--wait --timeout), keeps the non-recursive form so file-copy coverage is preserved (no-r), and drops the now-unneeded local temp file. Also confirmedcreateis the right server-side write mode (openviking/storage/content_write.py), same call shape astests/cli/test_cli_snapshot.py.now-ing commentedon Sep 6, 2026
Verified fixed on current main: 94a1031 (merged 2026-09-04 via #4589) rewrote
test_cp_file_json_and_human_outputto copy the existingtest_file_urifixture (a real file inside the pack) instead ofov_add_resourceon a temp.txtpath, so the non-recursive file-copy path is covered again instead of hitting theisDir=trueFAILED_PRECONDITION. The06. API & CLI Integration Testsjob is green on main at 0c5147c (run 34003645461) after being red since f6d9dec. Closing #4672 was the right call — superseded by the fixture rewrite above. This looks closable; happy to reopen if the same signature reappears.now-ing commentedon Sep 6, 2026
This looks fixed on current
mainand can probably be closed:ov_add_resourcecreating a directory source for the non-recursiveov cpfile test) is gone — fix: watch task status #4589 (94a11313b) rewrotetest_cp_file_json_and_human_outputto take its source from thetest_file_urifixture, which resolves to a real file inside a pack, so the FAILED_PRECONDITION path no longer exists intests/cli/test_cli_filesystem.py.continue-on-erroraggregation from the API & CLI job, so if the test were still broken the job would be red. Recent runs on the current base (e.g. the API & CLI job on feat(parse): support task-based MinerU APIs and the online batch service #4725, based on post-fix: watch task status #4589 main) are green with the rewritten test in place.I had #4672 open with a different fix for the same test and closed it as superseded by the upstream rewrite — details there if useful.
qin-ctx commentedon Sep 18, 2026
感谢提交这个 issue。#4589 已将
test_cp_file_json_and_human_output改为使用test_file_uri提供的真实文件,不再通过单个 txt 导入得到一个目录,再拿它测试非递归文件复制。因此原来的Cannot copy directory without --recursive失败原因已经消除,文件复制的测试目标也保留了。按已修复关闭。如果当前 main 再出现同一失败,可以 reopen,或留言请求重新打开,并附上提交号、CI 运行链接和该测试的错误输出。