Summary
The corteza bash tool intermittently fails with:
Error: Native call to `processx_poll` failed
This happened repeatedly while running long-ish R package commands in ~/chatterbox, especially R CMD check and tinypkgr::check().
Examples
Commands that triggered it:
r -e 'tinyrox::document(); tinypkgr::check()'
R CMD build --no-build-vignettes --no-manual . >/tmp/chatterbox-build-pr8.out 2>&1 &&
env _R_CHECK_FORCE_SUGGESTS_=false R CMD check --no-manual --as-cran chatterbox_0.1.0.3.tar.gz >/tmp/chatterbox-check-pr8.out 2>&1
The underlying R process/check often appears to keep progressing or at least writes partial logs. The tool call itself returns the processx_poll failure, so corteza loses the command status and treats verification as failed/unknown.
Observed behavior
bash returns Error: Native call to processx_poll failed.
- Partial output/log files exist afterward.
- Re-running smaller pieces often works.
tinytest::test_package("chatterbox") completes fine.
- The failure seems tied to longer-running commands or commands with redirected output, but I haven't isolated the exact trigger.
Expected behavior
If the subprocess exits normally, bash should return the subprocess exit status and captured output.
If corteza times out or kills the process, the error should say that explicitly and include whatever output was captured.
Why this matters
This makes package verification ambiguous. In the chatterbox PR #8 review, local checks got far enough to show install/load/docs progress, but corteza returned processx_poll instead of a clean pass/fail result.
Environment/context
- Project:
~/chatterbox
- R package workflow
- Commands run through corteza
bash tool
- R version seen in logs: 4.6.0
- OS: Ubuntu 24.04
Summary
The corteza
bashtool intermittently fails with:This happened repeatedly while running long-ish R package commands in
~/chatterbox, especiallyR CMD checkandtinypkgr::check().Examples
Commands that triggered it:
r -e 'tinyrox::document(); tinypkgr::check()'The underlying R process/check often appears to keep progressing or at least writes partial logs. The tool call itself returns the
processx_pollfailure, so corteza loses the command status and treats verification as failed/unknown.Observed behavior
bashreturnsError: Native call to processx_poll failed.tinytest::test_package("chatterbox")completes fine.Expected behavior
If the subprocess exits normally,
bashshould return the subprocess exit status and captured output.If corteza times out or kills the process, the error should say that explicitly and include whatever output was captured.
Why this matters
This makes package verification ambiguous. In the chatterbox PR #8 review, local checks got far enough to show install/load/docs progress, but corteza returned
processx_pollinstead of a clean pass/fail result.Environment/context
~/chatterboxbashtool