Skip to content
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

Add logging and error handling to punk file transfer #29

Open
mattyschell opened this issue Jul 20, 2023 · 3 comments
Open

Add logging and error handling to punk file transfer #29

mattyschell opened this issue Jul 20, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@mattyschell
Copy link
Owner

mattyschell commented Jul 20, 2023

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.

@mattyschell mattyschell self-assigned this Jul 20, 2023
@mattyschell mattyschell added the enhancement New feature or request label Jul 20, 2023
@mattyschell
Copy link
Owner Author

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

@mattyschell
Copy link
Owner Author

Partially addressed in 61a4c1a

@mattyschell
Copy link
Owner Author

Next up:

As we learn which activities under punkreplica.synchronize()

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant