Python3 installation failed, Error code 0x80070003 - python-3.x

Python3 installation failed, error code 0x80070003.
My system is windows 10 64 bit, The installed version is 3.6.2
Installation error screenshot
The error log:
[2C1C:40E8][2018-01-15T12:32:04]e314: Failed to cache payload: core_AllUsers from working path: C:\Users\WESTIN~1\AppData\Local\Temp\{E8A75A81-A084-498C-865F-D7D322105665}\core_AllUsers, error: 0x80070003.
[2C1C:3D2C][2018-01-15T12:32:04]e000: Error 0x80070003: Cache thread exited unexpectedly.
[2C1C:3D2C][2018-01-15T12:32:04]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{f71cfe9a-4a67-48a6-844b-571a76b33d33}, resume: ARP, restart: None, disable resume: No
[2C1C:3D2C][2018-01-15T12:32:04]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{f71cfe9a-4a67-48a6-844b-571a76b33d33}, resume: ARP, restart initiated: No, disable resume: No
[2C1C:3D2C][2018-01-15T12:32:04]i399: Apply complete, result: 0x80070003, restart: None, ba requested restart: No*

when you perform the installation and choose the "Download debugging symbols" or "Download debug binaries", make sure your internet connection is up and available otherwise un-check those.

Related

Unable to apply changes on device: emulator-5554. Error is: Command gradlew.bat failed with exit code 1

I begin new project with NativeScript, but after more and more try i couldn't fix my error.
After build my application with:
tns run android --device Pixel_4_API_30
i have this error :
Unable to apply changes on device: emulator-5554. Error is: Command gradlew.bat failed with exit code 1.**
...............................................................................................
My trace loge :
#############################################################################
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
Debug level logging will leak security sensitive information!
https://docs.gradle.org/6.4/userguide/logging.html#sec:debug_security
#############################################################################
Command gradlew.bat failed with exit code 1
Will send the following information to Google Analytics: {
type: 'googleAnalyticsData',
category: 'CLI',
googleAnalyticsDataType: 'event',
action: 'Performance',
label: 'AndroidProjectService__buildProject',
customDimensions: { cd2: 'Angular', cd9: 'false', cd5: 'CLI' },
value: 3529
}
Error: Command gradlew.bat failed with exit code 1
at Errors.failWithOptions (C:\Users\BRYAN\AppData\Roaming\nvm\v12.13.0\node_modules\nativescript\lib\common\errors.js:157:27)
at Errors.fail (C:\Users\BRYAN\AppData\Roaming\nvm\v12.13.0\node_modules\nativescript\lib\common\errors.js:130:21)
at GradleCommandService.<anonymous> (C:\Users\BRYAN\AppData\Roaming\nvm\v12.13.0\node_modules\nativescript\lib\services\android\gradle-command-service.js:40:30)
at Generator.throw (<anonymous>)
at rejected (C:\Users\BRYAN\AppData\Roaming\nvm\v12.13.0\node_modules\nativescript\lib\services\android\gradle-command-service.js:6:65)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
tns info :
√ Getting NativeScript components versions information...
√ Component nativescript has 7.2.0 version and is up to date.
‼ Update available for component #nativescript/core. Your current version is 7.1.4 and the latest available version is 7.3.0.
√ Component #nativescript/ios has 7.2.0 version and is up to date.
√ Component #nativescript/android has 7.0.1 version and is up to date.
Gradle is connected to Java so check your installed version is 8. If not then get the correct version and try again. ns doctor is your friend!
If that doesn't work, stop any java and emulator (android/qemu) related tasks/processes and try again.
If that fails try rebooting your computer and test again.

Anchore Engine - Jenkins CI plugin

