Recently (I'd say since around 2 weeks ago) LUIS has been getting some of the dates wrong for us. And indeed: datetimeV2's start date seems off by a month. Is it a bug or am I misunderstanding this value?
Ex: "since august" returns a start date of 2017-09-01 instead of 2017-08-01.
{
"entity": "since august",
"type": "builtin.datetimeV2.daterange",
"startIndex": 15,
"endIndex": 26,
"resolution": {
"values": [
{
"timex": "XXXX-08",
"type": "daterange",
"start": "2017-09-01"
},
{
"timex": "XXXX-08",
"type": "daterange",
"start": "2018-09-01"
}
]
}
}
I can confirm this is an issue. Since is currently being handled with the same regex that is being used to handle after so the reason of the issue.
In the next days, we will create PR with a proposed fix and I will update this answer with the link to it. We will separate the regexes.
Update
A fix for this issue was created and this is the PR for it.
Related
result = requests.get('http://d.yimg.com/autoc.finance.yahoo.com/autoc?query=tesla&callback=YAHOO.Finance.SymbolSuggest.ssCallback').json()
result
When I run the python code above, I get <Response [404]>, does anyone know why that might be? I am worried this API no longer works even though I saw posts from just a year ago talking about it working.
If it's not documented, you can't rely on it working. The only (relatively) sure bet is to use some official API instead (which usually comes at a cost).
That said, if you want to continue using undocumented stuff (with the same risk of it getting shut down or you getting blocked any day), give this a try:
https://query2.finance.yahoo.com/v1/finance/search?q=tesla
(I looked at what https://finance.yahoo.com/ uses.)
This delivers results like these:
{
"explains": [],
"count": 15,
"quotes": [
{
"exchange": "NMS",
"shortname": "Tesla, Inc.",
"quoteType": "EQUITY",
"symbol": "TSLA",
"index": "quotes",
"score": 2048451,
"typeDisp": "Equity",
"longname": "Tesla, Inc.",
"exchDisp": "NASDAQ",
"isYahooFinance": true
},
{
"exchange": "NEO",
"shortname": "TESLA, INC. CDR (CAD HEDGED)",
"quoteType": "EQUITY",
"symbol": "TSLA.NE",
"index": "quotes",
"score": 24083,
"typeDisp": "Equity",
"longname": "Tesla, Inc.",
"exchDisp": "NEO",
"isYahooFinance": true
},
// ...
],
"news": [
// Also delivers news here...
],
// Some meta stuff here
}
Use at your own risk.
Can you inspect and explain the problem not to get error?
This is Pirl Source Code
https://github.com/pirl/pirl-2_0
(at v0.8.25-ad031f3)
This is pirl polkadotjs.org clone at version at (api v2.2.2-2 ,apps v0.62.2-2 check right top at link)
https://dashboard.pirl.network/
custom endpoint: wss://rpc.pirl.network
When i try to transfer coins i got this error
Pirl has their own (now stale and seemingly unmaintained) fork of the Polkadot UI:
https://github.com/pirl
I would recommend using their own products and also read their docs that detail how to use it properly.
EDIT: Looks like there is a solution here https://github.com/paritytech/subport/issues/139
it worked after i set the custom type json (julien, #masterdubs, pirl coin developer, have given me this json
{
"Address": "AccountId",
"LookupSource": "AccountId",
"Account": {
"nonce": "U256",
"balance": "U256"
},
"Transaction": {
"nonce": "U256",
"action": "String",
"gas_price": "u64",
"gas_limit": "u64",
"value": "U256",
"input": "Vec",
"signature": "Signature"
},
"Signature": {
"v": "u64",
"r": "H256",
"s": "H256"
},
"Keys": "SessionKeys5"
}
I'm using the latest elk image for kibana dashboard and I have json file which is having list of array[] and I'm not able to show those as field in kibana and It's showing that the object in array is not well supported error message.
As per the document in kibana I just went through the below link but I didn't find anything useful for elk docker image.
https://github.com/istresearch/kibana-object-format
I just tried to run the command
Run bin/kibana-plugin install <package.zip>
but it returned as run is unknown command removed run and ran remaining command but It says that's invalid.
I'm using linux box and Kibana 7.3 version.
Is it possible to overcome this issue? how to deploy that plugin for elk image else is there any other way to make those arrays object as fields in kibana.
I'm not sure how can I proceed. Please help me.
Sample Data:
{
"expand": "schema,names",
"startAt": 0,
"maxResults": 50,
"total": 4,
"issues": [{
"expand": "operations,versionedRepresentations,editmeta,changelog,renderedFields",
"id": "1999875",
"self": "https://amazon.kindle.com/jira/rest/api/2/issue/1999875",
"key": "KINDLEAMZ-67578",
"fields": {
"summary": "contingency is displaying for confirmed card.",
"priority": {
"name": "P1",
"id": "1"
},
"created": "2019-09-23T11:25:21.000+0000"
}
},
{
"expand": "operations,versionedRepresentations,editmeta,changelog,renderedFields",
"id": "2019428",
"self": "https://amazon.kindle.com/jira/rest/api/2/issue/2019428",
"key": "KINDLEAMZ-68661",
"fields": {
"summary": "card",
"priority": {
"name": "P1",
"id": "1"
},
"created": "2019-09-23T11:25:21.000+0000"
}
},
{
"expand": "operations,versionedRepresentations,editmeta,changelog,renderedFields",
"id": "2010958",
"self": "https://amazon.kindle.com/jira/rest/api/2/issue/2010958",
"key": "KINDLEAMZ-68167",
"fields": {
"summary": "Test Card",
"priority": {
"name": "P1",
"id": "1"
},
"created": "2019-09-23T11:25:21.000+0000"
}
}
]
}
I just want to fetch KEY, Summary, Priority from each of the above array. But its not working as expected when I tried to make a field its showing as array in kibana. If this is not working with 7.3.0 should I downgrade to lower version? the steps are missing for docker user in that document. Is there any way to get those details?
Checking here: https://github.com/istresearch/kibana-object-format/releases it looks like the plugin latest release was for Elasticsearch 6.3. I guess that is the reason for your error.
I'm not sure there's a fix for this in kibana. There are many issues on this subject, open for a long time, like: https://github.com/elastic/kibana/issues/3333.
LUIS doesn't handle the below correctly.
Example utterance:
From Friday the 26th until Tuesday the 30th
Response:
"entities": [
{
"entity": "from friday the 26th until tuesday",
"type": "builtin.datetimeV2.daterange",
"startIndex": 0,
"endIndex": 33,
"resolution": {
"values": [
{
"timex": "(2018-01-26,XXXX-WXX-2,P-2.33532467143519D)",
"type": "daterange",
"start": "2018-01-26",
"end": "2018-01-23"
}
]
}
}
]
The date range resolved is not legal, due to a failure to identify "the 30th" as part of the date.
I should note that this doesn't seem to be a question, and that the moderators would probably prefer to have you posit an actual question next time as opposed to an observation.
In the future, please submit prebuilt entity-related bugs to our repo, Recognizers-Text. I've gone ahead and created an issue there that stems from this question.
Update (2018/01/31):
This issue has been fixed and is in the pipeline awaiting release, thank you for reporting this!
I have added the resources via the 'add new' button next to resources and then in my code I am executing
image_logo = gbitmap_create_with_resource(RESOURCE_ID_IMAGE_APP_LOGO_LONG);
but I am getting the following compilation error:
../src/main.c: In function 'main':
../src/main.c:120:44: error: 'RESOURCE_ID_IMAGE_APP_LOGO_LONG' undeclared (first use in this function)
../src/main.c:120:44: note: each undeclared identifier is reported only once for each function it appears in
Waf: Leaving directory `/tmp/tmpGhVqKn/build'
Build failed
Here is what my appinfo.json file contains, I downloaded this from the settings section for the app. You can see that the images have been added with the same identifier.
{
"appKeys": {
"agency": 0,
"cleanStops": 11,
"error": 10,
"eta": 8,
"getEta": 9,
"getRoutes": 5,
"index": 1,
"refresh": 4,
"routeId": 6,
"routeName": 7,
"stopId": 2,
"stopName": 3
},
"capabilities": [
"location",
"configurable"
],
"companyName": "joshua103us#yahoo.com",
"longName": "DoublePebble",
"projectType": "native",
"resources": {
"media": [
{
"file": "images/doublemap_menu_icon.png",
"menuIcon": true,
"name": "IMAGE_DOUBLEMAP_MENU_ICON",
"type": "png"
},
{
"file": "images/spoon_long_med-2.png",
"name": "RESOURCE_ID_IMAGE_APP_LOGO_LONG",
"type": "png"
}
]
},
"sdkVersion": "3",
"shortName": "DoublePebble",
"targetPlatforms": [
"aplite",
"basalt"
],
"uuid": "409b7111-c0bf-43bd-a90c-8a44c33d1eb3",
"versionLabel": "1.0",
"watchapp": {
"watchface": false
}
}
The RESOURCE_ID_ part of the resource identifier is added by the system to the name you specify in appinfo.json
For example:
{
"file": "images/doublemap_menu_icon.png",
"menuIcon": true,
"name": "IMAGE_DOUBLEMAP_MENU_ICON",
"type": "png"
},
You would then use RESOURCE_ID_DOUBLEMAP_MENU_ICON.
In my case I experienced the same problem in the Cloudpebble environment, apparently even after formatting the image with http://www.watchface-generator.de/converter/ and saving the resource following Pebble tutorials it was like if CloudPebble still wouldn't recognize. It only did after i clicked on "Run Build" in the compile section of CloudPebble environment...just trying to save other some precious time :)
Another useful note when working in the Cloudpebble environment is you can hover over the name of the resource file and it will say the name of the identifiers.
For whatever reason mine showed up as different names than what I thought I had saved them as in the settings. Going in and editing the name (even if you just delete something and save the same name after editing it) and saving it should fix the issue. But in my case, just deleting the resource and then uploading it again seemed to resolve my issue. I suspect I might have had set them up as multiple identifiers. There is an "Another Identifier" button at the bottom of the page and I think that what was my issue. You can see this when you hover over the file and it has multiple names as identifiers (even if they are the same name).