oops, managed to send the email too early, but then also extracting the tar etc.
I have also tried simply clean-installing but it doesnt seems to change the outcome. any idea what it could be? Best regards Jeppe Halvorsen ________________________________ Fra: Jeppe Nordvi Halvorsen <h...@itu.dk> Sendt: onsdag 9. april 2025 13:38 Til: dev@wayang.apache.org <dev@wayang.apache.org> Emne: Sv: JSON API error messages Hey Juri, I attempted some changes, but it seems nothing changes when I run it, so I would assume I have a re-build issue I am doing this after making changes: ./mvnw clean install -DskipTests -pl wayang-api ./mvnw clean package -pl :wayang-assembly -Pdistribution ________________________________ Fra: Juri Petersen <j...@itu.dk.INVALID> Sendt: fredag 4. april 2025 08:16 Til: dev@wayang.apache.org <dev@wayang.apache.org> Emne: Re: JSON API error messages Hi Jeppe, I would assume that the parsing of the plan fails here: https://github.com/apache/incubator-wayang/blob/295b624f6158d5cb914a90c620dac6aff1c135b2/wayang-api/wayang-api-json/src/main/scala/parserutil/ParsePlanFromJson.scala#L43 I agree, it should return a useful error message, which shouldn't be too big of a change. I hope this pointer helps. Best, Juri ________________________________ From: Jeppe Nordvi Halvorsen <h...@itu.dk.INVALID> Sent: 03 April 2025 15:51 To: dev@wayang.apache.org <dev@wayang.apache.org> Cc: Christoffer Emil Kristensen <c...@itu.dk> Subject: JSON API error messages You don't often get email from h...@itu.dk.invalid. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hello, Currently for a Project we are attempting to run Wayang plans using the JSON API, The endpoint works with a proper JSON, but when executing faulty plan it would be nice to receive an error message, but currently it only gives a 404. I've looked into wayang-api-json/src/main/scala/Main as it is here the jsonRoute is stored, but it seems whenever I attempt to add prints to debug it never seems to reach the else clause when failing (below), only printing the stack trace to console, though idk if this happens in some other file. Any ideas how this could be solved? [cid:f1c9f329-cfdc-43df-a223-ef2c92867a6b] Best regards, Jeppe Halvorsen
