> On 14/08/2023, at 5:25 AM, Jamie Lentin wrote:
>
> Thanks both!
>
> On 2023-08-12 23:52, Uwe Ligges wrote:
>> On 12.08.2023 23:19, Dirk Eddelbuettel wrote:
>>> On 12 August 2023 at 18:12, Uwe Ligges wrote:
>>> | On 12.08.2023 15:10, Jamie Lentin wrote:
>>> | > The system call in question is
On 13.08.2023 22:57, Avraham Adler wrote:
I had a similar issue with a paper on JSTOR. Usually CRAN let it through.
However, I eventually switched from URL to DOI and now the user needs to find
the free source so to rid myself of the constant hassle. CRAN really doesn’t
like redirects. I gu
I had a similar issue with a paper on JSTOR. Usually CRAN let it through.
However, I eventually switched from URL to DOI and now the user needs to find
the free source so to rid myself of the constant hassle. CRAN really doesn’t
like redirects. I guess you could wrap it in \code{} so as not to h
I have a package whose documentation includes the reference
\doi{10.1137/18M1186411} which redirects here:
https://epubs.siam.org/doi/10.1137/18M1186411
Running R CMD check --as-cran on the package gives
Found the following (possibly) invalid URLs:
URL: https://epubs.siam.org/doi/10.1137/18
Thanks both!
On 2023-08-12 23:52, Uwe Ligges wrote:
On 12.08.2023 23:19, Dirk Eddelbuettel wrote:
On 12 August 2023 at 18:12, Uwe Ligges wrote:
| On 12.08.2023 15:10, Jamie Lentin wrote:
| > The system call in question is done by the TMB package[2], and not
ours
| > to tinker with:
| >
| >
В Sun, 13 Aug 2023 00:59:40 -0700
Michael Topper пишет:
>- Setting the nthreads argument to 2 in fixest::feels() in case
> this is the problem as suggested.
Any chance you could be hitting some other code paths in the fixest
package while working on the objects returned by fixest::feols()?
I have tried the following:
- Trimming down the examples substantially to only run 1 regression
per-function.
- Setting the nthreads argument to 2 in fixest::feels() in case this is
the problem as suggested.
- Tried to use skip_cran_test() on the tests that include fixest
regress
