timeout from a locked repo doing bzr push
Bug #1017591 reported by
ilogue
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Critical
|
Unassigned | ||
Bug Description
When pushing from bazaar after replacing a .svg file, I got this message (twice):
<Fault 380: 'An unexpected error has occurred while updating a Launchpad branch. Please report a Launchpad bug and quote: OOPS-2d7687da8991fdcc1d86d2453c3117a4.'>
OOPS-2d7687da8991fdcc1d86d2453c3117a4
Should I be worried about my repository's state?
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #1 |
Revision history for this message
| ilogue (ilogue) wrote | #2 |
| tags: | added: codehosting-ssh lp-code oops |
| tags: | added: timeout |
| tags: | removed: oops |
| summary: |
- Fault 380 on bzr push + timeout from a locked repo doing bzr push |
To post a comment you must log in.
It looks like this error is being caused by the fact that the remote branch is still locked. This is a bug in Launchpad - it should at least be giving you a better error message.
This doesn't say anything about the state of your repository.
You can probably work around this error by forcibly breaking the lock on the server; this should not be an issue unless you have any other processes actively trying to write to this branch.