View Issue Details

IDProjectCategoryView StatusLast Update
0004040PartDesignBugpublic2021-02-06 06:43
Reporterfreman Assigned To 
Status newResolutionopen 
Target Version0.20 
Summary0004040: lack of error message on failing to pad sketch
DescriptionThere is clearly some test or operation which is failing here but nothing is output at a stage where it can be useful.

Having effectively broken the outline in the sketch, no error is produce on closing when the pad attempts to recompute.

Errors should be adequately trapped and useful output provided as to what failed, at a level where that information is available.

Similarly, on attempting to change the length of the pad in this condition, a window with the text "Error! is really not that informative.

This could be handled in a way which is more informative to the user.
Steps To ReproduceCreate a sketch with closed form.
pad from sketch.
edit sketch to no longer be a closed form.
close sketch.
Note exclamation on pad: try to find some error output, explaining the error.

The attached file shows the state of a model after inadvertently leaving a sketch without a closed form ( the construction lines masked that there was a missing line to close the loop ).

On exiting sketch editor, the pad element named base-block showed an exclamation mark but there was no output in report window nor on the console showing that an error had occurred.

Subsequent attempts to edit the pad produce a tiny window with the text "Error!". As before, nothing more is produced.

Additional InformationOS: Linux (LXDE/LXDE)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17119 (Git)
Build type: Release
Branch: master
Hash: e72b48e0cfcf4773e4b6527c74f2bac11ccff1ab
Python version: 2.7.15
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedKingdom (en_GB)
TagsNo tags attached.
FreeCAD Information



2019-06-27 10:26


housing-error.FCStd (49,989 bytes)


2019-06-28 06:06

reporter   ~0013314

TheMarkster has noticed that the presence of the path elements seems to be eating the error context, leading to the terse and unhelpful "Error!".

I have confirmed that the presence of the jobs do not affect this but at least one path in either job will trigger this bug. With no paths present there is a proper error msg which reports "failed-to-validate-broken-face".

Presumably the change to pad triggers a recompute of the paths and the error context is lost. It seems that this should be trapped and reported before attempting a recompute ( which will be futile anyway if the base pad object is broken).


2022-03-03 13:55

administrator   ~0016792

This ticket has been migrated to GitHub as issue 5958.

Issue History

Date Modified Username Field Change
2019-06-27 10:26 freman New Issue
2019-06-27 10:26 freman File Added: housing-error.FCStd
2019-06-28 06:06 freman Note Added: 0013314
2021-02-06 06:43 abdullah Target Version => 0.20