You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Neal Richardson (Jira)" <ji...@apache.org> on 2022/10/14 15:56:00 UTC

[jira] [Commented] (ARROW-18062) [R] error in CI jobs for R 3.5 and 3.6 when R package being installed

    [ https://issues.apache.org/jira/browse/ARROW-18062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617816#comment-17617816 ] 

Neal Richardson commented on ARROW-18062:
-----------------------------------------

The slice PR added a UDF registration in .onLoad: https://github.com/apache/arrow/compare/02c671a3791d5f92d3ad0260396e2ee9c286670f...dd9c2243421e165686aaff5e3ff7267ae30e2e14#diff-d33e59c0468a492a62bbb832ed1b4a925e201bbe20cd22b36f24c2483f8bc738R165

Are UDFs known not to work on R < 4.0?

> [R] error in CI jobs for R 3.5 and 3.6 when R package being installed
> ---------------------------------------------------------------------
>
>                 Key: ARROW-18062
>                 URL: https://issues.apache.org/jira/browse/ARROW-18062
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: R
>            Reporter: Nicola Crane
>            Priority: Blocker
>             Fix For: 10.0.0
>
>
> e.g. https://github.com/ursacomputing/crossbow/actions/runs/3246698242/jobs/5325752692#step:5:3164
> From the install logs on that CI job:
> {code}
> ** R
> ** inst
> ** byte-compile and prepare package for lazy loading
> ** help
> *** installing help indices
> ** building package indices
> ** installing vignettes
> ** testing if installed package can be loaded from temporary location
> Error: package or namespace load failed for ‘arrow’:
>  .onLoad failed in loadNamespace() for 'arrow', details:
>   call: fun_cache[[unqualified_name]] <- fun
>   error: invalid type/length (closure/0) in vector allocation
> Error: loading failed
> {code}
> It is currently erroring for R 3.5 and 3.6 in the nightlies with this error.
> The line of code where the error comes from was added in  ARROW-16444 but seeing as that was 3 months ago, it seems unlikely that this change introduced the error.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)