git push times out

Asked by Dimitri John Ledkov

$ git push --set-upstream lp:~xnox/ubuntu/+source/linux-signed/+git/unstable download-signed-grub2
fatal: remote error: Path translation timed out.

The repository is smallish, and I have a simple patch on top of the https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-signed/+git/unstable

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Tom Wardill (twom) said :
#1

Is this still a problem?
The git service has been showing normal load for the last couple of days, so hoping it's all okay now.

Revision history for this message
Dimitri John Ledkov (xnox) said :
#2

Still fails.

Fails with other projects & teams too.

Revision history for this message
Ioana Lasc (ilasc) said :
#3

Hi Dimitri

Did you manage to set the upstream or are you still seeing timeouts on this?

Revision history for this message
Dimitri John Ledkov (xnox) said :
#4

I'm trying to fork https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-signed/+git/unstable and create a personal fork at https://git.launchpad.net/~xnox/ubuntu/+source/linux-signed/+git/unstable

This fails for me still.

Maybe it would be nice if OOPS id was returned in the git ssh error message?

xnox@ottawa:/tmp$ git clone lp:~ubuntu-kernel/ubuntu/+source/linux-signed/+git/unstable
Cloning into 'unstable'...
remote: Counting objects: 1642, done.
remote: Compressing objects: 100% (1165/1165), done.
remote: Total 1642 (delta 955), reused 911 (delta 462)
Receiving objects: 100% (1642/1642), 210.81 KiB | 1.10 MiB/s, done.
Resolving deltas: 100% (955/955), done.

xnox@ottawa:/tmp$ cd unstable/

xnox@ottawa:/tmp/unstable$ git push --mirror lp:~xnox/ubuntu/+source/linux-signed/+git/unstable
fatal: remote error: Path translation timed out.

xnox@ottawa:/tmp/unstable$ date
Fri 22 May 12:45:06 BST 2020

Revision history for this message
Kristian Glass (doismellburning) said :
#5

Hi Dimitri,

Apologies for the repetition but would you be able to try now? We've had some load issues and this is a hefty push and you're right, we definitely need to at least fail more gracefully, but I've managed success when doing it myself:

```
$ git clone lp:~ubuntu-kernel/ubuntu/+source/linux-signed/+git/unstable 690465
Cloning into '690465'...
remote: Counting objects: 1655, done.
remote: Compressing objects: 100% (1178/1178), done.
remote: Total 1655 (delta 963), reused 911 (delta 462)
Receiving objects: 100% (1655/1655), 213.73 KiB | 715.00 KiB/s, done.
Resolving deltas: 100% (963/963), done.

$ cd 690465/
$ git push --mirror lp:~doismellburning/ubuntu/+source/linux-signed/+g
it/unstable
Enumerating objects: 1655, done.
Counting objects: 100% (1655/1655), done.
Delta compression using up to 2 threads
Compressing objects: 100% (677/677), done.
Writing objects: 100% (1655/1655), 213.65 KiB | 5.62 MiB/s, done.
Total 1655 (delta 963), reused 1655 (delta 963), pack-reused 0
remote: Resolving deltas: 100% (963/963), done.
To ssh://git.launchpad.net/~doismellburning/ubuntu/+source/linux-signed/+git/unstable
 * [new branch] master -> master
# etc...
```

Revision history for this message
Dimitri John Ledkov (xnox) said :
#6

It still fails for me

xnox@ottawa:/tmp$ git clone lp:~ubuntu-kernel/ubuntu/+source/linux-signed/+git/unstable test-20200602
Cloning into 'test-20200602'...
remote: Counting objects: 1655, done.
remote: Compressing objects: 100% (1178/1178), done.
remote: Total 1655 (delta 963), reused 911 (delta 462)
Receiving objects: 100% (1655/1655), 213.73 KiB | 329.00 KiB/s, done.
Resolving deltas: 100% (963/963), done.

xnox@ottawa:/tmp/test-20200602$ git push --mirror lp:~xnox/ubuntu/+source/linux-signed/+git/unstable
fatal: remote error: Path translation timed out.

Can we please trace _my_ pushes to see, why _my_ pushes fail?

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Dimitri John Ledkov (xnox) said :
#8

$ git push lp:~xnox/ubuntu/+source/ceph
fatal: remote error: Path translation timed out.

today again.

I was told that my account may have too many membership. Can I somehow make it better?

I.e. create ~xnox-team "team" and push to that only?

Or should I try to reduce my memberships?

Revision history for this message
Tom Wardill (twom) said :
#9

We've got patches actively landing that should solve this one, tracked by this bug: https://bugs.launchpad.net/launchpad/+bug/1883510
There's not a lot else we can do for it right now I'm afraid.

Revision history for this message
Launchpad Janitor (janitor) said :
#10

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Dimitri John Ledkov (xnox) said :
#11

cd $(mktemp -d)
echo hello > world
git add world
git commit -m "initial"

$ git push --set-upstream lp:~xnox/ubuntu/+source/linux-signed/+git/unstable main
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 868 bytes | 868.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
remote:
remote: Create a merge proposal for 'main' on Launchpad by visiting:
remote: https://code.launchpad.net/~xnox/ubuntu/+source/linux-signed/+git/unstable/+ref/main/+register-merge
remote:
To git+ssh://git.launchpad.net/~xnox/ubuntu/+source/linux-signed/+git/unstable
 * [new branch] main -> main
Branch 'main' set up to track remote branch 'main' from 'lp:~xnox/ubuntu/+source/linux-signed/+git/unstable'.

When i tried it earlier today, it timed out. I guess i "won" the race, by doing things twice, and also having very "small" history to push.

I will subscribed to the bug report. I think this answer can be closed for now.

Revision history for this message
Thiago F. Pappacena (pappacena) said :
#12

Hi, Dimitri!

Indeed, the fix for this problem is in production, but restricted for members of ~launchpad team for now.

We are testing and making sure nothing will break because of that change (it was kind of a big change), and we should rollout that fix to everyone pretty soon.

I'll mark this question as solved, and hope to soon close the bug too.