I am requiring "elasticsearch/elasticsearch": "^7.1.1" in my Laravel project composer.json file, and when I perform "composer install" it says "- Downloading elasticsearch/elasticsearch (v7.11.0)". However, the actual version that is installed seems to be 6.8.14, as output by the curl -XGET 'http://localhost:9200' command and as displayed in Kibana.
I have tried running "composer clearcache", deleting the vendor folder and composer.lock, rerunning "composer install", then restarting Elasticsearch, but the actual installed version does not seem to change.
Previously Elasticsearch was being installed as a dependency of "ruflin/elastica": "7.*", and it was still installing as version 6.8.14, even though ruflin/elastica": "7.* requires Elasticsearch ^7.1.1.
When we call the \Elastica\Index updateDocument() method in ruflin/elastica, it throws the error "Document mapping type name can't start with '_', found: [_update]" which I assume is being caused by the failure to upgrade the Elasticsearch version. What is the best way to fix this?
Related
Question
I'm new to Substrate and going through Add a Pallet to Your Runtime. At first, running the command cargo check -p node-template-runtime gave me error
error: failed to parse manifest at `/Users/bashar/work/substrate/start/substrate-node-template/pallets/template/Cargo.toml`
Caused by:
feature `rename-dependency` is required
consider adding `cargo-features = ["rename-dependency"]` to the manifest
I added it and then I started getting this error:
error: no matching version `^2.0.0` found for package `codec`
location searched: registry `https://github.com/rust-lang/crates.io-index`
versions found: 0.0.0
required by package `frame-benchmarking-cli v3.0.0`
... which is depended on by `node-template v3.0.0 (/Users/bashar/work/substrate/start/substrate-node-template/node)`
I tried modifying the codec version to 2.0.1 with no luck. My setup
rustup 1.23.1
rustc 1.50.0
cargo 1.30.0
Any idea what I'm doing wrong?
UPDATE
I went back to the Create Your First Substrate Chain, which this tutorial is built on, started from scratch, which the Pallet tutorial is based on. And this time, after cloning the repository for first tutorial, cargo build --release failed with the same error feature rename-dependency is required.
This built fine the first time before I moved to the second tutorial. Which makes me think maybe a recent Mac update ruined something? I even tried uninstalling Rust and re-installing it, then installing a new template. Same thing
I am trying to install M2ePro module on my Magento ver. 2.1.8 application using composer and getting this error:
[http]$ php-7.0 /usr/local/bin/composer require m2e/ebay-amazon-magento2
Could not find a matching version of package m2e/ebay-amazon-magento2.
Check the package spelling, your version constraint and that the
package is available in a stability which matches your
minimum-stability (alpha).
The spelling of the package is correct, I have tried defining the version of the module (The only one available is 1.3.2):
[http]$ php-7.0 /usr/local/bin/composer require m2e/ebay-amazon-magento2:1.3.2
However get the same error so I believe stability of this module is "Beta" and I have "minimum-stability (alpha)" set so beta modules should be installed with no problems.?
I looked for solution in composer docs but could find anything about installing beta: https://getcomposer.org/doc/03-cli.md#require
Or was I looking in the wrong place?
I managed to successfully install the module on my development site and didn't receive this error so I thought it might be due to the fact that my Magento application was in the "Production" mode but setting the mode to "Developer" did not solve my problem.
UPDATE:
I just found this thread: https://magento.stackexchange.com/questions/114393/error-in-using-composer-to-install-a-module-in-magento-2-0. The answer to this question is that you need to define the package as repository. The package is from marketplace and this is content of my composer.json:
"minimum-stability": "alpha",
"prefer-stable": true,
"repositories": [
{
"type": "composer",
"url": "https://repo.magento.com/"
}
],
I have previously installed modules from marketplace using composer with no problems.
It came out that my auth.json had incorrect credentials and couldn't find the account.
Correcting the account settings fixed my problem.
After installing a new version of a Magento 2 module composer fails on every command. Also the backend of Magento isn't working anymore:
1 exception(s):
Exception #0 (UnexpectedValueException): Package magento/composer's
source key should be specified as {"type": ..., "url": ...,
"reference": ...},
{"type":"git","url":"https:\/\/github.com\/magento\/composer.git","reference":null} given.
Also when using composer -v command via ssh the same error is showing.
When trying to flush the cache via ssh the same error is showing and also an extra error:
Fatal error: Uncaught Error: Class 'Cli' not found in
Does anyone know how to fix this?
Few things you can try:
Try to reinstall composer.
Also you can try running composer clear-cache. Also check for any running composer process and kill then first.
If this is still an issue anyone has I found through much digging that reference cannot be set to null. If a download from source is necessary than I recommend moving up a directory for your url or use a dist instead of source
OS : 'CentOS 6.5
'
ElasticSearch version : '2.3.0'
Master's puppet version: '3.8.7'
Client's puppet version : '3.7.4'
Base module version before upgrade : '0.10.2'
Base module version after upgrade : '5.1.0'
Error: could not retrieve catalog from remote server: Error 400 on
SERVER: invalid parameter elasticsearch_package_name on
Elasticsearch_plugin[license] at
/etc/puppet/environments/production/modules/elasticsearch/manifests/plugin.pp:169
on node bla-test01.dom'
Hi,
This error started after we upgraded our Elasticsearch's base (Official from puppet forge) module from version '0.10.2' to '5.1.0'. Our puppet module of elasticsearch worked just fine before the upgrade.
Since the upgrade this error occurred whenever puppet ran on our nodes.
After we saw this case we tried to restart our puppetserver service. Since the restart, the error occurs once every 3-4 runs of puppet and we have no idea why.
Looking at the elastic/elasticsearch module which is the one you seem to be using i can see that the elastic_plugin custom type did not have the elasticsearch_package_name parameter in version 0.11.0 however the 5.1.0 version does. This looks to me that you may have updated the module on the system but have not restarted the puppet server so it still has the 0.11.0 custom type/provider ruby files loaded.
Restart the puppet master server and see if that fixes the issue
I'm using CentOS7; tried downloading the golang 1.5.1 binary and also yum install golang, and run into the same problem installed revel. Go works fine; when I do go version it displays the proper version.
When I type go get -v github.com/revel/revel, a few packages download just fine.... until it gets to fsnotify. Then I get this output:
Fetching https://gopkg.in/fsnotify.v1?go-get=1
Parsing meta tags from https://gopkg.in/fsnotify.v1?go-get=1 (status code 200)
get "gopkg.in/fsnotify.v1": found meta tag main.metaImport{Prefix:"gopkg.in/fsnotify.v1", VCS:"git", RepoRoot:"https://gopkg.in/fsnotify.v1"} at https://gopkg.in/fsnotify.v1?go-get=1
gopkg.in/fsnotify.v1 (download)
And it just freezes. No matter what I try, it doesn't download anything into src/gopkg.in/fsnotify. Files in src/github.com and src/golang.org are pulled just fine. I already made sure I'm able to curl into http://gopkg.in and https://gopkg.in, so it doesn't look like an SSLv3 issue.
Any ideas?
Upgrade Git so that it is greater than 1.7.1 (latest CentOS base version). Try rpmforge first; if that doesn't work, compile from source: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git#Installing-from-Source
I'm on Git 2.6.2 and it's working fine now: go get -v github.com/revel/revel (-v for verbose mode)