I've recently been developing an app, and noticed a few days ago I updated R to 4.1.2. After making some changes to the app, I used the Publish button to deploy to shinyapps.io. The deployment console threw the following error and failed:
Error: Unhandled Exception: Child Task 1045191965 failed: Error building image: R version 4.1.2 currently unavailable
Execution halted
Now, I've deployed many times previously, and this was the first deployment since the update to R. I haven't included any code because my app.R is over 1500 lines and it really didn't seem to be related to any of thee changes I made. I was wondering if anyone could help me figure out whether this error is referring to my system or the server I am deploying to. I expect I may have to roll back to the pre-update snapshot and try again, but I'd like to avoid doing that if the problem lies somewhere else.
Rstudio is Version 1.4.1103
Operating system:
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
Thanks in advance!
After checking with shinapps.io support, they informed me their server has not been updated to 4.1.2 and to downgrade until they are able to make the upgrade. They were not able to provide an ETA on that. Thanks to the support staff there!
Related
Trying to compile Corda from scratch. I cloned version 4.3 from Github. Details and error codes below.I am using Oracle java version 1.8. I have asked this question on slack as well but didn't find anyone who has faced this issue before.
Task :node-api-tests:test
net.corda.nodeapitests.internal.crypto.X509UtilitiesTest > create valid server certificate chain FAILED
java.security.cert.CertificateException at X509UtilitiesTest.kt:166
net.corda.nodeapitests.internal.crypto.X509UtilitiesTest > create valid self-signed CA certificate FAILED
java.security.cert.CertificateException at X509UtilitiesTest.kt:131
46 tests completed, 2 failed
Task :node-api-tests:test FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ‘:node-api-tests:test’.
So it looks like you're trying to build Corda's source code. Most of the time you really won't need to do this. I'd recommend instead just taking a look at the Corda samples as they use gradle which will download the jars and compile the samples for you.
Here's a link to some of those sample repo's so you can try building off of them.
https://github.com/corda/samples-kotlin
https://github.com/corda/samples-java
All of them compile and run the same way so it shouldn't be too difficult to get running.
./gradlew deployNodes
and then
./build/nodes/runnodes
I have connected my Android application with firebase-database by putting this dependency (kapt 'com.google.firebase:firebase-database:16.0.1:15.0.0') but after that I am getting errors like the one mentioned in title also when I synchronized the project I am getting different errors like: Connection time out, Failed to resolved build listener.
Enabling/Disabling offline work and setting proxy in gradle.properties file doesn't work for me.
Also you guys have seen that I used 'kapt' in dependency as it is necessary to use, without it I am getting error "failed to resolve 15.0.0". Removing 15.0.0 doesn't work for me.
Error
Cause:org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl.getModuleIdentifier()Lorg/gradle/api/artifacts/ModuleIdentifier;ing
I am using Android Studio 3.2 and sadly I can't update this version.
Gradle version: 5.1.1 and
Plugin version: 3.4.0
I am trying to run Corda nodes on macOS El Capitan with JDK 1.8.0_60 by following the instructions here: https://docs.corda.net/getting-set-up.html.
I am getting the following error:
CAPSULE EXCEPTION: Could not parse version: -9.0.1 while processing
system property java.home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre
java.lang.IllegalArgumentException: Could not parse version: -9.0.1
How can I fix this?
Although its older thread, i encountered it today and stumbled upon this page and thought to share my findings.
Actually Oracle changed the numbering style from java9 (like 9.0.1) and it seems you have it installed. You will have to point to jdk 1.8.x so make it work until capsule is updated to work with java9.
Running Corda nodes requires a JDK version greater than JDK 8u121. If you upgrade your JDK, this error will disappear.
I have a shiny app that depends on a GitHub package. I recently updated the GitHub package, so I want to republish the shiny app as well. I have made no changes to the shiny app code at all, and it runs without error in RStudio. But, when I go to republish it, I get these messages in the Deploy tab of RStudio.
Preparing to deploy document...DONE
Uploading bundle for document: 96244...DONE
Deploying bundle: 426681 for document: 96244 ...
Waiting for task: 180459152
building: Parsing manifest
building: Building image: 419646
building: Building package: xtable
################################ Begin Task Log ################################
################################# End Task Log #################################
Error: Unhandled Exception: Child Task 180459153 error: Unhandled Exception: HTTP 599: Connection closed
Execution halted
I am running the latest versions of R (3.2.5) and RStudio (0.99.893) on Windows 7, and I made sure all the packages have been updated.
I searched around for folks reporting similar errors (and solutions) and found didn't find anything helpful.
I'd appreciate any tips.
Links:
Shiny app - if it says "Last modified: 7 January 2016", it's still the old version that I'm trying to replace.
Code for shiny app
GitHub package
Did you update to R 3.2.5? It seems shinyapps.io is not ready for this.
I had these errors yesterday. Roll back to 3.2.4 and it will work.
Note this is confirmed in shinyapps forum:
"Is it at all possible that you are running with R version 3.2.5? If
so, downgrading to 3.2.4 should fix this issue. The error message
should be saying something like: shinyapps.io doesn't support this
version of R yet."
Fresh install of Meteor 0.5.0 on Windows Vista. I don't get the basic examples working. No success after creating the empty'ish hello app either. The shell is running as admin. Meteor recognises that I changed a source file, but then nothing. It doesn't matter where in the filesystem i try this. Always getting
Exited with code: -1073741819:
eg
C:\Users\jawford\Meteor Apps\Examples>meteor create starter3
starter3: created.
To run your new app:
cd starter3
meteor
C:\Users\jawford\Meteor Apps\Examples>cd starter3
C:\Users\jawford\Meteor Apps\Examples\starter3>meteor
[[[[[ C:\Users\jawford\Meteor Apps\Examples\starter3 ]]]]]
Running on: http://localhost:3000/
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
=> Modified -- restarting.
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
^CTerminate batch job (Y/N)? y
C:\Users\jawford\Meteor Apps\Examples\starter3>
If you run into this problem using Windows 8, you will need to change compatibility mode for the node executable.
Go to the folder where you installed Meteor
Open properties for bin/node.exe
Set compatibility mode for Windows 7
You should now be able to start the application as you did earlier.
This has to do with Fibers not loading correctly. You can attempt to run app/meteor/meteor.js with bin/node, both are in the Meteor directory in Program Files. This could maybe give you more details why it is crashing. It might also be handy to run the tests in the lib/node_modules/fibers folder which might point out why Fibers is misbehaving.
The exit code -1073741819 corresponds to C0000005 which indicates an access violation.
Many users find that setting compatibility mode to "Windows 7" solves that problem, but it doesn't always and there is some evidence that it also occurs on Windows 7.
Investigating a later issue on win Meteor 0.5.9, I discovered a problem with fibers on windows that may explain this issue, and I have a tentative fix.
Please see: https://github.com/TomWij/meteor/issues/66#issuecomment-15994548 for further details.