I'm attempting to log in to Github using the PyCharm IDE.
It keeps saying that I cannot log in with the credentials that I gave it. I made sure my login credentials were correct by logging in on the github.com site. I also made sure capos lock wasn't on. I swear I'm not crazy and am putting in the right credentials.
Any idea what the problem could be?
GitHub has shut down v1 and v2 APIs on June 12. PyCharm is still using v2 API, therefore it will no longer work until a new PyCharm version using v3 API is released. The same applies to the other products based on the IntelliJ IDEA platform (WebStorm, PhpStorm, IDEA, AppCode, RubyMine).
You can track the progress of this issue in YouTrack.
Related
I have just created a hosted blazor webassembly pwa project, which generates client, server and shared projects, all fine. I start the solution and everything runs fine.
But after I start to add small changes to the projects it stops working with a message like this:
"Failed to find a valid digest in the 'integrity' attribute for resource '' with computed SHA-256 integrity '47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='. The resource has been blocked."
I search the net and stack overflow and find others having almost the same problem. Some can do clean and rebuild to solve this, but that's not working for me.
So, what is this? Why is this happening, totally useless?
Is it the PWA feature? Should I create a new solution without the pwa enabled?
It started happening to me recently. Only on a published released solution. Not on local debug.
Clean+rebuild didn't work for me. I had to delete bin and obj folders from both Client and Server (note: tried client only and, it did not work but, did not try server only) then republish.
cf. Failed to find a valid digest in the 'integrity' attribute for resource in Blazor app
It now occurs each time I upgrade or downgrade a package.
I've done several tests and can confirm :
DLL are the right ones (SHA256 hash validated) on the server.
the string in the blazor.publish.boot.json is the right ones.
I was even able to get rid of the problem by reverting to the previous package version prior to the bug (which changes back the related entry in blazor.publish.boot.json). Which for me confirms a reference is not updated somewhere.
The only significant changes I've made recently are switching to VS2022 and .NET6. The bug appeared after I did my first successful publish on Azure through VS2022: 1st package upgrade after that triggered the bug.
I'm trying to setup an integration between my GitHub and VSTS account.
I'm creating a build definition to build and deploy my code to my azure web app. From all the things I've read online (I've been trying to make this work for at least some 3h now) this should be so simple I'm reconsidering calling myself a developer... =/
I've added the Service Endpoint:
But it doesn't show up at the build definition:
The other service endpoints for azure work fine, I'm able to set them at the build definition, but the GitHub just won't work! I've tried signing out, using chrome's private window, removing and re-adding the endpoint, using IE, nothing makes that damn thing show up as an option in the dropdown.
Does anyone have any ideas?
EDIT - ScreenCast
http://screencast-o-matic.com/watch/cDif6XiUSZ
After 3 days and no answer from MS I kept trying to figure it out and it seems this account is running on an old version.(?)
I have another account that's working fine and I started to compare both, here's why I think that:
Different versions
no online column and different header (Account profile vs Account/acc_name)
Perhaps you are right that your account is running in an old server.
I created one in India South and experienced the same behavior.
Then I deleted it and created one in South US and I can see my GitHub repository.
I have a problem in eclipse with the tfs plugin. I try to login and it stuck in some kind of login loop.
I looked here and in google. Nothing help.
I found this posts:
Eclipse with TFS plugin - looping login
http://social.msdn.microsoft.com/Forums/vstudio/en-US/5e3f8b3a-d623-4401-b9f1-50f1f52ab299/eclipse-tfs-plugin-keeps-signing-in-in-loop-followed-by-there-were-some-problems-message
I tried to clean cookies and password and everything possible in IE
I reinstalled the plugin. I updated everything possible, checked for eclipse indigo last version (3.2.7)
Nothing worked. Anyone can help me?
The forum posts you referenced are about the Team Foundation Service, not the on-premise server. Since the service uses Microsoft Accounts (previously known as Live Id's) it depends on cookies in your browser.
The on-premise version of Team Foundation Server uses your domain account which isn't stored as a cookie, but which is stored in the Windows Credentials Vault by default for Windows processes. Try going through the stored credentials to make sure your username/password or TFS server isn't mentioned there. If it is, either update it or remove it.
Can you verify whether the same account settings are correctly picked up by Visual Studio/Team Explorer (if you have it installed on the same machine)? Eclipse and Team Explorer should use the same credential vault.
few days ago (without installing anything new as far as I know) my Eclipse environment started looping authentiacation action when loging to Team Foundation Services. Everytime I want to explore, checkin and so on I see dialog "connecting to server" then dialog loading indentity providers appears and after it white blank screen and all repeats again and again.
I tried to find if I can reset stored password but there is no one in Credentials Manager in Windows (related to TFS address).
I tried update Eclipse plugins (ADT, TFS plugin) to latest version - same behavior.
Any suggestions or same experience
Kind Regards Jindrich Polenius Brezina
I'm afraid that the authentication mechanism got broken during a recent upgrade of the service. It was fixed quickly, but due to the fact that you were unlucky enough to attempt to log-in while it broken I'm afraid that you are going to need to close Eclipse, delete all your cookies in internet explorer, close IE, open Eclipse and attempt to log in again. Very sorry about that.
We have been using the Grails Facebook-graph plugin for a while now - it has been working perfectly until earlier this month when FB apparently turned off their old authentication scheme, and indirectly forced everybody to use oauth2 instead.
This post from FB https://developers.facebook.com/blog/post/525/ describes the changes, and the issue in the Grails plugin seems to be that it does not comply with the new standard.
The main issue appears to be in the way the active user data is being maintained in the plugin. This is currently based on the FB provided cookie "fbs", which contains all the necessary session data related to the active user. Unfortunately, this is no longer provided by FB (apparently replaced by a "fbsr" cookie instead).
I have searched the FB documentation, and in various forums for details on how to upgrade the plugin, but unfortunately without luck.
Can anyone help with a hint or two on what steps should be performed in order to get the plugin updated?
EDIT: I think the updated version of the plugin (0.14) has been pushed the public repository. You should try grabbing that one first before reading the rest of my answer.
It looks like the plugin maintainer, Jesus Lanchas, made some updates over the last few days to enable oauth2 support. It has not been pushed to the plugin repository yet, but I was able to get it working with my project. Here's what I did:
#Install a local copy of the plugin WITHIN my project
mkdir plugins-local
cd plugins-local
git clone git://github.com/chechu/grails-facebook-graph.git
mv grails-facebook-graph facebook-graph
Update BuildConfig.groovy and tell grails where to load the plugin from. I put this line before grails.project.dependency.resolution
grails.plugin.location.'facebook-graph' = "plugins-local/facebook-graph"
Uninstall the existing facebook-graph plugin from my project
grails uninstall-plugin facebook graph
This is a temporary solution for me until the offical update hits the repo, but it allows me to make sure I'm using the same new code everywhere.
EDIT: we released our Facebook Grails SDK on GitHub :
https://github.com/benorama/facebook-grails-sdk.
Currently only tested on Grails 2.0…
Any feedback is welcome before we release it officially to Grails.org.
Indeed, it looks like Grails Facebook-graph plugin does not support OAuth2 Facebook authentication (which is required since October 1st 2011).
We have already ported the official PHP SDK V3.1.1 to ColdFusion 9 (https://github.com/affinitiz/facebook-cf-sdk).
Last month, we started to implement it as a plugin in Grails 2.0.
It is currently at an alpha stage so we have not released it yet, but it is working on our prototype.
To connect to the Facebook Graph API, it uses RestFB internally.
If you want to give it a try and give us some feedbacks, let me know, I'll sent it to you by email.