I am trying to develop my own browser for fun and I am following this turorial. The problem arises when I get to the part where I should fetch chromium by using the command fetch --no-history chromium. When it is done with some part it starts to hung up on "Still working on: src" and keeps repeating it forever:
1>Cloning into 'C:\chromium\_gclient_src_p6la7lya'...
1>remote: Finding sources: 100% (410801/410801)
1>remote: Total 410801 (delta 94529), reused 259376 (delta 94529)
1>Receiving objects: 100% (410801/410801), 1.18 GiB | 9.26 MiB/s, done.
1>Resolving deltas: 100% (94529/94529), done.
[0:03:40] Still working on:
[0:03:40] src
[0:03:50] Still working on:
[0:03:50] src
[0:04:00] Still working on:
[0:04:00] src
[0:04:10] Still working on:
[0:04:10] src
I have tried to stop it, remove all files, restarted computer etc. Nothing works and it is still stuck like this. Has anyone else experienced this issue and knows what is going on?
Related
I have a node app in my local machine, which works totally fine on localhost, i have tried to push the code to github repository, if it didn't work, i created new repos and tried again
I even adopted both methods to push using git bash:
using ssh and http
In my .gitignore file i have written node_modules/
But every time i get the same error message and code is not pushed to my github repo, the error is :
$ git push -u bb4 main
Enter passphrase for key '<path for ssh key>':
Enumerating objects: 2484, done.
Counting objects: 100% (2484/2484), done.
Delta compression using up to 8 threads
Compressing objects: 100% (2457/2457), done.
Writing objects: 100% (2484/2484), 272.37 MiB | 679.00 KiB/s, done.
Total 2484 (delta 492), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (492/492), done.
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
remote: error: Trace: 7eaa2fe7b701a22ea9b13333b122831363593fb6a0ce25c557df3aa90fa29f9e
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File mongod.pdb is 367.00 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: File mongos.pdb is 247.35 MB; this exceeds GitHub's file size limit of 100.00 MB
To github.com:<username>/<reponame>.git
! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'github.com:ritish73/bb4.git'
it shows two too large files mongod.pdb and mongos.pdb, where are these files coming from , i thought they might be in node_modules but i have already added that to .gitignore file.
There is also a .git(hidden) directory inside my project directory which is a local repo of the project handled by vscode itself, Could it be causing some issue? (though i did add this to .gitignore too, still didn't work).
What could be the problem here? Happy to hear your thoughts and resolve this error. This is my directory structure where i run git bash.
Clearly github doesnt allow too big files, you got that right.
You also added node_modules to your .gitignore which is good, too.
You shouldnt add your .git directory, tho, since this is created when you ran git init - this directory is essential for your local git repository.
I guess that you added your node_modules in some previous commit, thus it is added in your history, meaning that the resulting diffs would be pushed to the repository.
You would have to alter these commits to exclude node_modules but for the sake of simplicity it would just create a new git repository (by deleting .git and run git init again)
There seems to be so called Github hook to deny your push, see [remote rejected] main -> main (pre-receive hook declined) error message.
Whoever initialized the repository (maybe you), set up a custom git hook to do some pre-checks before anything is pushed.
git-2.16.2 on linux
I'm not terribly experienced with git push, so please bear with...
I made changes to a clone which was created from origin master. I want to push those changes to origin master without merging with what's there. I tried git push --force but that didn't seem to work even though the messaging seems to indicate that it did...
--> git push --force
Counting objects: 4, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 597 bytes | 597.00 KiB/s, done.
Total 4 (delta 1), reused 0 (delta 0)
To /proj/projects/git_repos/mytool.git
+ eafc0ab...3155ce8 master -> master (forced update)
I say it didn't work because when I now do a git clone of origin master to make a new repo with the changes, the changes aren't there.
The reason I tried the --force is that I want all my local (committed) changes to basically clobber whatever's in origin master. I don't want to merge with whatever's there, although I can see why that's an important thing to be able to do in some circumstances. I'm basically looking for a shortcut around doing the git pull --rebase and all the merging (accepting everything I have locally and rejecting everything else), git add, git rebase --continue, etc... . I just want my local changes to replace whatever's in the origin master.
If there is a shortcut outside of git push --force that I can use to to avoid all the merging and just accept the local changes, that's good, because it'll save the history.
Thanks for any help
OK, I think my mistake was that I did a "git push --force" and not a git push --force origin master". Not sure where things get pushed to, but that appears to have worked.
I have been following several tutorials from Microsoft on the Hololens, from the real basic 100 ( creating a Cube ) to the 101E.
However when deploying to the Hololens it doesn't troughs a error, all succeed, but when starting the App it shows a white screen and then zzz with a Moon "emoticon".
The only error i'm getting is the one attached. However developer license is active. And i also renewed it, but is that related? Don't know.
Log file:
>
3>------ Deploy started: Project: Origami, Configuration: Release x86 ------
3>Deploying to Phone Internal Storage...
3>Creating a new clean layout...
3>Copying files: Total 48 mb to layout...
3>Checking whether required frameworks are installed...
3>Framework: Microsoft.VCLibs.140.00/x86, app package version 14.0.24123.0 is not currently installed.
3>Framework: Microsoft.NET.CoreRuntime.1.0/x86, app package version 1.0.23819.0 is not currently installed.
3>Framework: Microsoft.VCLibs.140.00/x86, app package version 14.0.24123.0 is not currently installed.
3>Installing missing frameworks...
3>Registering the application to run from layout...
3>Deployment complete (0:00:05,557). Full package name: "Origami_1.0.0.0_x86__sx6pycx103f58"
========== Build: 2 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
There are several scenarios which produce this error. Here are a few ways, from my expetience, that may solve this issue:
In the Package.appxmanifest, find the line specifying TargetDeviceFamily and change Name="Windows.Universal" to Name="Windows.Holographic" and MaxVersionTested="10.0.10240.0" to MaxVersionTested="10.0.10586.0".
Go to the device portal and shutdown the instance of the app if it is running.
Try uninstalling the app from the emulator before installing it.
The hololens can be quite tedious to work with at first, but once you get the hang of it, it is a wonderful technology!
I am new to git and have been following various tutorials on setting up a centralized git server. For the past few days, I have been having trouble with the following error message:
Counting objects: 59, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (59/59), done.
Writing objects: 100% (59/59), 525.33 KiB | 0 bytes/s, done.
Total 59 (delta 15), reused 0 (delta 0)
remote: fatal: failed to read object 24e3826fe4be7dbaddbfcd698e943b5b8f9598ec : Bad file descriptor
error: unpack failed: unpack-objects abnormal exit
To ssh://git#[server url]/volume1/git/[project name]
! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'ssh://git#[server url]/volume1/git/[project name]'
Initially, I used GitEye on my client side to manage git repository, but I encountered the problem when I tried to push my first commit to my linux server. So I played around with the permission and set the ownership of the whole git directory recursively to user "git". Nothing works. So I tried cloning a bare repository from the server and then try the push, but that didn't work either...returning me with unpacker error.
So I switch my software to Git Extensions and also trying the push on Git Bash...still the same error. Oh, forgot to mention that in the process, I deleted my local and remote git repository various times.
While one may argue that this may be a duplicate of git push over sshfs failing with “error when closing sha1 file: Bad file descriptor”, but I don't use sshfs and I am running Windows on my client side.
This may be a duplicate of Git push error - fatal: file '' write error: Bad file descriptor, but the push never works before.
UPDATE:
With mentioning about the version, I wonder if the version mismatch between the server and the client is the source of the problem. So I downgrade my client git version from 1.9.4 to 1.8.4.msysgit.0, but still found the problem after deleting and recreating a new git repository.
What interesting though is that I also tried to copy manually the git repository from the client to the server and do a git status on the remote side. As a result, I encounter the bad file descriptor, but that error didn't appear on the client side.
I found the source of the problems. I tried to do a first commit on my remote side and I got "not a valid object" error. Thus, I have a bad git build on my remote side. Thanks for your guidance. It points me the right path to look.
Now I have to figure how to get a newer (or different) version of git for my remote platform without having to use ipkg.
So I'm brand spanking new to Git and development in general. I'm a Linux and Mac user on a few different machines and have a couple cloud servers with AWS, I work on small little python projects on all of them.
I'll try to explain what I want first, hopefully I'm close to having the best solution that will work for my use case. I want to be able to write code on whatever device I own, Ubuntu desktop at home, work Macbook, cloud servers, Ubuntu desktop at work, and a personal Macbook. Obviously I'm working with different hostnames and usernames, I'm the only one that works on my code.
I went through the git guide and it's working, sort of. I tried to setup my repository on my cloud server which I will also be changing code on. I've been trying to commit and push from my Macbook but have been getting a string of permission errors all day, I've been having to go back to the repo and chown -R as my ssh wheel user since every object there is getting overwritten as root.
Here are some sample error messages I'm seeing when trying to push from my macbook:
A commit:
macbook:dev macbookuser$ git commit
# On branch master
# Your branch is ahead of 'origin/master' by 6 commits.
#
nothing to commit, working directory clean
And then the push:
macbook:dev macbookuser$ git push
user1#myserver-aka-repo.com's password:
Counting objects: 18, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (12/12), done.
Writing objects: 100% (14/14), 1.62 KiB, done.
Total 14 (delta 7), reused 0 (delta 0)
error: insufficient permission for adding an object to repository database ./objects
fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To user1#myserver-aka-repo.com:/home/myserver-aka-repo/dev/.git
! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'user1#myserver-aka-repo.com:/home/myserver-aka-repo/dev/.git'
If the chown and umask 0002 don't fix this on the server, make sure the repo you are pushing to has been shared with the right mode.
git config core.sharedRepository
See "Git Push Error: insufficient permission for adding an object to repository database" for more on this option.
I usually set core.sharedRepository to umask, and set my umask to 0002.