git repo access denied after months of no problems - git-config

Up until today, I've had no problem using GitHub to access my client's source repository. I've been happily working as a developer for 6 months on their project. Over the weekend I shut down my computer. Something I don't do very often. For the first time since the restart, I attempted to push a branch to the remote I get Authentication failed. You may not have permission.... git command line has the same issue. I figure it must have something to do with some environment variable that I had established and lost, or some configuration file that got overwritten somehow, but I don't know how to get it to work again. I'm looking for ~/.ssh/config file because some posts reference it in relation to this. I don't know where to go. git config --get-all doesn't produce any output. Too few parameters it says. Can anybody help me with this?

Related

Error: could not handle the request comes up when I deploy firebase from my local

On firebase console, it says my files are successfully deployed but in actual web page, it is just a black page with one senetence "Error: could not handle the request"
i did not started this project i am working on, and i have no idea what to do.
BTW, no errors are loged in firebase-debug.log
All things are clear, except for the web page.
As far as i know, this is based on Next.js, if you would care to know.
I opened up the file from the root folder, used "cd (myfilename)" command to go into the actual project, and then executed firebase deploy.
I googled thousands of times, and I doubted these:
node js version problem?
os problem? (i work on Window, and the first start was from Mac)
number one i solved. number two? i dont know.
Please help me out if you have any idea or can guess why this happens.

iExpress error: "Unable to end update of resources"

I've been successfully using iExpress for years. Now, when generating the same .exe files that I always generate, iExpress is now giving me the error: Unable to end update of resources.
This error comes at the very end of the process. I see the Create Package screen and the text "Creating the package..." Then the error occurs. In the file folder, I'll see a file like: ~MyFileName.CAB which would normally be deleted at the end of running iExpress.
I've tried deleting the .CAB file and rerunning iExpress again (many times). I tried rebooting. I tried running iExpress with different applications. I tried searching the web and Stack Overflow. I'm using the same Windows user account I normally use. Desperate for help as I'm unable to release my applications. Thank you!!!
The problem is resolved, though not exactly sure how. I did have another user run iExpress on my machine as that other user. (Ie, right-click on the iExpress executable and run as the other user.) That user was able to run iExpress without the error I reported above. And after that, iExpress started magically working for me too.
Could running as the other user have caused Windows to clear out some file that had been corrupted? Something else? I don't know. I just thought I would write what happened in case this can help someone else in the future.
FURTHER UPDATE
The problem popped up again. I finally figured out that if I closed File Explorer before running iExpress, the error never happens. There's some bug with Windows 10 and/or iExpress where having the folder open can interfere with the final step that iExpress does.
Of interest: It's not a consistent bug. Sometimes iExpress finished and sometimes I got the above error when File Explorer and the folder in question was open.

The package "apppxbundle" is taking a long time to process. Unable to push update to windows store [UWP] [ Xamarin.Forms]

