While I am trying to push on GitHUb from rstudio it is stuck and is not reflecting on Github
There might be some mismatch in the settings that I have configured watching tutorials.
Error Screenshot
Git Settings
Rstudio Options
GitHub Account Settings
Repository Settings
I was facing the same issue while following one of the courses online. I don't know exactly what causes this issue.
Problem: Exactly the same with every setting as shown in the screenshot.
The solution:
in RStudio, click on the "Tools" menu and select "Shell"
Run the following command: git push
it might ask you for your git username and password. Supply this
information, make sure it is correct
hopefully, the push is successful, then you can close the window
Now make some more edits to some files so that you have new content to
push
Click on the "push" button in RStudio and this time the push should
work
This is not my solution I found it here: https://stackoverflow.com/a/45804117/5677883
Related
I have a new archlinux installation and got rstudio-desktop-bin from AUR, as the project site says to. However, I get a blank screen (as below) when trying to open it. When using
sudo /usr/bin/rstudio-bin
It opens normally. I tried to reset rstudio from this tutorial
https://support.rstudio.com/hc/en-us/articles/200534577-Resetting-RStudio-Desktop-s-State
and in this question, the problem was solved changing file permission. Both did not work for me.
What could I do?
Rstudio when opening normally:
I found a suggestion that an update to electron may have caused an issue in the RStudio community forums. By disabling sandboxing, they were able to start RStudio as a user and it worked for me:
/usr/bin/rstudio-bin --no-sandbox
To make more permanent until the problem is resolved you can add a line to your .bashrc (or equivalent in another shell):
export RSTUDIO_CHROMIUM_ARGUMENTS="--no-sandbox"
There is also a suggestion in there about building from a weekly source instead. But this was easier for me so I can't vouch for it.
I'm learning RStudio, and I'm stuck with my code not being able to be pushed to the GIT. To give you a brief, I was using another account for the GIT and I used to clone a team repo through it. Recently, I have made my personal account on GIT and have started to work on it. Initially, when I tried to push the code, it was pushing to the previous team repo and my personal account isn't a collaborator of that. It sent an error as unable to access 'https://github.com/AyushSaxena0402/Testing.git/': The requested URL returned an error: 403
After going through some solutions, I deleted my previous account on my Windows system. Now when I try to push the code, it doesn't show this message instead the progress bar keeps loading and doesn't give any result too. I'm pretty new to coding, hence it's pretty hard to understand other answers. If someone can help me out, it'll be great.
Attaching the screenshot of the progress bar. Screenshot of the loading progress bar
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.
I am trying to create a website using the R package blogdown. Just have a little problem here. After these functions,
library(blogdown)
new_site()
I tried to commit the folders to Github (have a look)
I don't get anything after pressing "Commit". When I try to check the boxes, nothing happens. When I click "Stage", nothing. What's gone wrong?
Your problem has nothing to do with blogdown but it is a GIT issue. From your picture, it seems, that you did not select and check all the boxes for those files you want to stage. This is necessary to tell GIT which files it should include for your commit:
Check those files you want to prepare for the commit. Only those files which are staged will be included in the commit. (This is the action you missed!)
Add a commit message (this you have already done)
Only now you can click the button "Commit" successfully.
The documentation for blogdown is pretty extensive. In particular, I suggest reviewing the quick example here.
You've generated the template for a new site with blogdown::new_site() but you haven't built it without running blogdown::build_site(). Then the public folder that is generated and populated is the thing that should be committed.
I want my project in Rstudio to connect to a repository. However, the push and pull options are grayed out, which leads me to believe I am not connected.
Under tools -> project options -> Git/SVN, I see that I am using Git as the version control system, but the Origin box is grayed out, so I cannot enter the URL that would connect to the repo.
Any ideas what is happening?
Thanks in advance.