I managed to use both Answer and Crashlytic together. i did it before just with CrashLytic.
But for my new app i can't initialize that again.
I see logs which shows everything is alright.
but my app is not in dashboard.
I used this code as one of the Twitter Staff mentioned here:
Fabric fabric = new Fabric.Builder(this).debuggable(true).kits(new Crashlytics()).build();
Fabric.with(fabric);
In my log i see these lines :
D/Fabric: Requesting settings from ....
D/Fabric: Loaded settings: .....
D/CrashlyticsCore: Initialization marker file created.
D/CrashlyticsCore: Finalizing previously open sessions.
D/CrashlyticsCore: Closing open sessions.
D/CrashlyticsCore: Closed all previously open sessions
D/CrashlyticsCore: Initialization marker file removed: true
D/CrashlyticsCore: Starting report processing in 1.0 second(s)...
D/CrashlyticsCore: Checking for crash reports...
D/CrashlyticsCore: No reports found.
But still my app won't be shown in dashboard. Any idea how to resolve it ?
The problem was from Fabric side. Their support team solve the problem at their side. The initialization Code above is correct.
Related
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.
I am using a local install of Playground on MacOS.
I was successful to create my business network, add my model file and logic to this network and create assets and participants instances.
So now I am ready to submit my first transaction, but I get an error message in the popup window as a result to my request. The message per se is not the problem (it's about some Undefined asset), my problem is I want to debug this transaction code by producing some execution traces, using old-school printf or log message.
I tried to insert console.log(message) instructions in my transaction code but eventually I was not able to retrieve those logs traces (eg. using a command like docker logs -f composer).
Is there another way to produce logs traces? Or did I miss a config setting to defilter logs in docker logs?
Any help greatly appreciated!
Olivier.
On console logging (and seeing them in the browser Developer console), see this Stack Overflow here (hyperledger composer playground) Can you see results of console.log('something') in browser? (it also has a link to more info there
See here https://hyperledger.github.io/composer/latest/problems/diagnostics.html for more on logging / where to find debug logs.
As for setting checkpoint/breakpoints: These are set by the Editor tooling 🙂 In H/Composer, you can just use the embedded connector (eg such as TP functions) to try out / step through each breakpoint - for more info on VSCode -> https://code.visualstudio.com/docs/editor/debugging and Atom -> How do I set a breakpoint inside of atom's package? and I posted the link to diagnostics/logging above.
One quick way I used to insert breakpoints with debug messages, is to throw an exception using throw new Error(...) in the transaction method.
This shows up in the playground interface as well.
I have a datasnap server configured for HTTPS, this starts and runs fine as far as I can tell.
From the client's point of view when I 'Generate datasnap client classes' via the TSQLConnection component I get an error message - Error getting server certificate.
Can anybody offer any useful info regarding this and how to fix it?
Thanks,
Appears to be a bug with the TDSCertfiles component in the Server project.
Having set the following properties programmatically, the bug seems to ignore what I have put in code and looks for what is set manually in the object inspector (empty) :
Cerfile
Keyfile
RootCertfile
FIX - After setting the above properties and before calling DSHTTPService.Start add the following :
DSCertFiles.SetServerProperties(DSHTTPService.HttpServer).
Retesting the connection/Generating server methods from my client app, I no longer get the error message and it successfully connects.
I'm trying to use sw-precache, but I must be doing something wrong!
I'm mostly using the demo code available from the github repo and can't seem to get updates to the app to come through. Once it's cached the first time, it never checks for new versions.
I was expecting that when I publish a new service worker, the browser would request the new service worker and update the cache accordingly in the background. Then using the registration code in the example, I would be able to prompt the user to refresh and get the latest version from their newly refreshed cache.
Would really appreciate if someone could please point me in the right direction.
Example
To demonstrate the problem, I've created an isolated example here:
https://github.com/stevenocchipinti/sw-precache-demo
The example uses a basic skeleton from create-react-app which has a built in build task which take care of fingerprinting the filenames, etc.
I suspect the problem is with me caching everything by using the following sw-precache config:
{
"staticFileGlobs": [ "build/**/*.*" ],
"stripPrefix": "build/"
}
There are more accurate steps in the repo's readme, but the basic steps I'm taking to reproduce the problem are as follows (with my probably incorrect expectations).
Steps and Assumptions
Browse to the app for the first
I should see Content is now available offline! in the console
Reload the page
The message in the console should not appear again because the service worker is installed, but the page should still work.
Go offline and reload the page
The page should still work
Make a visible change to the source code
Rebuild (run the build task and sw-precache)
This is where my understanding must be wrong
Reload the page
The service worker should update the cache in the background
When its done, you should see New or updated content is available. in the console
The actual visible changes should not be visible until the next reload
Reload the page again
The browser will use the new cache this time around
The changes should be visible now!
There shouldn't be any messages in the console
The problem
Once the app has been cached initially, it will never update unless you unregister the service worker or force a reload.
I'm not sure how to make this work - any help would be greatly appreciated!
After replicating your development hosting environment, I can see that you're serving your service-worker.js file with a browser HTTP cache lifetime of one hour:
There's more information as to why this is leading to the behavior you're seeing, along with best practices, in this previous answer. As mentioned at the top of that answer, browsers plan on changing their behavior to stop honoring the HTTP cache for the service worker file by default, mainly due to the type of confusion that you're experiencing here. For the time being, though, the production versions of both Chrome and Firefox continue to honor those headers.
I have a console application which hosts two WebApi applications using OWIN Self Host approach. One of the apps uses EF6 with Code First. When I run the executable from the bin folder and make a request to the WebApi, everything works like it should - if the database is already created it just returns the results, otherwise it creates the db first. But if I start the console app from Visual Studio (with debugging), I receive the following error:
Additional information: Cannot open database "{db name}" requested by the login. The login failed.
Login failed for user 'sa'.
Anyone has any ideas why this happens?
EDIT: Problem is not related to the self hosted apps. I referenced the dbcontext directly in the console app and the same issue happens. I also tried Integrated Security and it still fails with "Login failed for user '{DOMAIN\USERNAME}'."
EDIT 2: I fixed my problem by doing deleting the .suo file. That helped me find these two questions mentioning the same solution:
Login failed for user "xxx" Failed to open the explicitly specified database solution
EF 4.1 code first causes weird (login) runtime errors
Can anyone say the reason why the .suo file causes this?