I followed the instructions on https://quarkus.io/get-started/ and build this demo using the latest quarkus(2.7).
My java environment is:
when I run quarkus dev it turns out fine like this:
But when I access http://localhost:8080/hello I got an 404 like this:
I should have got a string "Hello RESTEasy" as the demo code is like:
Can any one tell me why would this happen?
Related
I've been following the example shown here:
https://www.youtube.com/watch?v=w6JlZpYMvpo&list=PL9tzQn_TEuFXdfbkEw5_16Dsf0F6QLDmL&index=21&t=900s
The repo is here:
https://github.com/Learn-NEAR/NCD.L1.sample--thanks
As I tried to run ./scripts/1.dev-deploy.sh, and this was returned:
The Error Shot
I'd love to know if I did anything wrong here and if so what the solution would be.
From the error about a missing dependency, I think you forgot to run yarn
I've updated the instructions to include this as step #2
## Usage
### Development
To deploy the contract for development, follow these steps:
1. clone this repo locally
2. run `yarn` to install dependencies
3. run `./scripts/1.dev-deploy.sh` to deploy the contract (this uses `near dev-deploy`)
**Your contract is now ready to use.**
I'm trying to run cypress on CircleCI, but I can't find any good guides on how the "orb" works other than this: https://circleci.com/orbs/registry/orb/cypress-io/cypress
In my config.yml file, this is the only configuration that I can get to work on CircleCI
version: 2.1
orbs:
cypress: cypress-io/cypress#1
workflows:
build:
jobs:
- cypress/run:
executor: cypress/browsers-chrome69
browser: chrome
This runs all the tests, and that's basically all I need. However, I think it's running on chrome version 69, which is really old. When I try to make it any other version of chrome, the executor is not recognized.
How do I set the chrome browser version?
Also, it would be nice to have more control over which tests to run, rather than simply run them all. How do I do that?
Any references to good guides for cypress + circleci would be appreciated.
Refer to the list of prebuilt containers here and replace executor with one of the options in the "Base Image" column https://github.com/cypress-io/cypress-docker-images/tree/master/browsers#cypressbrowsers
In addition, refer to the circle.yml in the Cypress Real World App for a reference of how the executor is composed.
I am using the MeanJS (https://github.com/meanjs/mean) framework, running on Heroku. When I try to run the application I get errors like:
Error: Cannot find module 'eslint-config-airbnb/legacy'
I am running in production mode (NODE_ENV=production).
The question I have is, it seems like gulpfile.js (when running the task prod) calls the task lint which calls the task eslint. But when I look at the packages.json file, I see that eslint-config-airbnb is only included in the devDependancies (and not dependancies). Now I tired to add it to dependancies, but I still get the same error about the missing module.
I'm new to MEAN.js, so I appreciate any help.
I am following the Build Larabook from scratch Laracasts tutorial (building a Facebook-like app).
In lesson 14, we implement the "sign in" feature.
Problem, when I try to run my functional test (that has been running smoothly so far), I get nothing, not even an error message:
vagrant#homestead:~/larabook$ vendor/bin/codecept run functional
Codeception PHP Testing Framework v2.0.7
Powered by PHPUnit 4.3.4 by Sebastian Bergmann.
Here is the content of my SignInCept.php:
$I = new FunctionalTester($scenario);
$I->am('a Larabook member');
$I->wantTo('login to my Larabook account');
$I->signIn();
$I->seeInCurrentUrl('/statuses');
$I->see('Welcome back!');
I tried to log out of my Vagrant vm but kept getting the same issue.
Is it possible that I broke something while updating some files?
Check carefully your signIn action in FunctionalHelper for any syntax errors. Tests fail like this without showing any errors when there is something wrong in there.
Late answer but do not use composer exec. Use the full path to codeception.
For example:
**vendor/bin/codecept run**
Running yeoman server:test opens Jasmine in my browser and says that my test has passed. Now I want to try the same, but without a browser - using PhantomJS on the CLI. Unfortunately, running yeoman test only throws a:
Running "jasmine:all" (jasmine) task
Running specs for index.html
>> 0 assertions passed in 0 specs (0ms)
Why doesn't it find any tests, even though everything is included in my test/index.html and works pretty well using yeoman server:test?
I used yeoman init jasmine:app --force over my project and adjusted the Gruntfile.js as described here. It looks like that:
...
// headless testing through PhantomJS
jasmine: {
all: ["test/**/*.html"]
},
...
// Alias the `test` task to run the `jasmine` task instead
grunt.registerTask("test", "jasmine");
...
Note: My tests are written in CoffeeScript.
After some research I found out that PhantomJS is not able to find the files at the same location as ´yeoman server´ or yeoman server:test does.
I precised my question in another thread: Running tests in both headless and browser