I try to follow the tutorial for the First Application of Quarkus.
When I try to run this command: ./mvnw compile quarkus:dev:
I've the following error:
The specified path could not be found. "D" is not recognized as an
internal or external command, an executable program or a batch file.
The specified path could not be found.
Exception during "DownloadFile" call with "2" argument (s): "Exception during a WebClient request." In line: 1 car: 282
... pe] :: Tls12; $ webclient.DownloadFile ('https://repo.maven.apache.org/ma ...
CategoryInfo: NotSpecified: (:) [], MethodInvocationException
FullyQualifiedErrorId: WebException
Error: cannot find or load the main class org.apache.maven.wrapper.MavenWrapperMain"
The problem was used the command prompt of Windows instead the Linux Command Line.
Related
I installed node.js and installed cypress also, but everytime I try to open cypress, I am getting this error:
cypress : The term 'cypress' is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling
of the name, or if a path was included, verify that the path is
correct and try again. At line:1 char:1 + cypress open --browser +
~~~~~~~ + CategoryInfo : ObjectNotFound: (cypress:String) [],
CommandNotFoundException + FullyQualifiedErrorId :
CommandNotFoundException
I tried -> npm run cypress:open
and the cypress window says "Not Responsding"
Could anyone please help as I tried everything
I did try adding this in Package.json file
{
"scripts": {
"test": "cypress open"
}
}
I am using Allure report for my WebDriverIO mocha test automation. Report generation was working fine however, it started showing below error while running 'allure generate allure-result' command.
allure : The term 'allure' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
allure genertae
CategoryInfo : ObjectNotFound: (allure:String) [], CommandNotFoundException
FullyQualifiedErrorId : CommandNotFoundException```
This is my package.json devDependencies
"devDependencies": {
"#wdio/allure-reporter": "^7.16.11",
"#wdio/cli": "^7.16.13",
"#wdio/local-runner": "^7.16.13",
"#wdio/mocha-framework": "^7.16.13",
"#wdio/spec-reporter": "^7.16.13",
"chromedriver": "^97.0.2",
"mocha-allure-reporter": "^1.4.0",
"wdio-chromedriver-service": "^7.2.6"
},
What could be the reason for this failure and how to handle it?
Run:
npm install -g allure-commandline --save-dev
Resolved the issue for me.
Reference: https://www.npmjs.com/package/allure-commandline
Thanks
we have an Ansible script to deploy software on Windows. One of the task if to check the existence of a folder with win_stat command.
However, om some servers, the task throws an error when a path that doesn't exist is defined in the 'LIB' environment variable on the windows server (the path has nothing to do with what we check)
I'm able to reproduce with a dead simple script:
- hosts: all
gather_facts: no
tasks:
- name: Check addon folder
win_stat:
path: 'C:\temp\'
and the error is (with verbose):
The full traceback is:
(0) : Warning as Error: Invalid search path 'System.Collections.DictionaryEntry' specified in 'LIB environment variable' -- 'The system cannot find the path specified. '
(1) : using Microsoft.Win32.SafeHandles;
At line:408 char:5
+ Add-Type -TypeDefinition $link_util
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Power...peCompilerError:AddTypeCompilerError) [Add-Type], Exception
+ FullyQualifiedErrorId : SOURCE_CODE_ERROR,Microsoft.PowerShell.Commands.AddTypeCommand
ScriptStackTrace:
at Load-LinkUtils, <No file>: line 408
at <ScriptBlock>, <No file>: line 76
fatal: [IADCMP019]: FAILED! => {
"changed": false,
"msg": "Unhandled exception while executing module: (0) : Warning as Error: Invalid search path 'System.Collections.DictionaryEntry' specified in 'LIB environment variable' -- 'The system cannot find the path specified. '\n\n(1) : using Microsoft.Win32.SafeHandles;\n"
}
Problems happens with 2.11.6 and 2.11.4 of Ansible core, but not with 2.10 (at least 2.10.9)
I'm wondering if it's a new check in 2.11 or if it's something I should open a bug report about.
EDIT1: changed 'c:' to 'c:\temp' as the win_stat command is long on the former, much faster on the later
I wasn't looking in the right repository for this. The bug is already opened, on ansible.windows collection : https://github.com/ansible-collections/ansible.windows/issues/297
I am attempting to execute a ruby script via WinRM
ruby "R:\Scripts\testDir.rb"
that contains the following code:
Dir.foreach("\\\\FileServer\\TestDir\\") { |x|
puts "Found #{x}"
}
I have no problems executing the script locally on the server, but it fails with the following Permission Denied error via WinRM:
ruby : R:/Scripts/testDir.rb:1:in `open': Permission denied # dir_initialize - \\FileServer\TestDir\ (Errno::EACCES)
+ CategoryInfo : NotSpecified: (R:/Scripts...(Errno::EACCES):String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
from R:/Scripts/testDir.rb:1:in `foreach'
from R:/Scripts/testDir.rb:1:in `<main>'
When running the script locally, I get the following output.
Found .
Found ..
Found test.txt
Found test.tar.xz
My guess is that my script is failing because of the . and .. returned values being passed through WinRM, but I am not sure why.
The issue I was having was caused by double-hopping. The command I was running to execute the ruby script was from my local machine via WinRm.
I'm using vagrant on windows 8, with the hyper-v provider starting a windows server 2012 box.
Before I updated to vagrant 1.7.4 I was on version 1.7.2, and everything worked.
But after updating I am getting an error when it is trying to mount the shared folder:
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
cmdkey /add:xxx.xxx.xxx.xxx /user:DOMAIN\user /pass:Password
Stdout from the command:
Stderr from the command:
Exception calling "RegisterTaskDefinition" with "7" argument(s): "The user
name or password is incorrect. (Exception from HRESULT: 0x8007052E)"
At C:\tmp\vagrant-elevated-shell.ps1:58 char:1
+ $folder.RegisterTaskDefinition($task_name, $task, 6, $username, $password,
1, $n ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
I have replaced the details from the line:
cmdkey /add:xxx.xxx.xxx.xxx /user:DOMAIN\user /pass:Password
With placeholders for obvious reasons. I did try and run the command above in the VM and I get the following output:
CMDKEY: Credential added successfully.
So I assume it is working correctly. Has something changed or broken in 1.7.4?
I have figured out a fix for this.
Our password contained dollar signs ($), these were being stripped out in the vagrant-elevated-shell.ps1 script.
I have forked the vagrant repo and made the change and made a pull request - https://github.com/mitchellh/vagrant/pull/6452
To patch your local environment, you can find the communicator.rb file on your local machine at:
C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.4\plugins\communicators\winrm\communicator.rb
(provided you used the default setting in the installer)