Re: [Savannah-users] broken 'git clone ssh://git.sv.gnu.org/srv/git/PKG.git'
Andreas Schwab wrote: > Pavel Raiskup writes: > > > .. I'm unable to 'git clone git://' from savannah, ATM. I tried several > > packages, but unsuccessful. It always goes like this: > > Anonymous access is probably limited to avoid too much load. I wish I could say exactly what is happening but at this time I have no reasonable findings. I can only say that I was able to see the same problem myself when testing it. Problem confirmed. But then later it worked fine. It isn't a hard repeatable failure. It is different on different invocations. I can only suggest to keep retrying as it will eventually work. The git-daemon is being invoked through a timeout wrapper script invoked through the xinetd. The xinetd is limited to 20 parallel daemon processes for exactly the reason to avoid too much load. It used to be 40 parallel git-daemon processes but when Emacs converted to git and all 40 slots were running it overloaded the system and it would melt down. Xinetd git-daemon maximum instances was reduced to 20 in order to reduce the level to something that the system could reasonable handle. It has been that way for the last year. But the failure of an immediate git clone failure does not match the behavior that should be happening when max instances has been reached. In that case it should be paused waiting for a free slot (might eventually time out if it goes too long) and not failing immediately. And so the debugging continues in order to try to understand this issue. Bob
Re: [Savannah-users] broken 'git clone ssh://git.sv.gnu.org/srv/git/PKG.git'
Pavel Raiskup writes: > .. I'm unable to 'git clone git://' from savannah, ATM. I tried several > packages, but unsuccessful. It always goes like this: Anonymous access is probably limited to avoid too much load. > Clone over https/ssh still works, but the git:// is usually used for > git-submodules (so might be considered important). You can use git config url.ssh://git.sv.gnu.org/srv/git/.insteadof git://git.sv.gnu.org/ to automatically redirect git:// to ssh://. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: [Savannah-users] Help with PNG++ (max size images)
Hello, On 02/23/2016 06:54 AM, wim peters wrote: I'm working with you C++ solution to libpng (PNGPP) and it works great. [...] Please help me? This is the savannah user mailing list - it deals with issues relating to the GNU Savannah website ( http://savannah.gnu.org ). We can not help with libpng/programming related issues. Best to search for a related mailing list at http://www.libpng.org/ . regards, - assaf
[Savannah-users] Help with PNG++ (max size images)
Hello Savannah I'm working with you C++ solution to libpng (PNGPP) and it works great. I only have one problem... I'm working on an image processing project which has to load big images (like 799x2429 pixels). When I read the pixel values of a small image, it works just fine. But when I read a big image, the values are all wrong. So I was wondering if there is a maximum size for the image? Or did I oversee something in your code? This is all I have now (just to get used to your code and to see how to compare and read all the values) png::image< png::rgba_pixel > img, img2; img.read(argv[1]); img2.read(argv[2]); for(unsigned int y = 0; y < img.get_height(); y++) { for(unsigned int x = 0; x < img.get_width(); x++) { /*if(img[x][y].red == 0) cout << "x:" << x << "y:" << y << endl;*/ } } cout << "pix[0][2429] " << (int)img[14][14].red << endl; cout << "pix2[0][2429] " << (int)img2[14][14].red << endl; so its nothing big of a code. Please help me? Greetings Wim Peters
[Savannah-users] broken 'git clone ssh://git.sv.gnu.org/srv/git/PKG.git'
On Saturday 20 of February 2016 11:30:56 Bob Proulx wrote: > The vcs system was suffering from a system overload. Caused by a > DDos? Caused by an overload of normal usage? It was impossible to > tell. The FSF admins were aware of the problem and were working to > address the issue. After an hour of tinkering the server became > usable again. I wish I could say it was some specific problem but in > the end after working through multiple overload issues the overload > stopped. Upgrading the servers has been a long discussed topic. > > See the out of band status information page for up to the moment > status information. > > https://pumprock.net/fsfstatus > > It may not be obvious to people but all of the version control > services (git, svn, cvs, hg, bzr, viewcvs, cgit, and so forth) all > live on the same vcs server. Therefore when the server is overloaded > all vcs services are affected. Thanks for the info. This report might be related or not. As I believe this list is correct place to report issues, and it does not seem to be mentioned on fsfstatus page .. .. I'm unable to 'git clone git://' from savannah, ATM. I tried several packages, but unsuccessful. It always goes like this: $ git clone git://git.sv.gnu.org/gnulib.git Cloning into 'gnulib'... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Clone over https/ssh still works, but the git:// is usually used for git-submodules (so might be considered important). Thanks, Pavel