[quarkus] Missing Error handler

[matzew]

When an error/exception occurs, I sometimes want to decorate the actual HTTP response, returned by Quarkus.

Motivation for decorating the error is here.

Now, let's say I have a bogus app that creates a NPE, like:

@Funq
public CloudEvent<Output> function(CloudEvent<Input> input) {

    // Add your business logic here
    iAmNull.toString();

    ...
    ...

    return CloudEventBuilder.create().build(replayEvent);
}

this gives me this log, on the kn func run... console:

2022-09-30 08:01:23,905 ERROR [io.qua.ver.htt.run.QuarkusErrorHandler] (executor-thread-0) HTTP Request to / failed, error id: cc9491bf-4257-4762-a84e-89031ff05010-1: io.quarkus.funqy.runtime.ApplicationException: java.lang.NullPointerException
	at io.quarkus.funqy.runtime.FunctionInvoker.invoke(FunctionInvoker.java:134)
	at io.quarkus.funqy.runtime.bindings.knative.events.VertxRequestHandler.dispatch(VertxRequestHandler.java:567)
	at io.quarkus.funqy.runtime.bindings.knative.events.VertxRequestHandler.lambda$processCloudEvent$4(VertxRequestHandler.java:399)
	at io.quarkus.vertx.core.runtime.VertxCoreRecorder$13.runWith(VertxCoreRecorder.java:545)
	at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
	at org.jboss.threads.DelegatingRunnable.run(DelegatingRunnable.java:29)
	at org.jboss.threads.ThreadLocalResettingRunnable.run(ThreadLocalResettingRunnable.java:29)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
	at functions.Function.function(Function.java:27)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at io.quarkus.funqy.runtime.FunctionInvoker.invoke(FunctionInvoker.java:123)
	... 9 more

and the curl:

* Connected to localhost (127.0.0.1) port 8080 (#0)
> POST / HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.79.1
> Accept: */*
> content-type: application/json
> ce-specversion: 1.0
> ce-source: curl-command
> ce-type: curl.demo
> ce-smartevent: super-duper-event-extension
> ce-id: 123-abc
> Content-Length: 25
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< content-type: application/json; charset=utf-8
< content-length: 72
< 
* Connection #0 to host localhost left intact
{"details":"Error id cc9491bf-4257-4762-a84e-89031ff05010-1","stack":""}%                

It would be nice if the documentation shows how to add an error-handler or the like

[lance]

/kind enhancement

[lance]

/kind good-first-issue

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[zroubalik]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[lance]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.