Hi,
I think the situation is a little more complex and there may be some
network card bug. Below my reasoning.
Martin Husemann wrote:
> I have never seen that (neither on 10.0 nor on -current). It is very
> hard to tell what causes the errors for you. Two potential reasons
> would be network
Hi Martin and Aryabhata,
network is probably the issue. I was around this weekend and used
wireless in two different places, the connection was good. I know both
places and used them often with different computers (parent's house,
girlfriend home.. not some hotel or airport).
However, at my home
On Mon, May 06, 2024 at 12:51:19PM +, Riccardo Mottola wrote:
> I'just doing a git clone or a git pull... so don't blame "me".
> At most git.. or its NetBSD compilation.
I have never seen that (neither on 10.0 nor on -current). It is very
hard to tell what causes the errors for you. Two
Hi,
Lucifer wrote:
> you guys are using too many resources...
I'just doing a git clone or a git pull... so don't blame "me".
At most git.. or its NetBSD compilation.
I am able to perform the same actions on the same repository on slower
or less performing systems with other OSs though.
It seems like you're encountering network-related issues while updating
large Git repositories over WiFi. The error message "RPC failed; curl 92
HTTP/2 stream 7 was not closed cleanly: CANCEL (err 8)" indicates a problem
with the network connection during the fetch operation.
Here are a few
Hi,
I'm updating fairly big git repositories (e.g. mozilla and similar) and
continue getting these errors. I am over a fast WiFi.
e$ git pull
remote: Enumerating objects: 4822, done.
remote: Counting objects: 100% (4822/4822), done.
remote: Compressing objects: 100% (1027/1027), done.
error:
