ITwrxOrg/EZ-Bkup
Template
2
0
Fork 0
Code Issues 2 Pull Requests Packages Projects Releases 4 Wiki Activity

EZBkup crashes intermittently with unhandled OSError and no log output #3

New Issue
Open
opened 2024-11-10 14:40:54 -06:00 by ITwrx · 0 comments
ITwrx commented 2024-11-10 14:40:54 -06:00
Owner
Copy Link

Sometimes the EZBkup crashes with nothing logged. Running from the terminal until a crash happened (second time) produced

oserrors.nim(92)         raiseOSError
Error: unhandled exception: Invalid argument [OSError]

Running again with no changes completes the bkup without crash or error. Next release(s) will focus on updating dependencies and improved robustness/error handling prior to any new feature releases.

Sometimes the EZBkup crashes with nothing logged. Running from the terminal until a crash happened (second time) produced ``` oserrors.nim(92) raiseOSError Error: unhandled exception: Invalid argument [OSError] ``` Running again with no changes completes the bkup without crash or error. Next release(s) will focus on updating dependencies and improved robustness/error handling prior to any new feature releases.
ITwrx added the acceptedbug/defectdesign flaw labels 2024-11-10 14:40:54 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
?/support
Question/Support Request
 accepted
accepted and being worked on.
 bug/defect
not working as designed
 design flaw
working as designed, but design is flawed...
 design note
planning/discussion of how something should work
 duplicate
This issue or pull request already exists
 enhancement
New feature/capability
 fix in dev
This issue is fixed in a development branch but not included in a release yet.
 help wanted
Contributions appreciated!
 invalid
Not actionable as submitted.
 needs info
The issue requires more information for further action.
 rejected
Issue not accepted for implementation.
feedback?
Let us know what you think!
 investigating
Under initial investigation for validity and cause.
 low priority
Could be improved but not the end of the world and it might be a while before it's important enough to address.
 upstream
issue exists in a project that is upstream of EZ Bkup.
No Label accepted bug/defect design flaw
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ITwrx Lucius
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ITwrxOrg/EZ-Bkup#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?