I have installed version 1.2.1 of weaviate and selected a transformer module. but the /v1/meta endpoint does not display the transformer details. I get the following:
{
"hostname": "http://[::]:8080",
"modules": {
"text2vec-transformers": {
}
},
"version": "1.2.1"
}
Related
I've been trying to add a custom CSS file to the final build from Sencha CMD on ExtJS Application. The application has been generated using the CMD.
My CSS file is located in resources/Custom/myfile.css
try to do many different approach that i found but with no success.
My app.json looks like
{
"builds": {
"production": {
"default": true,
"compressor": {
"type": "closure"
}
}
},
"name": "Test.App",
"css": [
{
"path": "resources/Custom/_body.css",
"remote": true
}
],
"requires": [
],
"id": "fb0cc613-c7e3-4e2e-9f9f-aa569fcf2465"
}
But when try to build i got the error:
BUILD FAILED
[ERR] com.sencha.exceptions.ExBuild: Combining x-compile in HTML page with Microloader in app.json is not supported
If i remove the CSS part fo the app.json it does work !!!
I am using ExtJS 4.1.1
Any Help?
I am trying to update dozens of services to au.com.dius:pact-jvm-consumer-junit_2.12:3.5.12 from au.com.dius:pact-jvm-consumer-junit_2.11:3.2.13 but it seems that the new consumer version is generating pacts that the old provider version (au.com.dius:pact-jvm-provider-junit_2.11:3.2.13) cannot handle.
The old pact had a hashmap with matching rules being added at the root as show below
{
"consumer": {
"name": "consumer-amqp"
},
"provider": {
"name": "prodvider-amqp"
},
"messages": [
{
"description": "amqp contract",
"contents": {
"body": {
"guidProperty": "795ecfd5-a3a5-430f-a0cd-1569df61bff6"
}
},
"matchingRules": {
"$.body.body.guidProperty": {
"regex": "[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}"
}
}
}
],
"metadata": {
"pact-specification": {
"version": "3.0.0"
},
"pact-jvm": {
"version": "3.2.13"
}
}
}
The new consumer adds and wrapper body around the matchers. Below is an example of the same pact generated with the new consumer version
{
"consumer": {
"name": "consumer-amqp"
},
"provider": {
"name": "prodiver-amqp"
},
"messages": [
{
"description": "contract",
"contents": {
"body": {
"guidProperty": "e2490de5-5bd3-43d5-b7c4-526e33f71304"
}
},
"matchingRules": {
"body": {
"$.guidProperty": {
"matchers": [
{
"match": "regex",
"regex": "[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}"
}
],
"combine": "AND"
}
}
}
}
],
"metadata": {
"pact-specification": {
"version": "3.0.0"
},
"pact-jvm": {
"version": "3.5.12"
}
}
}
Because of that change the provider fails to parse the matching rules with the following error:
body
^
10:21:24.526 [main] DEBUG au.com.dius.pact.matchers.JsonBodyMatcher - compareValues: No matcher defined for path List($, body, body, guidProperty), using equality
10:21:24.527 [main] WARN au.com.dius.pact.matchers.Matchers$ - Path expression body is invalid, ignoring: [1.1] failure: `$' expected but `b' found
java.lang.AssertionError:
comparison
{$.body.body.guidProperty=Expected 'e2490de5-5bd3-43d5-b7c4-526e33f71304' but received 'aff876f5-5014-937c-6855-c099f9857437'
Looking at the v3 spec the new message seems to be valid, does the old provider library (v3.2.13) not support it? I looked through the code and found this commit which seems to me where the change was introduced.
From my testing the new provider library (3.5.12) can handle both old and new formats, but if both the new provider and old consumer libraries are present in the classpath http contract tests fail with run-time errors.
Questions:
1) Is there a way to force the new consumer to create the pacts the old way, and is that form spec compliant?
2) Is there a way to update the provider to the new version and still have the old consumer library in the path and not get failures?
As J_A_X pointed out, it looks like the commit you referenced fixed a bug where pacts that were supposed to be version 3 were not fully version 3 compliant (they used the old matchers format)
1) Is there a way to force the new consumer to create the pacts the old way, and is that form spec compliant?
Yes and yes. You should be able to fix this by setting the system property pact.provider.version to 2 - then both the old and the new versions will be able to read the generated pact.
2) Is there a way to update the provider to the new version and still have the old consumer library in the path and not get failures?
Yes, as long as you ask the old consumer version to generate version 2 pacts (but ideally, why not update both to the same version?)
I've got a project that I started on an older version of Meteor and I've now installed the most recent version. I cloned my project code and ran into problems as soon as I ran meteor so I deleted all the files except the smart.json, smart.lock and packages.json
I ran meteor add meteorhacks:npm then meteor to install the node modules I require. It looks like all the packages I need are in the smart.lock file.
This should be really simple, how do I install the most recent version of these packages? I thought just running meteor would pick them up but apparently not. I checked by by doing meteor list and I don't see all the packages I need.
smart.json:
{
"packages": {
"loading": {},
"jquery-jcrop": {},
"accounts-admin-ui-bootstrap-3": {},
"accounts-ui-bootstrap-3": {},
"font-awesome-4-less": {}
}
}
smart.lock
{
"meteor": {},
"dependencies": {
"basePackages": {
"loading": {},
"jquery-jcrop": {},
"accounts-admin-ui-bootstrap-3": {},
"accounts-ui-bootstrap-3": {},
"font-awesome-4-less": {}
},
"packages": {
"loading": {
"git": "https://github.com/bitIO/meteor-loading.git",
"tag": "v0.0.1",
"commit": "48840a828a614e25d0e19c124494b16f255a902e"
},
"jquery-jcrop": {
"git": "https://github.com/waltyuyu/meteor-jquery-jcrop.git",
"tag": "v0.0.3",
"commit": "45a62562f3d13cbc72a7710472a76cf9c3c589cd"
},
"accounts-admin-ui-bootstrap-3": {
"git": "https://github.com/hharnisc/meteor-accounts-admin-ui-bootstrap-3.git",
"tag": "v0.2.6",
"commit": "fe74692303daf73d440f2729010bcf1557af62ca"
},
"accounts-ui-bootstrap-3": {
"git": "https://github.com/mangasocial/meteor-accounts-ui-bootstrap-3.git",
"tag": "v0.3.5",
"commit": "bbd0a8a46ae02526c2ebfee05fa8075d8d04a9ba"
},
"font-awesome-4-less": {
"git": "https://github.com/svub/fontawesome4-less.git",
"tag": "v4.4.0",
"commit": "250d2336a217c18eb70e9d074784a7db3ca38472"
},
"roles": {
"git": "https://github.com/alanning/meteor-roles.git",
"tag": "v1.2.8",
"commit": "68844ba216c348d332bdb840825850f497f515bb"
}
}
}
}
For meteor packages, the one you install using meteor add package:name
Their version are be stored in the .meteor/versions
Running meteor update will update them the last available version
Typing meteor list will list the used packages, their version and a comment if a new version is available.
For pure NPM packages, the one you install through meteorhacks:npm listing them into a root based packages.json file
Their version is and must be defined in the file directly
Example of a packages.json file:
{
"redis": "0.8.2",
"github": "0.1.8"
}
i.e. "NPMModuleName":"releaseVersion", the alternative being to directly poing to the aModule.tar.gz file.
Manually finding the version can be a bit boring but just go to the project's git, and browse to the release path, for example: https://github.com/user/projectName/releases/
My advise in your case, as you do not have a lot of packages to
reinstall, is to manually find their new name on
http://www.atmospherejs.com and reinstall them manually. You could
attempt manually editing the .meteor/packages file but as the
packages name are now (since meteor v0.9) prefixed with the contributor's name, meteor might
not be able to find them back. By the way, unclaimed migrated packages takes the prefix mrt per default For example font-awesome-4-less is now mrt:font-awesome-4-less
I've created a asp.net 5 project and am trying to add a reference to an older package from NuGet (Mysql.Data). From what I've read, I should be able to do this to add pre-vnext packages:
{
"version": "1.0.0-*",
"dependencies": {
},
"commands": {
"run": "run"
},
"frameworks": {
"net45": {
"dependencies": {
"MySql.Data": "6.9.4"
}
},
"aspnet50": { },
"aspnetcore50": {
"dependencies": {
"System.Console": "4.0.0-beta-22416"
}
}
}
}
But all that happens is I get a reference to it in the project browser but there is a yellow triangle next to it. I have seen other similar questions on here but they all suggest the above, but I'm not sure why this doesn't work?
That means that the MySQL library is not supported in aspnetcore5, you can remove the aspnetcore50 JSON node and that will get rid of the warning. Not all libraries are supported in core. See this Question
In addition to what Son_of_Sam said, you need to put this in the dependencies section at the top.
Has anybody ever used Symfony in conjunction with payone(payone.de)?
I got the SDK and it has the folders js, locale and php.
My problem: I don't really know how to include/use them in my project(inexperienced in Symfony) because I don't know where I should place it and how to include it. I read about the auto loader but since the SDK doesn't follow the standards needed(concerning folder structure) I guess it's not the way to go.
You can autoload all classes with the psr-0 too if the classes are following the PEAR-style non-namespaced convention.
To manage the vendor download via composer, you can define a package in your composer.json directly.
{
"repositories": [
{
"type": "package",
"package": {
"name": "payone/php-sdk",
"version": "1.0.0",
"dist": {
"url": "http://github.com/PAYONE/PHP-SDK/archive/master.zip",
"type": "zip"
},
"autoload": {
"psr-0": { "Payone_": "php/" }
}
}
}
],
"require": {
"payone/php-sdk": "1.0.*"
}
}
Note: This repository type has a few limitations and should be avoided whenever possible:
Composer will not update the package unless you change the version field.