Lately I can't start single tests in VSCode in neither TestExplorer nor the gutter in the editor via the 'play' button.
npm run test and npm run test:coverage work fine as does the JestRunner extension.
The error I'm receiving is:
> myproject#version1 test
> jest --maxWorkers=${JEST_MAX_WORKERS:-4} "--testLocationInResults" "--json" "--useStderr" "--outputFile" "C:\\Users\\ME~1\\AppData\\Local\\Temp\\jest_runner_myproject.json" "--testNamePattern" "TestFile should do something" "--no-coverage" "--reporters" "default" "--reporters" "c:\\Users\\me\\.vscode\\extensions\\orta.vscode-jest-5.2.2\\out\\reporter.js" "--colors" "--watchAll=false" "--testPathPattern" "c:\\\\path\\\\to\\\\my\\\\project\\\\src\\\\persistence\\\\testfile\\.spec\\.ts"
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In C:\path\to\my\project
86 files checked.
testMatch: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x) - 25 matches
testPathIgnorePatterns: dist\\, src.bak\\, integration-tests\\ - 83 matches
testRegex: - 0 matches
Pattern: c:\\\\path\\\\to\\\\my\\\\project\\\\src\\\\persistence\\\\testfile\\.spec\\.ts - 0 matches
Apparently the pattern uses 4 backslashes, which might be the problem, but I have no idea how to resolve this issue.
I tried changing the testPathIgnorePatterns in the jest.config.cjs but that didn't change anything.
Also in IntelliJ IDEA everything works as expected, but I prefer VSCode for this particular project.
Related
I have multiple installations of Eclipse(2021-12) + PyDev(9.3.0.202203051235) all using Iron Python(2.7). All running on Windows 10. They all run the scripts as expected, but one installation has a much more robust console output when debugging, almost like a tracing option is enabled. I've tried reinstalling, deleting workspaces, deleting '.metadata' folders, etc. All the project settings seem identical.
Any ideas how to minimize the console output? Something in registry?
Expected Console output:
pydev debugger: starting (pid: 15312)
Actual Console output:
1.99s - Using GEVENT_SUPPORT: False
0.00s - Using GEVENT_SHOW_PAUSED_GREENLETS: False
0.00s - pydevd __file__: C:\\Eclipse-2021-12-R\plugins\org.python.pydev.core_9.3.0.202203051235\pysrc\pydevd.py
0.11s - Initial arguments: (['C:\\Eclipse-2021-12-R\\plugins\\org.python.pydev.core_9.3.0.202203051235\\pysrc\\pydevd.py', '--multiprocess', '--protocol-http', '--print-in-debugger-startup', '--vm_type', 'python', '--client', '127.0.0.1', '--port', '60413', '--file', 'C:\\Test.py'],)
0.00s - Current pid: 8884
pydev debugger: starting (pid: 8884)
Those should only appear if you add an environment variable asking it to be shown.
i.e.: Something as:
PYDEVD_DEBUG=1
PYDEV_DEBUG=1
Maybe you have such an environment set in your launch configuration or interpreter configuration or elsewhere in your system?
You may want to check the os.environ of the running program to see what's set there.
I'm trying to run madge on a fairly big typescript project. Its compiled output goes to dist/*, and its React frontend are in public/*. Madge's documentation is pretty clear about how to exclude directories, but no matter what I try, it appears to still be checking these directories.
First attempt:
madge --circular --extensions ts,js --exclude '^(dist|public)' --ts-config ./tsconfig.json --warning .
The reason I think it's still checking there is because, first, I still see it scanning those directories as it runs:
And also, its warnings show imports that only occur in public/:
(the '#'-style import is from module-alias)
What I've tried:
Using a regex like ^.*public.*$
Specifying the excludes in .madgerc rather than on cli:
{
"fileExtensions": ["js","ts"],
"tsConfig": "tsconfig.json",
"excludeRegExp": ["^.*dist.*$", "^.*public.*$"]
}
Running with --debug (the output is so massive I can't really make much of it - if I run it to console it crashes with out-of-memory, and if I pipe to a file, it gets so big that it literally fills up my SSD - I had to cancel when the log file surpassed 25 gigs).
Interestingly, it doesn't seem to be reporting any cycles in public/ or dist/, so I think it might be "partially" working. However, it does still seem to be scanning & processing those excluded paths, so I can't get rid of all the warnings that shouldn't be relevant to this run.
I'm working on a simple Sikuli Script.
The script is simply one line shown below
click()
The following error is produced?
javax.script.ScriptException: ReferenceError: "Commands" is not defined in nashorn:mozilla_compat.js at line number 69
I believe I have all dependencies installed. Could I ask for some assistance for what else is missing to move on from this error?
You are trying to use the commands in javascript mode. Do the following: create a new tab, right click on it, select "set type" and choose "jython". Your code should now work.
I have EasyPHP-deverser-17 installed and working well for months. Today, without any reason (i mean did not change anything), i get these error messages when opening the Dashboard:
Notice: Undefined offset: 3 in C:\Program Files (x86)\EasyPHP-Devserver-17\eds-dashboard\index.php on line 18
Notice: Undefined offset: 3 in C:\Program Files (x86)\EasyPHP-Devserver-17\eds-dashboard\index.php on line 23
I can't figure out what happened and i can't find any solution on how to fix this.
Thank you so much for any help.
Sylvain
If you have not fixed this issue since you asked this question, I found the answer on GitHub:
Step 1 - Download the link file:
Download Link (update): https://drive.google.com/file/d/12rP6-UM2OxO9Qmyn3FHI6AsGSOk4Avni/view?usp=sharing
Step 2 - As administrator authorization is required, authorize it.
Step 3 - On the screen click "Y" to continue ("N" to exit), and wait for the process;
Step 4 - Go to the options to start the servers in the icon that is in the system tray, or go to Dashboard and refresh the page, then start the servers in the HTTP and DB buttons.
I just tried to follow below step worked for me.
Open cmd run as administrator.
Navigate to the C:\Program Files (x86)\EasyPHP-Devserver-17
Type cmd lodctr /r and press enter.
Success to all!
When I start play scala production mode that throw this kind of error please any one give me the clear idea..
F:\New_CMS\trunk\server\cms>activator start
[info] Loading project definition from F:\New_CMS\trunk\server\cms\project
[info] Set current project to cms (in build file:/F:/New_CMS/trunk/server/cms/)
[info] Wrote F:\New_CMS\trunk\server\cms\target\scala-2.11\cms_2.11-1.0-SNAPSHOT.pom
Starting server. Type Ctrl+D to exit logs, the server will remain in background
The input line is too long.
The syntax of the command is incorrect.
Follow these steps as a Windows solution:
activator stage in the command line
Copy the stage directory from target\universal\stage to c:\stage to avoid issues with long file paths
To avoid the Bad Application Path issues just create a new .bat file with the following (my project is called proj): set PROJ_OPTS="-Dconfig.file=../conf/application.conf" proj.bat
Note: change PROJ_OPTS to YOURPROJECTNAME_OPTS and proj.bat to yourprojectname.bat