How to handle different errors that occur in different locations within the interoperability layer #186

Open Sophietje opened 3 years ago

In GitLab by @barry.nouwt.tno.nl on Apr 23, 2021, 12:55

long term solution (see #172):

close a smart connector in 2 steps
introduce an ErrorMessage
use timeouts as proposed in #95 and others.
@wilco.wijbrandi.tno.nl will do (part of) this in #43

In GitLab by @barry.nouwt.tno.nl on Apr 23, 2021, 12:56

marked this issue as related to #160

In GitLab by @barry.nouwt.tno.nl on Apr 30, 2021, 10:58

marked this issue as related to #94

In GitLab by @barry.nouwt.tno.nl on Apr 1, 2022, 11:02

marked this issue as related to #148

In GitLab by @barry.nouwt.tno.nl on Mar 24, 2023, 07:30

@dominic.ectors.vito.be Hey Dominic, just a follow-up on your question yesterday during the WP5 sync call; this issue deals with the propagation of errors, but could also deal with ways to let the KB know whether errors occurred. Here we can discuss solutions and choose the optimal one.

Also, please create a separate issue to discuss the problems you were describing yesterday if necessary, so we can help out!

Regards, Barry

TNO / knowledge-engine

How to handle different errors that occur in different locations within the interoperability layer #186