I've been experiencing this very odd problem lately in Heroku.
I develop and test locally, then I push the changes to Heroku. Even though the files pushed have been changed (and Heroku does recognize it and push the new files), when I look at the exact webpage on Heroku, it behaves as though it was still using the old version of the file that I just pushed.
When I see the HTML source in firebug, I can actually confirm that the old file is being used.
I've tried using git push -f to "force" the git push, but no luck
any ideas??
Try heroku restart to force a restart of all the dynos. I'm not positive but I've seen indications like this that they tend to "lazy restart" the dynos and workers after a push. If you want to guarantee all workers and dynos are working off the latest pushed code, do a restart after your push.
I know this is old, but I just recently had this problem, turned out it was just my cache. If you hit ctrl + F5 it hard refreshes the page and the cache. Worked in my case after searching everywhere.
Experienced same problem too, so checked the repo files by running heroku git:clone -a my-app cloned the files currently in heroku master, and confirmed that the files in repo are the updated version. Hence, the newer files are uploaded correctly but is not being reflected by heroku. Hence I ran heroku restart and waited a long time, like 3 or 4 hours, and problem solved, heroku started running the new files.
Not exactly sure if heroku restart or simply waiting for 4 hours solved the problem, and I doubt I needed to wait 4 hours for heroku to reflect newer repo.
However, I think, after deploying to the same master branch git push heroku master, heroku needs some time to reflect the newer files, hence the switch to newer files will not be instant, it takes time.
Hope this helps anyone else experiencing the same problem.
Related
"This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting .git/hooks/pre-push."
I've never heard of git-LFS, much less installed it, before. This repository was pushing to heroku just fine for 2+ years.
I recently made a new fork so I could try upgrading to rails 5.2 and ruby 2.4. I got it all sorted and pulled my master FROM that fork, so my master is now rails 5.2 and ruby 2.4.
But I can't push it to heroku because of the above error.
I have no idea where git-LFS came from. I never installed it, and now I don't know how to get rid of it.
If anyone knows why I can't push to heroku, or how to disable this git-LFS (that feels like malware), please let me know! I've been searching for hours :(
Git LFS is an extension to Git that provides better handling of large files than native Git. When you use it in a repository, it installs hooks to ensure that the LFS files are pushed when you push your repository.
You should check your repository for a .gitattributes file. If there is one, and it contains entries that say filter=lfs, then your repository is using it to store large files. If not, then you can fix this by removing the hook in .git/hooks/pre-push, as the message says.
You haven't specified what operating system you're using or where you get your software from, so I can't tell you how it likely got installed, but it is currently removed from your system, which is why you see the message. It may have been installed through your system package manager, such as dpkg or Homebrew. If you're running on Windows, it's shipped as a standard part of Git for Windows.
I'm on a Mac. It really was as simple as deleting that file. It didn't occur to me at first that it was literally just a file in a folder on my hard drive because files and folders don't start with a period. And everything I'd read said to delete it from my repository; I read that and I'm thinking it's on github somewhere, not my local drive. Then I looked in my app's folder and saw a .git folder at the top, and from there it was obvious.
Today I made a change to my rails app, deployed it to Heroku, and everything seemed fine. But then, when I looked at the production website, my changes were not reflected. I ran heroku releases (and looked at their web dashboard version of this information) and indeed it shows my code should be there. It's pointing to the git commit that has my changed code in it as the one that was the most recent release.
Here's where it gets crazy: I use heroku run bash to get into the filesystem of my actual server, I use cat to view the changed file, and the new code isn't there! It's still the old version.
Has anyone seen this before? What else can I do to debug/fix this issue?
There is currently a large issue with Heroku that seems to be happening.
Their site: https://status.heroku.com/ seems to claim its only for Performance-L dynos. But if you search https://twitter.com/search?q=heroku&src=typd, you'll find convos about a lot of people not seeing the newest code deployed and/or having apps fully crashed.
I have this issue with Xcode 5 where I'm trying to commit a file to a remote git repository (BitBucket) and getting a pop up window with the following error: "The repository "project_name" could not be reached. Please verify that the repository is online and reachable and try again."
I've been working with this setup for awhile now (since Xcode 4) and didn't have any problems with it. Under Xcode->Preferences->Accounts->Repositories I saw the correct repository, but duplicated. I deleted and added it again, but it didn't help. I tried closing the project and rebooting the computer and it didn't help either. I can see the project's history under Source Control->History. I can access the repository on BitBucket.
Any idea where this is coming from and how to solve this issue?
Not sure if this helps in the tracking down of this problem, but here goes anyway:
I have been connecting to a local network git repository perfectly well for a number of months, but I encountered this problem later yesterday and nothing I did seemed to improve the situation. That included:
Rebooting both the development machine and the server;
Reinstalling Xcode from the App Store;
Re-cloning the project from the git command line (which could see the repository perfectly well);
Checking out the repository from Xcode (I was able to check out but every other operation, such as , Commit, Refresh Status etc. seemed to cause the problem...)
Manipulation the repository with SourceTree (which could also see it fine).
Eventually I stumbled across a solution to my local issue. If I launch Xcode with a wired and wireless network enabled then I can't see the repository. If I close it, disable wifi and relaunch it then I can.
I've not had much opportunity to work out what the difference is (especially as the wifi connects to the same network and is the secondary choice for networking) but it does seem to fix it.
Hope that might help others and hopefully I can find a real explanation soon!
Dave,
Well it seems this had nothing to do with Bitbucket.
The problem was a messed up .git folder on my machine.
My project resides in a Dropbox folder. Somehow, perhaps because of accessing it from different machines, it created copy/duplicate files in the .git folder and it messed up Git. After fixing all the conflicts Git returned to working as usual and I was able to commit from Xcode to the remote repository.
Now, if you encounter this issue, you might not have the same setup as mine or work on Dropbox or any similar service, but I strongly recommend checking your Git folder thoroughly. Good chance something is messed up there.
Check internet connection of system.also quit xcode and reopen it.
I created a project with local git repository using XCode 5 (preview 6), made some changes and tried to commit, and finally got the message "The repository 'HelloWorld2' could not be reached, please verify that the repository is online and reachable and try again".
The same message is also shown when the Refresh Status menu item under Source Control menu is clicked.
Actually, I have XCode 4.5 installed and run side by side with 5.0, but the issue does not exist when the project is opened using Xcode 4.5. Also, the commit action works fine as well via command line.
Not sure if this helps in the tracking down of this problem, but here goes anyway:
I have been connecting to a local network git repository perfectly well for a number of months, but I encountered this problem later yesterday and nothing I did seemed to improve the situation. That included:
Rebooting both the development machine and the server;
Reinstalling Xcode from the App Store;
Re-cloning the project from the git command line (which could see the repository perfectly well);
Checking out the repository from Xcode (I was able to check out but every other operation, such as , Commit, Refresh Status etc. seemed to cause the problem...)
Manipulation the repository with SourceTree (which could also see it fine).
Eventually I stumbled across a solution to my local issue. If I launch Xcode with a wired and wireless network enabled then I can't see the repository. If I close it, disable wifi and relaunch it then I can.
I've not had much opportunity to work out what the difference is (especially as the wifi connects to the same network and is the secondary choice for networking) but it does seem to fix it.
Hope that might help others and hopefully I can find a real explanation soon!
Dave,
I've installed github for windows.
I cloned a repository to my local drive.
But when i make some changes into my app from eclipse, the changes doesn't come in github for windows .
hoping a reply soon .
P.S. I am a noob
For anyone else reading this: if you generate a large amount of untracked/modified data, the GitHub Windows app sometimes appears to be ignorant of all recent changes.
For example: if you generate a bunch of untracked Doxygen files (~500MB), it may take GitHub a very long time to finally show "Uncommitted changes". In the meantime, you may not see any of your changes.
If your git bash shows changes, and your GitHub gui does not, then this is likely your issue.