I've been at this for past 2 days and I'm getting weird errors from the store.
I'm trying to upload an update to my application "CoManga" via the store and it's not working out.
I'm working on Xamarin.Forms (UWP) and before making the appxbundle, I made sure and "associated my app with CoManga" from my developer account. All the information over there matches and should work fine without any issues.
Then I made a release of my UWP app, got the bundle and I tried to upload it to UWP.
It said that the Publisher info is different, so it couldn't upload. This is weird because I tried signing the bundle with my developer account itself.
Now, I tried building and signing the app bundle from app center. I got the appxbundle and that I tried to upload. But, since today it's giving me weird error :
The package comic_dl.UWP_2.1.15.0_ARM_x86_x64.appxbundle is taking a
long time to process. If this isn’t completed soon, try refreshing the
page, or remove the package and then upload it again. If you continue
to see this issue, contact support.
This package I tried to build from my system manually : https://drive.google.com/open?id=1VVvF6IB70R2DKNUgBJcqw-HryL1LIwgo
This is what I got from App center : https://drive.google.com/open?id=1o0sGKU2AKVgrcTelIoRFz7QCe8Do0WJ3
This is the Store ID : 9N81F8B5WW93
Can someone guide me what I might be doing wrong/missing something.
Thanks
EDIT Update : So, I followed the suggestion and contacted Microsoft's Team for help on this issue. After 3 months of multiple contacts, I was able to get someone to reply back and follow the case. Even they tried things on their end and I tried by deleting all the certificate files I had in my current project and tried to manually build the manifest file and then it worked. I'm not entirely sure what worked out in the end. But, you can try these things if you run into this issue.
1.) Clean your project.
2.) Delete .vs directory.
3.) Look for any certificate files in your project. Back them up somewhere else and then delete them from the project (Don't exclude from project, just delete them entirely). Clean and rebuild your solution.
4.) Check if the application is already installed on your system (When you debug, VS will install your UWP app on your machine to run it). If it's installed, uninstall it completely.
5.) Make a backup of your manifest file and try to create a new manifest file.
These are the links I received from Microsoft Help:
PFN and package publisher name must match values here: https://partner.microsoft.com/en-us/dashboard/products/{YourAppID}/identity
Update manually: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/how-to-create-a-package-manifest-manually
Update in VS: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/generate-package-manifest
If these values were pulled from test certificate, partner needs to update their test cert: https://learn.microsoft.com/en-us/windows/msix/package/create-certificate-package-signing
I think this problem is not caused by anything code related, but rather it is a problem on the Store side. I would suggest contacting the Store support, they should be able to investigate if there is something wrong with your app package or the problem is on their side.
For support go to the official website, click the Contact Us tab and fill out the form accordingly.
The team should be able to advise even for the first error with different publisher info. If your app was always associated with the same account, there is no reason it should give you such an error message.
I had this issue gazillion of times. It is so frustrating. That error message isn't useful at all.
Anyway - I think it is something in Package.appxmanifest, something in Identity tag.
Retrieving some necessary info from store helped me.
Click right on your project -> Publish -> Associate App with the Store. This will update Package Display Name,Package Name,Publisher ID,Publisher Display Name and Version with correct values (within Package.appxmanifes).
Also be careful with version number. The last from numbers must be zero. 1.1.1.0 is fine, while 1.1.1.1 is not.

Could not find a part of the path .nuget\packages\.tools\Microsoft.Extensions.SecretManager.Tools

After having a 4-month break from my .NET project I suddenly run into this error:
Could not find a part of the path c:\Users\...myusername...\.nuget\packages\.tools\Microsoft.Extensions.SecretManager.Tools
Can anybody explain why I should suddenly get this kind of error? I have checked that Microsoft.Extensions.SecretManager.Tools is not found in the path listed here. I will try to install the SecretManager (although I installed it one year ago), but I'm still confused why I get the error now.
Take a look if you have the package folder in your local machine, maybe when you added the new packages to a project the TFS marked them as pending to check-in and then later you removed them manually from your hard drive, at that moment the tfs has a package pending to upload that is not physically present on the hard drive and that is the error you are getting

Meteor Environment - Blank and Everything Broken

I got to a point where Meteor seemed to just stop working, no HTML would load but the port was open, throwing basic console errors indicating that the most basic parts of the program weren't getting read.
After a lot of troubleshooting (clearing the database, restarting, logging out, using different ports), I just created a new Meteor project and copied and pasted my .html and .js files and the new project worked where the old project didn't.
So, question - how can I troubleshoot this in the future? Something was going on in the Meteor folder because the old and new files were exactly the same.
After a day, the error is happening all the time now and I can't create a single project. I tried uninstalling and reinstalling Meteor with no luck.
Also, the problem seems to be isolated to one port. I can open projects in other ports, but not in 3000.
Why is one port "breaking"? What can I do to fix this?
--Edit--
The HTML and CSS are loading, but in the default port 3000, the console reads
Uncaught ReferenceError: Package is not defined
It shows this code as the first error point:
/* Imports */
var Meteor = Package.meteor.Meteor;
Below is the Terminal:
--Edit--
So this is embarrassing, it seemed to be a cache problem. I cleared the cache, and I'm assuming it refreshed the .js files and now it works.
If anyone can answer why the errors were being thrown in the first place and how to fix besides creating an entirely new project, that would be hugely helpful!
please post your terminal so we have more clues to help you.
You definitely can run other ports, perhaps your port 3000 is used by another program.
Also, never run a meteor app as root.
Run meteor on a high port number. The default is 3000 when you don't give a --port argument. Connect to it via the URL printed in the console - e.g.
meteor --port 3001
http://localhost:3000/.
If you have settings.json then run meteor --settings settings.json

Resources