Specific error messages no longer returned · Issue #228 · r-lib/callr (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • White papers, Ebooks, Webinars
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

The recent updates to the error handling in the development versions of processx (r-lib/processx#335) and callr (#227) have broken some of my workflowr unit tests. My tests check for specific error messages, but these are no longer propagated via tryCatch(). Below is a reproducible example. Would it be possible to restore the previous behavior where the specific error message is retained?

f <- function() { tryCatch( callr::r_safe(function() stop("specific message")), error = function(e) e$message ) }

packageVersion("processx")

[1] ‘3.6.0’

packageVersion("callr")

[1] ‘3.7.0’

f()

[1] "callr subprocess failed: specific message"

packageVersion("processx")

[1] ‘3.6.0.9000’

packageVersion("callr")

[1] ‘3.7.0.9000’

f()

[1] "error in callr subprocess"

Metadata

Development

No branches or pull requests

Issue actions