I am trying to clone a project from my bitbucket to my computer, using SourceTree.
I tried to do so from the web interface :
But it always failed.
Here is the details of the error.
Can you help me please ?
Update: As mentioned below an update (1.6.25) has been released which fixes this error.
Original: Authentication in Version 1.6.24 of SourceTree is currently not working well. Use version 1.6.23 instead. You can find it here: http://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.6.23.exe
Enjoy:)
Yes, the problem is with Askpass.exe
We recently changed the logging framework we used to slf4net/log4net and this, unexpectedly is being picked up by askpass.exe.
But unfortunately since askpass.exe has no configuration in place it logs some output to stdout by default, this is interfering with the expected stdout output from askpass.exe.
We will release a 1.6.25 tomorrow with a proper fix.
Work Around
As a temporary workaround copying the attached Askpass.exe.config file in to
C:\Program Files (x86)\Atlassian\SourceTree
will provide the necessary configuration and should fix the multiple authentication requests.
You may find that unfortunately SourceTree has deleted what it thought were 'failing' passwords. Apologies for this you will need to re-enter them.
You can see the issue on Atlassian's own Jira: SRCTREEWIN-3944
Edit: Said update appears to be available now.
Help > Check for Updates > Update
Worked for me
It is because of the update which is the Two-step verification. I suggest you read this first to read more about their update and then you proceed over here. I was able to change my default HTTPS protocol to SSH protocol by following the steps above.
Related
I am attempting to follow the Hello World example for deploying an AWS Serverless Application, but I get a Security Constraints Not Satisfied Error when using sam deploy --guided. I'm pressing Enter at each prompt to accept the defaults per the tutorial.
The curious bit--to me--is if I use the AWS Toolkit extension for VS Code to deploy the app it works fine, so I don't think it has anything to do with my IAM permission config, but I'm new to this so I'm not ruling it out.
Recently the guided deploy was updated to include a prompt confirming if you were ok with not having any authorization defined. At the same time, a check was added that would fail the guided deploy if you answer 'No'. (See the relevant part of the commit here.)
This means that, as of this commit, you can't go through the AWS Hello World tutorial by responding with Enter to accept the default options.
To successfully deploy from the command line you'll need to confirm 'Yes' that you're ok with not having any authorization defined, and then it should work as expected.
During your sam deploy --guided, at the following question you need to answer YES.
OR
You can do sam deploy which skip that
I am trying to create a bot using OSX Server 4.0 and Xcode 6.4.
My project encompasses multiple repositories and uses additional libraries as submodules. When I go to "Product > Create Bot," A dialog appears, saying "Provide repository credentials for this bot."
The dialog shows all of the repositories which I use as submodules. If I attempt to authenticate them by either SSH or https, xcode rejects my credentials.
When I click "Ignore" and finish the setup process, it says "Bot creation failed with error: Internal Error Creating Bot" and gives me no other information.
As a test, I have successfully created a sample project in github which I can create a bot for without a problem. I have tried to add submodules to the sample project and it still can create bots fine.
Can anyone help fix this?
I figured out the answer.
The problem ended up being GitSlave (http://gitslave.sourceforge.net/) which my team was using to keep our repositories updated. Something about the way GitSlave set up the repositories causes Xcode bots to fail with an internal error.
My issues accessing the repositories were unrelated to the internal error and were fixed by creating a new set of SSH keys for the bot instead of using my personal SSH keys, which had different permissions.
Hope this helps anyone else having this problem!
I managed to get past the "provide credentials" dialog, but Xcode Bots would fail with the same "Internal Error Creating Bot" error once I had stepped all the way through the wizard and clicked "Create".
The solution in my case was to change the remote.origin.url setting for my repository from a git#github.com SSH URL to a https://github.com HTTPS URL, and suddenly it just worked.
(This is kind of maddening because I checked every log file and every place where there might be an error report and found nothing. Figured it out through trial and error)
I'd like to translate the management console to localized language. I've try to follow the instructions from http://wso2.com/library/knowledge-base/2011/11/playing-around-carbon-product-themes/ as a starting point, cause I think that should be in the same theory. But this didn't work, and cause an exception when entering the site.
I see the document is pretty old (2011), is this not work anymore? or the procedure has been changed?
Edit:
sorry, forgot to mention, I'm using WSO2 ESB 4.8.1.
Yes as you have mentioned, above link is outdated. However, the concept is same in new versions as well. Keeping an extracted jar file in the plugins directory will no longer work since we have disabled that along the way as a security fix.
Herewith I have given [1]. the latest documentation of "Customizing the Management Console" of the WSO2 Enterprise Service Bus. You can use it as a starting point.
If you need further help regarding this issue, please let me know.
Thanks,
Upul
[1]. https://docs.wso2.com/display/ESB481/Customizing+the+Management+Console
I am trying to setup a CI server on my Macbook, I have followed the documentation on the apple website up to the point of creating a bot and integrating my build. When I attempt to integrate the build I repeatedly get the following error:
Bot Issue: error. Build Service Error.
Issue: '/Library/Developer/XcodeServer/Integrations/Caches/14a8ea2a72904f1abcecd38b1c02196b' exists and is not an empty directory (-4).
Integration Number: 13.
Integration URL: https://DavidMcQueens-MacBook-Pro-2.local/xcode/bots/BF817C9/integrations
Description: '/Library/Developer/XcodeServer/Integrations/Caches/14a8ea2a72904f1abcecd38b1c02196b' exists and is not an empty directory (-4).
I have manually deleted the folders in this location, as well as changing the permissions incase the server was having issues writing. Each time I run, I receive the same error. Even after I have deleted the folder so it is empty before the integration.
Does anyone have any ideas on how to solve this issue? I have built my iOS application in Swift (which I believe should still work with the CI server)
I am running OSX Server 4.0 and the latest version of XCode.
I followed Apple's documentation for creating bots
Thanks,
EDIT:
After some experimenting and trying different things to see what the issue is, I disabled 2-factor authentication on my GitHub hosting. This appeared to solve the issue, despite the fact that I was generating a specific application key to get around 2-factor. It solved the issue for a small amount of time, and I managed to successfully get the bot to integrate a few times. However it appears to have gone back to its old tricks.
If anyone has any other knowledge on this, or has managed to get it working on their own machines it will be good to know.
So I believe I have solved this issue, the GitHub 2-factor authentication issue looks to be a red herring.
When setting up the bot, there is a section that says "Checkout the repository", I did not do this step because I already had the repository on my local machine and presumed that it would simply create the repository in another location, and server no other purpose.
However, after some investigation this step is very necessary. From what I understand, checking out the repository does create it again in another location, however this is necessary as this new repository is where the Bot's will pull changes into and build in order to perform the tests. I was trying to use the same repo for development and for the Bots, which it did not like.
Creating a clean checkout of the project (on the server), and configuring the bots in that project then allowed me to progress and get everything setup correctly. It comes down to user error. In hindsight, it makes perfect sense to have a separate repo for the bots (this is my first CI server setup), however the error messages were not helpful and I can't remember seeing this emphasised in the setup guide.
I am trying to install SmartGit and trying to provide bitbucket as hosting provide. I provide correct credentials of my bitbucket account but I get following error:
=======================================
java.security.cert.CerfiticateException: SHA fingerprint of the certificate does not match.
Expected: [some string]
Actual: [some other string]
This may either mean that the server certificate has changed or that you are spoofed.
=======================================
I think this is related to SSL certificate but do not know how to fix it. Any help will be highly appreciated.
From [1]: to fix SmartGit 5.0.7.1 (and older) add following line to smartgit.properties (in the SmartGit settings directory, see About dialog):
smartgit.hostingProvider.bitbucket.sslFingerprint=37:A8:0E:13:87:DA:13:C3:B8:35:6F:84:EF:74:D2:38:B1:AC:59:9B
After restarting SmartGit, connection will work again.
[1] http://blog.syntevo.com/2014/03/09/1394361360000.html
Same problem here. Guess BitBucket changed their key since the latest version got released.
Solution (or rather, workaround)...:
Don't add BitBucket as a remote provider. Add your URL simply per each project.
Remote -> Add
You can find the URL for your projects on the web interface of BitBucket.
Right after you select a project of yours, a link is displayed on the right side of your screen. It starts with https ... That is what you need.
BitBucket just changed their certificates, as announced on their blog.
On March 7th at 22:00 UTC, we’ll be updating our SSL certificates to replace ones that will be expiring soon. It’s likely that you won’t notice any changes and won’t need to take any action.
You can work around it it using the per-project URLs as described in Shiki's answer.
Just add the following line to your ~/.smartgit/5/smartgit.properties
smartgit.hostingProvider.bitbucket.sslFingerprint=7F:E2:6E:8F:0B:7F:3A:CD:6E:02:54:04:03:57:39:BD:D2:4B:CF:AE
Then re-try adding Bitbucket and it should work.
I had this same issue, but for github and adding the fingerprint to smartgit.properties was not working.
What did work was updating to the latest build (last option in the Help menu).