nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error "Uncaught exception during pre-commit trigger processing"

medini_1052680584

Hi forum,

I am creating some components and failure modes via scripting.

At the end I want to delete the ones with failure rates lower than say 0.01 FIT.

When I try to delete them I get the following error message:

Uncaught exception during pre-commit trigger processing

java.lang.NullPointerException

Doing step-by-step in the debugger does not present any error, it is just when the control goes back to medini (return from main()) that the error window pops up.

I've tried to synchronize the worksheet with "synchronizeWorksheet" from fmea.js, but it did not help.

If I finish the script without trying to delete the failure modes, it finishes ok. And then if I run a script containing only the deleting part, it runs also ok. It seems to be a problem of the internal updating of the model.

Have anyone met this error message before?

Cheers, Andre

ps medini 2020 R2

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Interesting! Could you post the minimal set that you think is reperoducing this? So you just

Use the factory.js to create a failure mode and
Use trashbin.js to delete some of them in one rush?

Maybe you really encountered a defect in these libraries.

Anyway, my only suggestion is to not create the failure mode right from the beginning, means, filter them before you use factory.js to create them.

Would that be possible?

Jan

medini_1052680584

Hi Jan,

sure, the minimal code is attached. You have to mark a component with a failure mode and execute it.

In preparing this minimal set I noticed that the line defining

the failure rate kind as DERIVED is crucial. Without it there is no problem.

This might give you a hint of where is the problem.

Filtering the failure modes from the beginning is a bit tricky, but maybe there is no other option.

Thanks for the help!

Cheers, Andre

medini_1024169437

Thanks Andre,

with that I indeed could reproduce the issue. I am not 100% sure, but that is an edge case that is not handled correctly.

I have to confirm. There is a non-documented pragma to deactivate all post-commit handlers but that's a dangereous thing if you are not sure what your script does and what the post commit handlers may do. So I propose to find a way to filter before creation. If that is absolutely not possible, please come back to this thread.

I meanwhile will file an internal defect.

Jan

medini_1052680584

Hi Jan,

Thanks for checking. I will try the filtering before creation. If it is too complicated,
I can just split the script into two, as written above (it is however not ideal).

Cheers, Andre

medini_1024169437

Indeed it is not. I filed a defect meanwhile.

medini_1024169437

... we meanwhile fixed the defect and will most likely release it with some service pack in August.

Jan

medini_1040289819

Hi, the issue was already fixed in version 2023 R2.1 and the fix is also included in the recently released version 2024 R1 of medini analyze.

Regards, Olaf.