-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't push again to reset repository #10
Comments
The original design of resumable did not account for resetting repos on
language depot. So this could be fixed in hgresume and on the client.
Chris
…On Tue, Mar 26, 2024 at 8:52 PM Tim Haasdyk ***@***.***> wrote:
If I:
1. Create a new repository on Language Depot
2. I can push to it with resumable 👍
3. I reset the repository on Language Depot
4. When I try to push again it fails 💥
5. I delete
C:\ProgramData\SIL\FieldWorks\Projects\sena-3\Chorus\ChorusStorage
6. I can push again 👍
So, it seems that the cache on the client somehow leads to confusion on
the server.
I presume the server is at fault.
Here's the relevant part of the logs
Ping took 19 milliseconds
Receiving any changes from languageForge.org [Low bandwidth]
(languageForge.org [Low bandwidth] is https://resumable.languageforge.org/sena-3-test-test-flex)
Initiating Resumable Transport
Executing: tip --template "changeset:{rev}:{node|short}
branch:{branches}
user:{author}
date:{date|rfc822date}
tag:{tags}
summary:{desc}
"
standout: changeset:4:216ebe50688b
branch:7500002.7000072
user:tim
date:Tue, 26 Mar 2024 14:34:08 +0100
tag:tip
summary:[FLExBridge: 4.1.0-beta.4+Branch.develop.Sha.14f14c27739551774de26d7b15ac4d05a2408005] sync
changeset:4:216ebe50688b
branch:7500002.7000072
user:tim
date:Tue, 26 Mar 2024 14:34:08 +0100
tag:tip
summary:[FLExBridge: 4.1.0-beta.4+Branch.develop.Sha.14f14c27739551774de26d7b15ac4d05a2408005] sync
Using cached result: log -r0 --template "{node}"
standout: 1af18777e23eadd69d4f9bddc9df202c64be804c
Using cached result: log -r4 --template "{node}"
standout: 216ebe50688b973d4c8d63cf4c49f52831418541
API REQ: https://resumable.languageforge.org/api/v03/pullBundleChunk?offset=0&chunkSize=5000&transId=da66d9d2-33fd-430c-9934-402fcc475553&baseHashes[]=216ebe50688b&baseHashes[]=1af18777e23e&repoId=sena-3-test-test-flex Timeout
Warning: Pull operation timed out. Retrying...
API REQ: https://resumable.languageforge.org/api/v03/pullBundleChunk?offset=0&chunkSize=5000&transId=da66d9d2-33fd-430c-9934-402fcc475553&baseHashes[]=216ebe50688b&baseHashes[]=1af18777e23e&repoId=sena-3-test-test-flex Timeout
Warning: Pull operation timed out. Retrying...
and a trace
<https://ui.honeycomb.io/sil-language-forge/environments/prod/result/bEe79iDfohJ/trace/DMdbLfo6YCA?fields%5B%5D=s_serviceName&fields%5B%5D=s_name&span=3c1ec2201a942e31>
:
image.png (view on web)
<https://github.com/sillsdev/hgresume/assets/12587509/3949785b-acb5-4da0-b27a-5ed269c19fa6>
—
Reply to this email directly, view it on GitHub
<#10>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2I6KPH66LRJARM2ID2O7LY2FVQHAVCNFSM6AAAAABFI7GWJOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYDQMZSGQ2DGOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I:
C:\ProgramData\SIL\FieldWorks\Projects\sena-3\Chorus\ChorusStorage
So, it seems that the cache on the client somehow leads to confusion on the server.
I presume the server is at fault.
Here's the relevant part of the logs
and a trace:
The text was updated successfully, but these errors were encountered: