I am trying to install ezpublish platform 15.05.02. When i run composer update i get the following error
[Symfony\Component\DependencyInjection\Exception\ParameterNotFoundException]
The service "ezplatform.installer.install_command" has a dependency on a non-existent parameter "search_engine". Di
d you mean one of these: "ezpublish.api.search_engine.class", "ezpublish.api.search_engine.factory.class", "ezpubli
sh.api.search_engine.default"?
You can add search_engine: legacy to ezpublish/config/parameters.yml to satisfy this requirement.
Just a note here, you can now use eZ Launchpad to bootstrap your project on top of Docker very easily.
https://ezsystems.github.io/launchpad/
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 actually found the answer to this question already, and just want to document my finding.
First of all, this problem is not specific to building the leveldown module for Windows PouchDB. From what I have read online, it is a fairly common problem.
It has to do with the fact that nw-gyp somehow forgot the target version of NW between the nw-gyp configure and nw-gyp build command. When this happens, a TyperError: Invalid Version: undefined would be thrown.
The solution is actually very simple, all you need to do is to set --target= again when you do nw-gyp build, like this:
nw-gyp configure --target=0.47.0
nw-gyp build --target=0.47.0
I have a React application with ApolloClient with Apollo-Link-Schema. The application works fine locally but in our staging environment (using GOCD), we get the following error:
Uncaught Error: Cannot use e "__Schema" from another module or realm.
Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.
https://yarnpkg.com/en/docs/selective-version-resolutions
Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.
at t.a (instanceOf.mjs:21)
at C (definition.mjs:37)
at _ (definition.mjs:22)
at X (definition.mjs:284)
at J (definition.mjs:287)
at new Y (definition.mjs:252)
at Y (definition.mjs:254)
at Object.<anonymous> (introspection.mjs:459)
at u (NominationsApprovals.module.js:80)
at Object.<anonymous> (validate.mjs:1)
Dependencies are installed with yarn, I've added the resolutions field to the package.json.
"resolutions": {
"graphql": "^14.5.8"
},
I've checked the yarn.lock and can only find one reference for the graphql package.
npm ls graphql does not display any duplicates.
I thought maybe its a build issue with webpack - I have a different build script for staging, but running that locally I am still able to get the react application to run with that bundle.
Can anyone suggest anything else to help me fix this?
I managed to find the cause of the issue, if this helps anyone else. The issue is not to do with duplicate instances of the package at all, this is a false positive triggered by us using webpack's DefinePlugin to set the process.env.NODE_ENV to staging for our staging build.
However, in webpack the mode (see https://webpack.js.org/configuration/mode/), which sets the process.env.NODE_ENV, only accepts none, development and production as valid values. This was triggering an env check in the graphql package to fail and trigger this error message.
In our case, we need to differentiate between staging and production as our API endpoint differs based on this, but the solution we implemented is to not rely on the process.env.NODE_ENV, but to assign a custom variable on build (e.g. process.env.API_URL)
I would try to replicate the error locally and debug it:
try this:
rm -rf node_modules yarn.lock
# also remove any lock files if you have package-lock.json too
yarn install
# build the project locally and see if you got the error
I got this problem one time where I was working with Gatsby and 2 different themes where using different versions of GraphQL. Also be more explicit with the version (without caret) and check if the error persist.
do you have a repo youc an share? that would also help us to help you :)
While changing NODE_ENV to production might solve the issue, if you have different variables for each environment and don't want to mess with your metrics this is not an ideal solution.
You said you use webpack. If the build with the issue uses some kind of source-map in your devtool, you might want to disable that to see if the problem persists. That's how I solved this without setting my NODE_ENV to production.
I had a similar problem when trying to run Apollo codegen and was able to fix it by deduping my npm packages. Run this:
rm -rf node_modules && npm i && npm dedupe
I was having this problem so I switched to yarn, and after deleting node_modules and npm lockfile, then running yarn, the problem went away :-).
I ended up here because I use the AWS CDK and the NodejsFunction Construct. I was also using bundling with minify: true.
Toggling minify to false resolved this for me.
Apparently there are two ways to configure scrutinizer-ci to use custom phpCodeSniffer standards. The documentation only mentions phpcs use in "build" node and it isn't clear if they do different things or if one is preferred over the other.
Docs reference: https://scrutinizer-ci.com/docs/tools/php/code-sniffer/
What's the difference between running the checks inside "build" or "checks"? Should I use both?
checks:
php:
custom_coding_standard:
ruleset_path: 'ruleset.xml'
build:
tests:
override:
- 'phpcs-run --standard=ruleset.xml'
The official answer was to use phpcs-run.
build:
tests:
override:
- 'phpcs-run --standard=ruleset.xml'
The phpcs-run wrapper retrieves the latest version of phpcs on every build. Otherwise a preinstalled version of it is used. So usually the best way of running phpcs is using the wrapper in the build section.
I am trying to install the "secureportaladdon". While installing it using the command:
ant addoninstall -Daddonnames="secureportaladdon" -DaddonStorefront.yb2bacceleratorstorefront="yb2bacceleratorstorefront"
I am getting the error
BUILD FAILED C:\work\trail\hybris\bin\ext-addon\addonsupport\resources\addonsupport\ant\acc-ant-addons.xml:592: The following error o ccurred while executing this line: C:\work\trail\hybris\bin\ext-addon\addonsupport\resources\addonsupport\ant\acc-ant-addons.xml:508: The following error o ccurred while executing this line: C:\work\trail\hybris\bin\ext-addon\addonsupport\resources\addonsupport\ant\acc-ant-addons.xml:354: Storefront template p arameters are missing. Set at least one storefront parameter (addonStorefront...) in command line : ant addoninstall -Da ddonnames="AddOnName1,AddOnName2" -DaddonStorefront.yacceleratorstorefront="B2CStorefront1,B2CStorefront2" -DaddonStoref ront.yb2bacceleratorstorefront="B2BStorefront1,B2BStorefront2"
Am i missing any template property to be set in the accelerator? Please help.
first of all, did you include < extension name="secureportaladdon" /> in the localextensions.xml file?
If so, instead of the ant command to install the addon you can alternatively add the "secureportaladdon" to < requires-extension > in the extensioninfo.xml file of your storefront.
Now, is "yb2bacceleratorstorefront" the storefront you want to add it to?
You can go to the administration console and check in platform/extensions, see if that extension you want is included and if its the one you want to use. If you have used the accelerator to generate your own storefront you would need to install it in yourgeneratedshopstorefront.