I cannot knit any papaja files. Whenever I try I get this error:
[WARNING] Deprecated: pandoc-citeproc filter. Use --citeproc instead.
pandoc-citeproc: Error in $: Incompatible API versions: encoded with [1,22] but attempted to decode with [1,21].
CallStack (from HasCallStack):
error, called at ./Text/Pandoc/JSON.hs:112:48 in pandoc-types-1.21-LpPdBV1sPudK4kVghsVxWs:Text.Pandoc.JSON
Error running filter pandoc-citeproc:
Filter returned error status 1
Error: pandoc document conversion failed with error 83
Execution halted
I am using:
R version 4.0.3
R Studio version 1.4.1013
RMarkdown version 2.5.3
papaja version 0.1.0.9997
I'm new to R so sorry if this is a silly question.
With version 2.11, pandoc has deprecated the pandoc-citeproc filter, which caused some trouble with version 0.1.2 of the rmdfiltr package that papaja relies on.
The issue should be resolved by installing version >= 0.1.3 of the rmdfiltr package which is now readily available from CRAN via
install.packages("rmdfiltr")
I ran into this issue as well -- same R, RStudio, rmarkdown, and papaja version. To add, I'm using pandoc version 2.11.0.2.
It looks like there's been some progress since this post and subsequent comments. I was able to get my document to knit by installing the rmdfiltr package per this comment: https://github.com/crsh/papaja/issues/427#issuecomment-731730225
remotes::install_github("crsh/rmdfiltr")
Related
After expo eject I run npx #react-native-community/cli doctor
It shows
✖ Watchman - Used for watching changes in the filesystem when in development mode
Version found: 2021.09.06.00
Version supported: 4.x
I guess react native doesn't understand it because numeration after version 4.9 was changed. How I can fix it?
I'm had the same issue after running 'react-native doctor'.
✖ Watchman - Used for watching changes in the filesystem when in development mode
- Version found: 2021.10.04.00
- Version supported: 4.x
I entered 'e' to fix the error and it worked!
› Press e to try to fix errors.
This was an issue with doctor - as you say, the date format (CalVer) versions are all newer than 4.9, which was released in 2017.
The misleading error was fixed in https://github.com/react-native-community/cli/pull/1700 (which should be included in new installations of RN ^0.70.1) - it can be safely ignored.
In my build pipeline, I have the following step:
I am getting the following error:
##[error]The nuget command failed with exit code(1) and error(NU1102: Unable to find package Microsoft.Windows.SDK.BuildTools with version (>= 10.0.19041.8)
When I go to the NuGet page for this package: Microsoft.Windows.SDK.BuildTools, I see that it only has one version: 10.0.18362.3-preview. I am not sure why the NuGet restore step is trying to get a higher version that does not exist. Why is this happening and how can I fix it? Note: this is my first Pipeline.
Agent Specification: Windows-2019.
From this page, you can see only two versions of the package Microsoft.Windows.SDK.BuildTools are listed:
10.0.19041.1
10.0.18362.3-preview
When open the page of version 10.0.19041.1, you can see the warning message to notify that this package version has been deprecated. But it seems that you can still download and install it.
I think the other package versions may have been permanently deleted by the owner due to some security vulnerabilities. So you no longer find them.
You can try to open your project using Visual Studio on your local machine, and change to use version 10.0.18362.3-preview in your program.
I am running protractor tests, and within the last couple days started getting this error:
WebDriverError: unknown error: cannot get automation extension
from unknown error: page could not be found: chrome extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html
After some research, I tried updating protractor but I was already on the latest version (5.1.1). I checked to see if my chromedriver and chrome version are compatible and it looks like they are. I also updated my webdriver-manage to 12.0.4 but I still have the same problem.
-My chrome version is: 57.0.2987.133 (Official Build) (64-bit)
-protractor is: 5.1.1
-webdriver-manager is: 12.0.4
-chromedriver version: 2.2.6
https://github.com/SeleniumHQ/selenium/issues/3508
According to the comment from "JimmyKane" installing chromedriver v2.28 and removing the browser.manage().window().setSize() fixed it.
Attempting to install Specio::Constraint::Simple, running into the following error:
Can't resolve method "???" overloading "&{}" in package
"Specio::Constraint::Simple" at Specio::Constraint::Simple->new line
35.
Only related article I have found has been: https://rt.cpan.org/Public/Bug/Display.html?id=117975
Any suggestions would be appreciated.
Thank you
This is caused by a bug in older versions of Role::Tiny that was fixed in version 1.003003:
overloads specified as method names rather than subrefs are now applied
properly
Upgrading Role::Tiny should fix it and allow Specio::Constraint::Simple to be installed normally.
Actually, you don't even need to do that manually: Version 0.26 of Specio now requires at least version 1.003003 of Role::Tiny. Any future attempt to install Specio will upgrade Role::Tiny automatically (if required).
This question is in continuation of this post, I have tried installing Xerces-C but the thing is Xerces-C version is 2.8.0 and 3.0.0 and XML::XERCES latest version is 2.7.0 and so am getting following error message:
Update2: Here is the error which am getting, it says there is somekind of version mismatch.
Using XERCES_LIB = /home/adoshi/XML-Parser/Parser2/
xerces-c_2_8_0-hppa-hpux-acc_3(1)/xerces-c_2_8_0-hppa-hpux-acc_3/lib
Using XERCES_INCLUDE = /home/adoshi/XML-Parser/Parser2/
xerces-c_2_8_0-hppa-hpux-acc_3(1)/xerces-c_2_8_0-hppa-hpux-acc_3/include
WARNING
You have defined the XERCESCROOT variable, but the file:
XERCESCROOT/src/xercesc/config.status
does not seem to point to the config.status file that was used to
build your Xerces-C library. Without that file, I may not be able to
properly build the C++ glue files that come with Xerces.pm.
Proceeding anyway ...
Using Xerces-C version info from /home/adoshi/XML-Parser/Parser2/xerces
-c_2_8_0-hppa-hpux-acc_3(1)/xerces-c_2_8_0-hppa-hpux-acc_3/include/xercesc/util
/XercesVersion.hpp
*** Version Mismatch ***
You are attempt to build XML::Xerces-2.7.0-0 using Xerces-C-2.8.0,
this will most likely fail, so I am aborting.
You must use Xerces-C-2.7.0
Any guidance would be highly appreciated.
Did you read the download page that clearly says "Older releases are available from the archive download site."? Perhaps you can find a 2.7.0 release there.