We are trying to scan our docker images using Anchore Engine Jenkins plugin.
Currently we create our application docker images, push it in our own private local registry and then deploy it in our test environments.
Now, we want to setup docker image scanning in our CI/CD process to check for any vulnerabilities.
We have installed Anchore Engine using the recommended Docker-Compose yaml method given in the Documentation link:
https://anchore.freshdesk.com/support/solutions/articles/36000020729-install-on-docker-swarm
Post installation, we installed the
Anchore Container Image Scanner Plugin in Jenkins.
We configured the plugin as mentioned in the document link:
https://wiki.jenkins.io/display/JENKINS/Anchore+Container+Image+Scanner+Plugin
However, the scanning fails. Error Message as follows:
2018-10-11T07:01:44.647 INFO AnchoreWorker Analysis request accepted, received image digest sha256:7d6fb7e5e7a74a4309cc436f6d11c29a96cbf27a4a8cb45a50cb0a326dc32fe8
2018-10-11T07:01:44.647 INFO AnchoreWorker Waiting for analysis of 10.180.25.2:5000/hello-world:latest, polling status periodically
2018-10-11T07:01:44.647 DEBUG AnchoreWorker anchore-engine get policy evaluation URL: http://10.180.25.2:8228/v1/images/sha256:7d6fb7e5e7a74a4309cc436f6d11c29a96cbf27a4a8cb45a50cb0a326dc32fe8/check?tag=10.180.25.2:5000/hello-world:latest&detail=true
2018-10-11T07:01:44.648 DEBUG AnchoreWorker Attempting anchore-engine get policy evaluation (1/300)
2018-10-11T07:01:44.675 DEBUG AnchoreWorker anchore-engine get policy evaluation failed. URL: http://10.180.25.2:8228/v1/images/sha256:7d6fb7e5e7a74a4309cc436f6d11c29a96cbf27a4a8cb45a50cb0a326dc32fe8/check?tag=10.180.25.2:5000/hello-world:latest&detail=true, status: HTTP/1.1 404 NOT FOUND, error: {
"detail": {},
"httpcode": 404,
"message": "image is not analyzed - analysis_status: not_analyzed"
}
NOTE:
In Image TAG 10.180.25.2:5000/hello-world:latest, 10.180.25.2:5000 is our local private registry and hello-world:latest is latest hello-world image available in docker hub which we pulled and pushed in our registry to try out image scanning using Anchore-Engine.
Unfortunately we are not able to find much resource online to try and resolve the above mentioned issue.
Anyone who might have worked on Anchore-Engine, please may I request to have a look and help us resolve this issue.
Also, any suggestions or alternatives to anchore-engine or detailed steps in case we might have missed anything would be really appreciated.
End of the output is as follows:
2018-10-15T00:48:43.880 WARN AnchoreWorker anchore-engine get policy evaluation failed. HTTP method: GET, URL: http://10.180.25.2:8228/v1/images/sha256:7d6fb7e5e7a74a4309cc436f6d11c29a96cbf27a4a8cb45a50cb0a326dc32fe8/check?tag=10.180.25.2:5000/hello-world:latest&detail=true, status: 404, error: {
"detail": {},
"httpcode": 404,
"message": "image is not analyzed - analysis_status: not_analyzed"
}
2018-10-15T00:48:43.880 WARN AnchoreWorker Exhausted all attempts polling anchore-engine. Analysis is incomplete for sha256:7d6fb7e5e7a74a4309cc436f6d11c29a96cbf27a4a8cb45a50cb0a326dc32fe8
2018-10-15T00:48:43.880 ERROR AnchorePlugin Failing Anchore Container Image Scanner Plugin step due to errors in plugin execution
hudson.AbortException: Timed out waiting for anchore-engine analysis to complete (increasing engineRetries might help). Check above logs for errors from anchore-engine
at com.anchore.jenkins.plugins.anchore.BuildWorker.runGatesEngine(BuildWorker.java:480)
at com.anchore.jenkins.plugins.anchore.BuildWorker.runGates(BuildWorker.java:343)
at com.anchore.jenkins.plugins.anchore.AnchoreBuilder.perform(AnchoreBuilder.java:338)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1724)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:421)
I also checked status and found below:
docker run anchore/engine-cli:latest anchore-cli --u admin --p admin123 --url http://172.18.0.1:8228/v1 system status
Service analyzer (dockerhostid-anchore-engine, http://anchore-engine:8084): up
Service catalog (dockerhostid-anchore-engine, http://anchore-engine:8082): up
Service policy_engine (dockerhostid-anchore-engine, http://anchore-engine:8087): down (unavailable)
Service simplequeue (dockerhostid-anchore-engine, http://anchore-engine:8083): up
Service apiext (dockerhostid-anchore-engine, http://anchore-engine:8228): up
Service kubernetes_webhook (dockerhostid-anchore-engine, http://anchore-engine:8338): up
Engine DB Version: 0.0.7
Engine Code Version: 0.2.4
It seems service policy engine is down
Service policy_engine (dockerhostid-anchore-engine, http://anchore-engine:8087): down (unavailable)
I also checked the docker logs . I found below error:
[service:policy_engine] 2018-10-15 09:37:46+0000 [-] [bootstrap] [DEBUG] service (policy_engine) starting in: 4
[service:policy_engine] 2018-10-15 09:37:46+0000 [-] [bootstrap] [INFO] Registration complete.
[service:policy_engine] 2018-10-15 09:37:46+0000 [-] [bootstrap] [INFO] Checking feeds client credentials
[service:policy_engine] 2018-10-15 09:37:46+0000 [-] [bootstrap] [DEBUG] Initializing a feeds client
[service:policy_engine] 2018-10-15 09:37:47+0000 [-] [bootstrap] [DEBUG] init values: [None, None, None, (), None, None]
[service:policy_engine] 2018-10-15 09:37:47+0000 [-] [bootstrap] [DEBUG] using values: ['https://ancho.re/v1/service/feeds', 'https://ancho.re/oauth/token', 'https://ancho.re/v1/account/users', 'anon#ancho.re', 3, 60]
[service:policy_engine] 2018-10-15 09:37:47+0000 [-] [urllib3.connectionpool] [DEBUG] Starting new HTTPS connection (1): ancho.re
[service:policy_engine] 2018-10-15 09:37:50+0000 [-] [bootstrap] [ERROR] Preflight checks failed with error: HTTPSConnectionPool(host='ancho.re', port=443): Max retries exceeded with url: /v1/account/users/anon#ancho.re (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7ffa905f0b90>: Failed to establish a new connection: [Errno 113] No route to host',)). Aborting service startup
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/anchore_manager/cli/service.py", line 158, in startup_service
raise Exception("process exited: " + str(rc))
Exception: process exited: 1
[anchore-policy-engine] [anchore_manager.cli.service/startup_service()] [INFO] service process exited at (Mon Oct 15 09:37:50 2018): process exited: 1
[anchore-policy-engine] [anchore_manager.cli.service/startup_service()] [INFO] exiting service thread
Thanks and Regards,
Rohan Shetty
When images are added to anchore-engine, they are queued for analysis which moves them through a simple state machine that starts with ‘not_analyzed’, goes to ‘analyzing’ and finally ends in either ‘analyzed’ or ‘analysis_failed’. Only when an image has reached ‘analyzed’ will a policy evaluation be possible.
The anchore Jenkins plugin will add an image, then poll the engine for image status/evaluation for the configured number of tries (default 300). Once the image goes to ‘analyzed’ (where policy evaluation is possible), the plugin will then receive a policy evaluation result from the engine.
The plugin will fail the build (by default) if the max retries has been performed and the image has not reached ‘analyzed’, if the image does reach ‘analyzed’ but the policy evaluation is producing a ‘fail’ result (meaning the image didn’t pass your configured policy checks). Note that all build failure behavior can be controlled in the plugin (I.e. there are options to allow the plugin to succeed even if the analysis or image eval fails).
You’ll need to look at the end of the output from your build run (instead of just the beginning from your post), and combined with the information above, it should be clear which scenario is causing the plugin to fail the build.
We have resolved the issue.
Root Cause:
We were not able to establish a successful https connection to URL : https://ancho.re from within the anchore-engine docker container.
As a result the service:policy_engine was not able to start.
https://ancho.re is required to download policy feeds and sync-up periodically. Without these policy anchore-engine won't be able to analyse the docker images.
Solution:
1) We passed a HTTPS_PROXY URL as an environment variable in the docker-compose.yaml of anchore-engine.
We used this proxy URL to bypass restrictions in our environment and establish a connection with https://ancho.re url.
2) Restarted the docker containers.
Finally we got all services up and running including Anchore policy-engine.
FYI:
It takes a while to download all the required Feeds depending on your internet speed.
Lastly, Thanks to the Anchore community for quick responses and support over slack.
Hope this helps.
Warm Regards,
Rohan Shetty

Xcode 9 Beta 2 fails - DVTPlugInErrorDomain plugin load fails

After downloading from Apple's site and installing Xcode 9 beta 2, it fails to launch on Sierra OS X version 10.12.5 with a following bug report:
Process: Xcode [4789] Path:
/Applications/Xcode-beta.app/Contents/MacOS/Xcode Identifier:
com.apple.dt.Xcode Version: 9.0 (13158.29) Build Info:
IDEFrameworks-13158029000000000~6 Code Type: X86-64
(Native) Parent Process: ??? [1] Responsible: Xcode
[4789] User ID: 501
Date/Time: 2017-07-10 09:27:38.822 +0300 OS Version:
Mac OS X 10.12.5 (16F73) Report Version: 12 Anonymous UUID:
D8406E47-CD80-D96B-2976-599E84980DE2
Sleep/Wake UUID: A8F0AF0B-2FF1-45A9-89AD-505F25730705
Time Awake Since Boot: 20000 seconds Time Since Wake: 3800
seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT) Exception Codes:
0x0000000000000000, 0x0000000000000000 Exception Note:
EXC_CORPSE_NOTIFY
Application Specific Information: ProductBuildVersion: 9M137d UNCAUGHT
EXCEPTION (NSInternalInconsistencyException): Error getting value for
parameter key 'name' of extension
'Xcode.InterfaceBuilderKit.PepperIntegration.Singletons' in plug-in
'com.apple.dt.IDE.IDEInterfaceBuilderWatchKitIntegration' UserInfo: {
NSUnderlyingError = "Error Domain=DVTPlugInErrorDomain Code=2 \"Loading a plug-in failed.\"
UserInfo={DVTPlugInIdentifierErrorKey=com.apple.dt.IDE.IDEInterfaceBuilderCocoaTouchIntegration,
DVTPlugInExecutablePathErrorKey=/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
NSLocalizedRecoverySuggestion=The plug-in or one of its prerequisite
plug-ins may be missing or damaged and may need to be reinstalled.,
DVTPlugInDYLDErrorMessageErrorKey=dlopen(/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
0): Library not loaded:
/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator\n
Referenced from:
/Applications/Xcode-beta.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit\n
Reason: image not found, NSLocalizedDescription=Loading a plug-in
failed.,
NSFilePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework,
NSLocalizedFailureReason=The plug-in
\U201ccom.apple.dt.IDE.IDEInterfaceBuilderCocoaTouchIntegration\U201d
at path
\U201c/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework\U201d
could not be loaded. The plug-in or one of its prerequisite plug-ins
may be missing or damaged., NSUnderlyingError=0x7fc8df3cb340 {Error
Domain=NSCocoaErrorDomain Code=3587
\"dlopen_preflight(/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration):
Library not loaded:
/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator\n
Referenced from:
/Applications/Xcode-beta.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit\n
Reason: image not found\" UserInfo={NSLocalizedFailureReason=The
bundle is damaged or missing necessary resources.,
NSLocalizedRecoverySuggestion=Try reinstalling the bundle.,
NSFilePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration,
NSDebugDescription=dlopen_preflight(/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework/IDEInterfaceBuilderCocoaTouchIntegration):
Library not loaded:
/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator\n
Referenced from:
/Applications/Xcode-beta.app/Contents/Developer/Library/PrivateFrameworks/SimulatorKit.framework/Versions/A/SimulatorKit\n
Reason: image not found,
NSBundlePath=/Applications/Xcode-beta.app/Contents/PlugIns/IDEInterfaceBuilderCocoaTouchIntegration.framework,
NSLocalizedDescription=The bundle
\U201cIDEInterfaceBuilderCocoaTouchIntegration\U201d couldn\U2019t be
loaded because it is damaged or missing necessary resources.}}}"; }
I had the same issue. I have reinstalled XcodeSystemResources.pkg package. You will find it in here:
/Applications/Xcode.app/Contents/Resources/Packages/XcodeSys‌​temResources.pkg
The installer will recreate /Library/Developer/PrivateFrameworks folder with its content. After that Xcode 9 started working for me.

PhantomJS has crashed - Fatal Windows exception, code 0xc0000005

We have built a application using EmberJS. We got a failure message when we test the application using ember test. Here I mentioned the error message
OS: Windows 8(64-bit)
PhantomJS: 2.1.1
PhantomJS - error
---
message: >
Error:
Non-zero exit code: 3221225477
Stderr:
Fatal Windows exception, code 0xc0000005.
PhantomJS has crashed. Please read the bug reporting guide at
<http://phantomjs.org/bug-reporting.html> and file a bug report.
Log: |
{ type: 'error', text: 'Error: Browser exited unexpectedly' }
{ type: 'error', text: 'Non-zero exit code: 3221225477' }
{ type: 'error',
text: 'Fatal Windows exception, code 0xc0000005.\r\nPhantomJS has crashed. Please read the bug reporting guide at\r\n<http://phantomjs.org/bug-reporting.html> and file a bug report.\r\n'
}
I was having a very similar problem running PhantomJS on Windows 10 in the WSL.
I have found that:
The crash might be originating in the QT WebSocket handling code.
Setting the Karma transports setting to polling solved my issue and PhantomJS does no longer crash on startup.
In your Karma.conf.js add :
transports: ['polling']
Reference Link
PhantomJS Crashing

Running Grails 2.3.1 in debug mode from linux

I'm trying to run Grails 2.3.1 en debug mode either from console or IntelliJ IDEA 12, but I always get the following error:
grails run-app --debug-fork
| Running Grails application
ERROR: transport error 202: bind failed: Address already in use
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
First of all I configure my IDEA Debug mode.
For grails <2.4
I'm doing next:
1. grails-debug run-app
It's opening port 5005 and waiting for your IDE to connect
2. Go to IDEA and hit "bug" button
3. Your grails console automatically runs application
For grails 2.4
1. "grails --debug run-app"
2. Hit "bug" button
I solved it as follows
i switched and reswitched the grails version with gvm default ...
i checked a fresh copy

Resources