After running
./gradlew bintrayUpload
I am getting the following error.
:my-library:bintrayUpload FAILED
FAILURE: Build failed with an exception.
What went wrong: Execution failed for task ':my-library:bintrayUpload'.
Could not sign version '0.8.1': HTTP/1.1 400 Bad Request [message:Private key is required, please supply it by using a JSON
body or alternatively you can stored in your Bintray profile]
Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
It had been working previously when I installed GPG authentication as described in this tutorial.
However, when I tried to update the version (as described here) it stopped working.
I was able to solve this issue by deleting the GPG key in Bintray and then regenerating the keys.
This happens mostly after the local.properties file is regenerated.
Instead of generating a new key, if you still remember the password, in your local.propreties file just add this line:
bintray.gpg.password= yourpassowrd
Related
When I use cargo run I get this error:
warning: unused manifest key: package.author
error: failed to lock file: C:\Users\lucas\Desktop\Work\Coding\melb_os\Cargo.lock
Caused by:
Denied Access. (os error 5)
I'm using rustc 1.57.0-nightly on a windows machine. My antivirus popped a warning when I ran the code. I had compiled the program before and didn't get any problems, but this time it happened and doesn't seem to work anymore.
I disabled the antivirus, added rustc to the path, tried to run it with other IDE, but changed nothing.
I found the log where Norton blocked rustc-nightly without my knowledge and white listed it. If you have this problem just enter your anti-virus history and look for the log of the action, then you can undo it.
I'm attempting to remote debug a linux module running on docker. Following this article works for a simple test project.
https://devblogs.microsoft.com/iotdev/debug-azure-iot-edge-c-remote-linux-module-container-with-visual-studio-2019-version-16-3/
When I attempt to attach to the module that is setup via SSH with root login permissions enabled, I get this output from Visual Studio:
VSDBG is not installed on my linux target so whats failing is the download/setup of VSDBG. I found a related article on installing VSDBG manually that references the //.vs-debugger path but I'm not sure if this is what is needed
https://www.plcnext-community.net/en/hn-makers-blog/464-remote-debugging-of-a-net-core-application-with-vs-code-on-plcnext.html
I noticed when I select the module to debug that the User Name show "nobody" instead of what I think is normal/expected which is "moduleUser". Is this related to the issue?
So I'm looking for help understanding why the download and install of VSDBG is failing. The SSH credentials are using root so I don't think permissions should be a problem. On the other hand, the failure is simple and possibly permission related:
Command 'mkdir -p '//.vs-debugger'' failed with code '1'. "
If there is a manual set of steps I can follow to install VSDBG so my visual studio attach-to-debug works, as shown above, that would be very helpful.
I am trying to run the Google Cardboard sample by following their guide: https://developers.google.com/cardboard/develop/c/quickstart
However, I run into the same error mentioned in this guide. Their solution was:
You should click the "assemble" option under ":sdk", not the one under ":hellocardboard-android".
As shown below:
The following is the image of my window. I don't have the :hellocardboard-android or :sdk folders, just Tasks.
So, is this the right assemble to be running? I am not sure how to see the other folders mentioned. If you have any clarifying questions let me know!
My full error:
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':hellocardboard-android:externalNativeBuildDebug'.
Build command failed.
Error while executing process C:\Users\Jonah\AppData\Local\Android\Sdk\cmake\3.10.2.4988404\bin\ninja.exe with arguments {-C O:\Dordt University Campus\hellocardboard-android.cxx\cmake\debug\armeabi-v7a cardboard_jni}
ninja: Entering directory `O:\Dordt University Campus\hellocardboard-android.cxx\cmake\debug\armeabi-v7a'
ninja: error: '../../../../libraries/jni/armeabi-v7a/libcardboard_api.so', needed by '../../../../build/intermediates/cmake/debug/obj/armeabi-v7a/libcardboard_jni.so', missing and no known rule to make it
It appears the problem had to do with the path having spaces, moving the project caused the proper folders to appear in the Gradle window.
I am trying to perform a diff of a LabVIEW (.vi) file using TortoiseGit. I get the following error:
Failed to checkout file "*****.vi" of revision ### to
"C:\Users\***\TortoiseGit\*****-###.vi".
libgit2 returned: External filter application exited non-zero (127) and reported:
/usr/bin/sh: git-lfs: command not found
I am using TortoiseGit 2.8.0.0 with a GitLab server. I have lfs enabled. Any file type that is tracked with lfs seems to have this problem. The error message seems straightforward as to what the problem is, but it's not clear to me how to fix it.
Try and launch TortoiseGit after changing the PATH, adding:
C:\Program Files\Git\mingw64\bin
The git-lfs.exe is in %GH%\mingw64\bin
./mingw64/bin/git-lfs.exe
That means TortoiseGit will be able to execute "git lfs" when launched with the proper %PATH% value.
I recently updated to CC.NET 1.5 and I'm now getting some strange exceptions.
On one project I get: -
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: svn: Can't create a character converter from native encoding to 'UTF-8'
This happens when CC is checking a subversion repository for any mods. If I run the actual command line CC says is failing it works and returns an empty XML (there are no mods).
Some other projects also fail to check mods with another "Source control operation failed" exception but no further info. Again the command is an "svn log" which when run from command line works ok.
I'm using subversion 1.4.5 client side and my source repository exists on a separate box than my build server.
Anyone got any ideas?
Have u try to update Svn client ? I doubt it is so simple, but let's check !
Try a svn cleanup
What is your svn config in ccnet ?
What is the build revision of ccnet you are using ? You should try the latest 1.5.x nigthly build, which is very stable for me.
http://ccnetlive.thoughtworks.com/CCNet-builds/1.5.0/
did you try to change the startup parameters of CCService?
Namely, set the "Allow service to interact with desktop" check box on Log On tab.
Also, you may try to use other account than "Local System".
I am not sure, but seems it may fix the issue, since it may be "Local System" account specific issue effect.