We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We occasionally see the file transfer from source to target just die without erroring. It's not a big file, 500MB zipped.
The error in the createpunkreplica-replicaname-xxxx-xxx.log logs is not vebose, just
INFO:root:Creating baby publicsafety replica from D:\XX\FGDB\xxx.gdb INFO:root:Synchronizing baby //xxx/xxx/xxxx.gdb replica from D:\xxx\xxx\xxxx.gdb
Add better logging here and maybe try, catch and re-try.
The text was updated successfully, but these errors were encountered:
Additionally, add more info in the failure report to indicate the environment where we have issues.
Right now users must parse a message like:
Failed to replicate D:\XX\XX\xxx.gdb to //xxx-xxx.xx.nycnet/xx/xxx.gdb at 2023-07-20 00:20:58.386065
Sorry, something went wrong.
Partially addressed in 61a4c1a
wraps punk file transfer in loving try catch addresses #29
27598ff
Next up:
As we learn which activities under punkreplica.synchronize()
geodatabase-replication-toiler/src/py/punkreplica.py
Line 82 in 27598ff
periodically fail we will wrap that particular exception to catch more details and report it out.
This is already done in the create() method here, follow the pattern
Line 66 in 27598ff
mattyschell
No branches or pull requests
We occasionally see the file transfer from source to target just die without erroring. It's not a big file, 500MB zipped.
The error in the createpunkreplica-replicaname-xxxx-xxx.log logs is not vebose, just
Add better logging here and maybe try, catch and re-try.
The text was updated successfully, but these errors were encountered: