I'm trying to install a few packages on the command prompt, but I keep getting this error:
ERROR: Ignored the following versions that require a different python version: 1.6.2 Requires-Python >=3.7,<3.10; 1.6.3 Requires-Python >=3.7,<3.10; 1.7.0 Requires-Python >=3.7,<3.10; 1.7.0rc1 Requires-Python >=3.7,<3.10; 1.7.0rc2 Requires-Python >=3.7,<3.10; 1.7.1 Requires-Python >=3.7,<3.10
ERROR: Could not find a version that satisfies the requirement opencv-headless (from versions: none)
ERROR: No matching distribution found for opencv-headless
I tried downloading the earlier version of python (3.7) and then created a new virtual environment, but I think that the command prompt is still creating a virtual environment on the 3.10 version of python I have installed. What can I do to fix this?
This is the project I am working on https://github.com/datascienceanywhere/FaceRecognition_Flask
in case more information is needed on the type of packages. I'm also working on a windows10.
Related
I am working on the Scala JS Tutorial located at: https://www.scala-js.org/doc/tutorial/basic/index.html which also links to the Repo: https://github.com/scala-js/scalajs-tutorial
So far I get through Step 5. The sample works well when you do:
sbt
~fastLinkJS
So when I run the run command that is where I have problems ( Starting Step 6 ). Node if you are using the Github Repo, make sure you update build.properties SBT version to 1.7.1 ( thats the version I have ).
When I then use the RUN command from within SBT, it will give the error I run into. So i can confirm it is reproducible.
I was not sure if it is also related to my machine. My statics are below:
uname -a:
Darwin HQSML-1689569 21.4.0 Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64 x86_64
node --version:
v12.4.0
sbt -version:
sbt version in this project: 1.7.1
sbt script version: 1.7.1
scala -version:
Scala code runner version 3.1.3 -- Copyright 2002-2022, LAMP/EPFL
Is this a current bug? Is this a ScalaJS thing? I was curious if it has lagged behind in comparison to javascript or something and it just fails to understand what the ?. statement means. Nothing is wrong with the jsdom module from what I can tell when looking at the JS itself, so i am thinking it is related to the Interpreter or something?
Can anyone help me with this. Im using Mac. I cant find the location of the rulemanager. Please see error below
Lxxxxxxx:pmd-bin-6.34.0 xxxxxx$ sfdx scanner:run pmd --target /usr/src --category rulesets/java/quickstart.xml -f sarif
(node:17810) [editions-autoloader-none-broadened] Error Plugin: sfdx-cli: editions-autoloader-none-broadened: Unable to determine a suitable edition, even after broadening.
module: #oclif/config#1.17.0
task: runHook init
plugin: sfdx-cli
root: /Users/xxxxxxx/.local/share/sfdx/client/7.100.0-9d243d8
See more details with DEBUG=*
(Use node --trace-warnings ... to show where the warning was created)
ERROR running scanner:run: Attempted to resolve unregistered dependency token: "RuleManager"
Kieran, this is an issue that we just discovered. It is related to an incompatibility with the version of Node.js that is bundled with the Salesforce CLI and a library that is used by sfdx-scanner.
A temporary workaround can be found at https://github.com/forcedotcom/sfdx-scanner/issues/412
You will need to use the npm installation instead of the pkg installer since you are interested in the Sarif output. Sarif output was added in version 2.6.0. The issue affects versions 2.6.0-2.8.0 when using the pkg installer on a Mac.
We hope to have a fix rolled out in the next couple of days. I will post here when version 2.9 has been released. Sorry for any inconvenience.
Kieran, this issue has been fixed in version 2.9.1. You can upgrade by executing the following commands in your shell.
sfdx plugins:uninstall #salesforce/sfdx-scanner
sfdx plugins:install #salesforce/sfdx-scanner
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")
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.
When I run my karma unit tests I get the following error:
karma start karma.conf.js
Fatal error: bundle() no longer accepts option arguments
Move all option arguments to the browserify() constructor.
I am running using the following versions:
karma 0.12.21
karma-browserify 0.2.1
browserify 5.9.3
The issue is that the karma-browserify version 0.2.1 - currently the latest version - is not compatible with the 5.0.0 release of browserify on Jul 22, 2014.
The package.json in karma-browserify does not prevent the 5.0.0 or greater version of browserify to be installed on an npm install, so when you install a new project or update your browserify version you will get this error.
until karma-browserify is updated you can force your project to use the most recent 4.X version of browserify - which is compatible with karma-browserify - version 4.2.3 via adding the following line to package.json:
"browserify" : "^4.0.0"
then running:
npm update browserify