I've got a New Relic application set up and I'm used to check the "Compare with yesterday and last week" button in APM in order to analyse long term trends in the metrics.
Today this checkbox has disappeared. Is it related to my price plan or somehting to do with data retention? I am using New Relic as a Heroku addon and I did not receive any message mentioning this restriction so I am not sure if this is a bug or the end of a trial period that I am not aware of.
Make sure that you're on the "Overview" tab, the time picker is set to "Ending now" and you're viewing the Transaction Time Chart (as opposed to the Transaction Histogram or Transaction Percentile view).
See this thread on the New Relic Technical Community for a similar reported issue.
Related
We converted country/states in Salesforce to the standard picklist. Heroku doesn't seem to reflect those changes as we get loads of errors in Heroku like the one below when Heroku syncs with SF. I re-polled the account object in Heroku to refresh the account table but still the same errors. The country/state picklists are considered meta data in Salesforce in case that helps to understand the issue. Does anyone know what needs to be done in Heroku in order to get the updated list of countries/states that is now in Salesforce?
"AccountsTrigger: execution of AfterUpdate caused by:
System.DmlException: Update failed. First exception on row 2 with id
0033X00003solkfQAA; first error: FIELD_INTEGRITY_EXCEPTION, There's a
problem with this state, even though it may appear correct. Please
select a state from the list of valid states.: Mailing State/Province:
[MailingState] Class.AccountHandler.HandleAfter: line 154, column 1
Trigger.AccountsTrigger: line 17, column 1"
You might have more luck on dedicated salesforce.stackexchange.com site. It's hard to say, sounds like error thrown from a trigger handler but you didn't post any code. Would be also good to know what do you have, the Heroku Connect product or some custom integration that happens to be deployed on Heroku?
https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/compound_fields_address.htm what are you mapping in your integration. Account.BillingCountry or Account.BillingCountryCode?
Worst case you could try contacting support
I was recently investigating an issue related to a delay in rendering a welcome/greeting message for the first time when webchat is launched. The very first activities network request (before showing the welcome/greeting message) is usually 2-6s long(mostly it's either 2.5s or 5-6s). We are trying to implement this using BotFramework webchat version: 4.10.1 with react (minimizable version).
What I'm trying to accomplish is to load welcome/greeting message faster than the current time and upon checking the performance profile I found that activities network request(directline.botframework.com/v3/directline.../activites) is taking either ~2.5s or ~5.5s and after that, there is some more buffer time in between before the welcome message gets rendered.
I tried to record the performance profile of both cases(2.5s/5-6s)
2.5s
https://i.imgur.com/InEyHxl.gif
5s
https://i.imgur.com/yl3l6Z8.gif
Trying to find more information on how to improve/fix this behavior and gain more insights on this. I would be really glad if anyone can share your thoughts on this issue. Please let me know if I need to provide more information.
This is probably a bug that should be solved in a more recent version of webchat
bugreport in github
we have an OBIEE 12.2.1.3.0 server in Linux that currently only has this OBI bundle patch applied:
29112070;OBI BUNDLE PATCH 12.2.1.3.190416
Since then, there have been 6 more bundle patches that have been released. I was wondering if each one has to be installed in the order they were released as they are considered cumulative, however on Oracles support site they show that they are all superseded by the latest, because well, they are all older than the latest bundle patch.
The latest patch is #32294042, and I was wondering if just that could be installed as it has these patches listed in the 'Bugs Fixed By This Patch" section:
OBI Bundle Patch 12.2.1.3.201216
24566569: DRILL-DOWN ERROR: SPECIFIED DRILL-DOWN SELECTION DOES NOT EXIST
27124002: PROCESSES USING BISERVER SSL STACK HANG AT 100% CPU WAITING FOR CLIENT DATA
31448057: Fix for Bug 31448057
30023519: Fix for Bug 30023519
26631503: EMAIL BODY IS RENDERING IN ONE LINE, WHEN SETTING EMAIL AS DESTINATION
31583579: Fix for Bug 31583579
30909437: Fix for Bug 30909437
31752569: Fix for Bug 31752569
31055308: Fix for Bug 31055308
31689614: Fix for Bug 31689614
31752589: Fix for Bug 31752589
31974393: Fix for Bug 31974393
31752601: Fix for Bug 31752601
30501937: Fix for Bug 30501937
31316014: "FILE SYSTEM ERROR WITH OBJECT: /SYSTEM/MKTGJOB/JOB52330" ERROR UPON JOB EXECUT
32283083: QA[REG]-ADMIN USER NOT ABLE TO DELETE CUSTOM FONTS UPLOADED
OBI Bundle Patch 12.2.1.3.201020
29899754: REL13: CHROME: QA:COULD NOT REANME AGENTS IN CATALOG IN CHROME BROWSER
30029029: CVE-2020-14766
31312661: CVE-2020-14815
27733354: REPORT JOB HISTORY DATE FIELD DROPDOWN HAS YEAR 3000 AS DEFAULT.
27641918: NULL VALUES IN TABLE CAUSE ERROR TO PDF OUTPUT
27800712: INCOMPATIBLE SORT ORDER ISSUE WITH UNION REPORT IF SET NULL_VALUES_SORT_FIRST=ON
28047277: OBIEE12C: NON-ADMIN USER GETS "YOU DO NOT HAVE ACCESS PRIVILEGE FOR THIS SA"
31360445: CVE-2020-11022
31448181: CVE-2020-14842
30690685: CVE-2020-14780
28535009: CHART PROPERTY TREAT NULLS AS ZERO FALSE IS NOT WORKING FOR LINE CHART
31712733: TRACKING BUG TO INCLUDE BUG 30690685 FOR BIMAD
31637106: CVE-2020-14864
30865195: CVE-2020-14784
31448244: CVE-2020-14843
28996803: BISERVER_MAIN_WINDOWS LABEL BUILD FAILURE
31087358: CVE-2019-11358
31747467: CVE-2020-14879
31752545: CVE-2020-14880
31858931: 12214[REG][-BIMAD-MOBILE APP CREATION FAILING IN LATEST OCTIBER BUNDLE PATCH
30763883: Fix for Bug 30763883
30763870: CVE-2019-1547
OBI Bundle Patch 12.2.1.3.200714
31024106: CVE-2020-14609
26556686: SFTP TEST CONNECTION FAILS FOR PRIVATE KEY AUTHENTICATION
27658023: R13 UNABLE TO FORMAT FILENAME WHILE SETTING UP REPORT JOB - UCM/SFTP DESTINATION
27137133: BIP REPORT REQUEST FAILS FOR THE FIRST TIME VIA /ANALYTICS THROUGH LOAD BALANCER
27539559: ERROR - STRING INDEX OUT OF RANGE : -31 WHEN REPORT IS CREATED WITH SUBJECT AREA
27501735: 12C SYSDATE STILL BEING SHOWN AS {$SYSDATE()$} IN JOB HISTORY
27545920: GUEST REPORT ACCESS ERROR
30971776: CREATE AGENT => ANALYTICS HANG & ERROR : [LDAP: ERROR CODE 11 - ADMINISTRATIVE LIMIT EXCEEDED]" AFTER 12.2.1.4.200114 + DIAGNOSTIC PATCH FROM BUG 30903799
30865185: CVE-2020-14585
30865177: CVE-2020-14584
30690694: CVE-2020-14571
31418768: CVE-2020-14696
29631418: CVE-2020-14548
29873706: CVE-2019-14862
29820321: BEFORE REPORT TRIGGER EXECUTES AFTER BURSTING SQL
28885154: BI PUBLISHER REMOVES RANDOM SPACES FROM RTF LAYOUT AFTER UPLOAD
26492182: PRIVATE KEY AUTHENTICATION WORKING ON ONE POD AND NOT ON 3 OTHERS FOR SAME CUST.
30690687: CVE-2020-14570
31405776: FIX 26556686 - SFTP PRIVATEKEY ISSUES - 12.2.1.3.200714
30579384: OBIEE 12.2.1.4: EXPORT TO EXCEL AND PDF PROPERTIES ARE NOT WORKING AS EXPECTED
27035568: 17.4.5-1164 : REPORT WITH LAYOUT TEMPLATE GETS CORRUPTED WHEN JUST OPEN AND SAVE
25896614: PDF FILES NOT WORKING AS TEMPLATES WHEN SAVED AS ADOBE ACROBAT DC 11 PRO FILES
27693385: INSECURE STRUTS 1.3 JARS STILL BE SHIPPED BY BITHIRDPARTY
31212299: Fix for Bug 31212299
31374057: CVE-2020-14690
31358667: CVE-2020-14626
OBI Bundle Patch 12.2.1.3.200414
22119433: BISERVER_MAIN:CRASH IN NQSSERVER
26832490: AFTER APPLYING PATCH 23299204 OK BUTTON DISABLED IN PARENT-CHILD HIERARCHY
30693647: 2.5 Authorization Bypass (Vertical Escalation)
25359947: MOUSE DISAPPEARS AFTER MOVING COLUMNS AROUND ON A DASHBOARD 6-10 TIMES
27960353: Fix for Bug 27960353
27365263: NEED TO ALLOW OBIS STARTUP TO CONTINUE EVEN THERE IS A CYCLE IN ROLE HIERARCHY
30961988: CVE-2020-2950
OBI Bundle Patch 12.2.1.3.200114
28747707: CVE-2020-2531
25826028: UNABLE TO QUERY RECIPIENT NAMES BY DISPLAY NAME ATTRIBUTE
27472788: OBIEE 12C: ROLES GRANTED ON "VIEW DELIVERS FULL UX" LOST AFTER RESTART
27443959: LINE IN GRAPH LINE IS NOT DISPLAYED IN IE11 IN HTML5 MODE
27345574: SAWLOG FILLS UP WITH: A TYPE MISMATCH OCCURRED WHILE EVALUATING AN EXPRESSION
26355617: CAN'T SELECT TABLE PROMPTS DROPDOWN LIST VALUE ON IE11
23211224: BICS PROMPT BASED ON TIMESTAMP DATATYPE COLUMN ERRORS WITH INVALID PROMPT VALUE
30374407: CVE-2020-2537
29879085: CVE-2016-1000031
27097220: HUGE NUMBER OF NOTIFICATION LOG ENTRIES FOR CONNECTION POOL EVENTS
27311972: IMPLEMENT RUNTIME EVALUATION OF DYNAMIC REPOSITORY VARIABLES
OBI Bundle Patch 12.2.1.3.191015
24415058: CVE-2015-7940
29780273: CBIL:11.13.19.01.0:CRM: REMOVE MESSAGE: COPY LINK REQUIRES ADOBE FLASH PLAYER
28709953: CVE-2019-2898
29506719: CVE-2019-1559
29953527: DISABLE ADOBE FLASH IMAGE SUPPORT IN ANSWERS
28627478: CVE-2019-2905
29488979: CVE-2019-1559
29506769: CVE-2019-1559
28722735: CVE-2019-2900
28831894: CVE-2019-2897
29827791: CVE-2016-7103
29750683: CVE-2020-2535
28565865: CVE-2019-3012
30380250: QA: CI BUG 30054026 IS NOT FIXED IN 9.191015
26382244: DISABLE FLASH TEMPLATE IN OAC
26551071: QA:UPLOAD TEMPLATE TEXT NEED TO BE MODIFIED AS FLASH TEMPLATE IS DISABLED
27440571: FLASH CONFIGURATION SHOULD BE REMOVED FROM OAC RUNTIME PROPERTIES
OBI Bundle Patch 12.2.1.3.190716
28900868: CVE-2019-2771
28886045: CVE-2019-2768
28885772: CVE-2019-2767
27839392: Fix for Bug 27839392
27580645: JNDI DATASOURCE ISSUE WITH PRE-PROCESS FUNCTION
29509993: CVE-2019-2906
27788081: CVE-2019-2742
OBI Bundle Patch 12.2.1.3.190416
25248099: NEED TO CHECK THE RETURN CODE OF BUILDROLEHIERARCHY
28797734: CVE-2019-2605
28885971: CVE-2019-2616
28722734: CVE-2019-2595
28627487: CVE-2019-2588
28747876: CVE-2019-2601
28077156: CVE-2015-9251
OBI Bundle Patch 12.2.1.3.181016
27747746: Fix for Bug 27747746
26560302: Fix for Bug 26560302
27826864: Fix for Bug 27826864
27826858: Fix for Bug 27826858
27826869: Fix for Bug 27826869
27747600: Fix for Bug 27747600
28143150: CVE-2018-8013
26957199: CVE-2017-5645
28095823: CVE-2018-3204
OBI Bundle Patch 12.2.1.3.180717
27019889: DYNAMIC REPOSITORY VARIABLES NOT WORKING IN 12.2.1.3.0
24623887: CVE-2017-10060
21216069: GRAPH CANNOT BE DISPLAYED IF DISPLAY VARIABLE IS SET
27155012: OBIS SESSION SWITCH DOES NOT CARRY OVER DEFAULT SUBJECT AREA
25071445: CRITICAL JOBS SHOULD NOT BE SHOWN WITH RED BACKGROUND ON JOB HISTORY PAGE
25484519: MAINTENANCE FLAG NEEDS TO BE CHECKED WHEN BIEE CONNETION FAILS
21309457: SSBEN ACCESSIBILITY: BIP REGION HAVING FORM AND STRUCTURE INSPECTOR ISSUE
26798068: HCMANALYTICS DEPLOYMENT ON 12CIWS FAILED WITH UNRESOLVED APPLICATION LIBRARY REF
27529288: 12C SMC PILLAR ESS APPS DEPLOYMENT UNKNOWNHOSTEXCEPTION: SLC01HJK.US.ORACLE.COM
26909225: CVE-2018-2925
27679984: CVE-2018-2958
OBI Bundle Patch 12.2.1.3.180116
24691274: CONFIG.XML FOR BI-ADF BROKER JDEV EXTENSION HAS AN ILLEGAL SPECIFICATION-VERSION
26266824: OBIEE 12.2.1.2.0 AN HTTP OPERATION TO XXXX.EMEA.XXX.LOC:80 TIMED OUT AFTER 1SEC
26486161: PS: PDFDOCMERGERV2/PDFMERGER ERRORS AND FAILS TO MERGE SOME PDF-CREATED BY LATEX
26171147: CALENDAR IS NOT UPDATED IN SEEDED REPORTS
26760055: PSR:PERF:BICS CLUSTER CONTROLLER SHOULD WAIT/ LOG/ RETRY BEFORE TAKING OBIS OFFL
26578260: SESSIONS IN OBIEE12C DO NOT FAIL-OVER GRACEFULLY WHEN ONE NODE IS KILLED
26975548: ADMINTOOL COMPARE NOT PULLING IN ALL DIFFERENCES IN RPDS
21766173: CVE-2016-3473
21766306: CVE-2016-0470
26535378: EL 12 UPGRADE A? LINKED ANALYSES NOT WORKING FROM HUMAN RESOURCES DASHBOARD
26944921: EEAR-TEST:CANCEL QUERY DOES NOT WORK
26017396: OBIEE 12C: CUSTOM SKIN / STYLE SET IN RPD VARIABLES IS NOT APPLIED TO DASHBOARDS
26541044: CVE-2018-2715
26775946: INCREASE THE DEFAULT VALUE OF OBIS_MAX_PERIODICTASKS_EXECUTOR_THREADS
25061256: CVE-2017-10068
26553225: CVE-2017-5662
26787841: Fix for Bug 26787841
26923935: 12C DEPLOYMENT - BIADMINESSBASERULEGENERATOR LIBRARY MISSING
26787682: Fix for Bug 26787682
26612444: HIDDEN DASHBOARD PAGE IS ADVERSELY AFFECTING DASHBOARD NAVIGATION.
27214490: SEVERE: EMBEDDED EXPORT SPECIFICATION JAR:BIADMINESSBASERULEGENERATOR.JAR
26632162: Fix for Bug 26632162
Bundle Patches are always cumulative. You can install the last one.
Generally you should try to stay up-to-date. it's not just application bugs which are fixed but also security bugs. The closer you stay to the current patch level the more secure you are.
My Luis bot app was working fine when I tested in the 2nd week of March 2017. Testing includes -
1) using Luis end point start with "https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/........." in browser and Luis.ai
2) using visual studio code where I provided the LuisDialog with LuisModel attribute having app id and subscription key.
When I today tried to test it again, it is working fine in browser and Luis.ai using luis end point but in NOT in visual studio.Please refer the screenshot. Every time it is giving "An item with the same key has already been added".
I checked the LUIS : An item with the same key has already been added but did not get answer.
I tried to integrate this luis bot app with Azure Bot service. Same error is there also -
"2017-03-12T12:27:17.657 Exception while executing function: Functions.messages. mscorlib: An item with the same key has already been added."
Please help.
Thanks,
Sarnendu
I was keep trying to solve my issue for couple of days to run bot service in azure. Finally I am able to run.
Mainly 2 issues were there -
One is wrong Luis API Host Name in Azure Portal
Another is wrong attribute in Intent.
Correcting the Luis API Host Name-
In Azure portal, I have updated the Luis API End Point to westus.api.cognitive.microsoft.com from api.projectoxford.ai.
Steps to follow - go to 'All Resources' and click on the bot. Now go to Setting Tab and click of Application Setting button. Please refer below screenshot.
Now update the LuisAPI end point key in yellow highlighted area as shown below-
Updating Luis API Host Name
After updating this setting, my bot was not working and throwing same error.
Correcting the Wrong Attribute in Intent :
Later I checked LuisDialog.csx,
[LuisIntent("")] atrtibute was present in one of the Intents other than None Intent. Here [LuisIntent("")] was given in BookHoliday Intent.
Please refer below screenshot -
Wrong attribute in Intent
Both [LuisIntent("")] and [LuisIntent("None")] can be used for None Intent.
I removed [LuisIntent("")] from BookHoliday Intent, it works fine.
It was copy-paste error, I copied None intent and modified None to BookHoliday but did not removed the [LuisIntent("")].
"An item with the same key has already been added"- this issue may also be raised if &q appears more than 1 time in query string as part of Luis App Endpoint url.
Regarding code run issue in visual studio, it looks like VS was not updated. It works after updating.
After discovering that the Google team upgraded the Android Developer API, I made a script to automatically update all my apps data in multiple languages at once.
However, I've noticed that, when you follow a workflow of:
Ask for Edit ID,
Do all your changes
Commit all your changes
At some point, you get a SocketTimeoutException when you try to update changes. Well, this may be due to a problem in my connection.
So, to solve that, I changed my workflow:
Ask for Edit ID,
Do one change
Commit one change
Repeat from 1 until changes finished
However, following this process, it ends with this when I try to commit after some changes:
{
"code" : 403,
"errors" : [ {
"domain" : "androidpublisher",
"message" : "Daily save quota exceeded.",
"reason" : "publishingDailySaveQuotaExceeded"
} ],
"message" : "Daily save quota exceeded."
}
Looks weird to me, as there is no explanation about save quotas for this API.
Also, after an intense use, the current quota limit keeps frozen at 0/200k, as if I didn't do anything. I didn't use the v1 of this API, so I don't know anything about this.
Do you know if that's the correct behavior?
Unfortunately it looks like their "recommendation" in their API's usage page is the rule.
Do not publish alpha or beta updates more frequently than once a day. (Production apps should be updated even less frequently than that.) Every update costs your users time and possibly money. If you update too frequently, users will start ignoring updates, or even uninstall the product.
Seems odd to me that they hard limit it like this though. It should be explicit at the very least.
Update
To follow up, I'm actually able to publish more than once a day as long as attempted uploads aren't rejected for some reason (such as 401 unauthorized). Haven't tested to see what the upper limit is, but it does make testing this a nuisance if it does heavily rate limit after one bad attempt.
The Google Play Developer API has a default limit of 200,000 queries per day.
For the purpose of enforcing this quota, the day ends at midnight Pacific time (UTC-8 when California is on standard time, UTC-7 when California is on daylight time).
https://developers.google.com/android-publisher/quotas