Sometimes the publish form doesn't respond upon pressing "Publish" but still publishes the nanopub

[tkuhn]

This leads to duplicate nanopubs being published, as it seems the first one didn't get out. Not sure what triggers this, and I can't consistently reproduce it...

[tkuhn]

Error logs look like this:

nanodash-1  | 2026-01-23 10:28:45.107 [http-nio-8080-exec-20] INFO PublishForm - Publish form submitted
nanodash-1  | 2026-01-23 10:28:45.109 [http-nio-8080-exec-20] INFO PublishForm - Nanopublication created: https://w3id.org/np/~~~ARTIFACTCODE~~~/
nanodash-1  | 2026-01-23 10:28:45.113 [http-nio-8080-exec-20] INFO PublishForm - Nanopublication signed: https://w3id.org/np/RA4MprIemmu0Qr8FoKo2rEMZYpXk9mRxCdQ4HrVEAUuKc
nanodash-1  | Initialized logging for CLI Runner. Verbose mode: false
nanodash-1  | 2026-01-23 10:28:45.839 [http-nio-8080-exec-20] INFO PublishForm - Nanopublication published: https://registry.petapico.org/np/RA4MprIemmu0Qr8FoKo2rEMZYpXk9mRxCdQ4HrVEAUuKc
nanodash-1  | 2026-01-23 10:28:46.258 [Thread-3095311] INFO QueryCall - Invoking API operation RAz1ogtMxSTKSOYwHAfD5M3Y-vd1vd46OZta_vvbqh8kY/find-uri-references?ref=https%3A%2F%2Fw3id.org%2Fnp%2FRA4MprIemmu0Qr8FoKo2rEMZYpXk9mRxCdQ4HrVEAUuKc
nanodash-1  | 2026-01-23 10:28:46.258 [Thread-3095311] INFO QueryCall - Trying API (1) https://query.petapico.org/
nanodash-1  | 2026-01-23 10:28:46.258 [Thread-3095311] INFO QueryCall - Trying API (2) https://query.nanodash.net/
nanodash-1  | 2026-01-23 10:28:46.382 [Thread-3095312] INFO QueryCall - Result in from https://query.petapico.org/:
nanodash-1  | 2026-01-23 10:28:46.382 [Thread-3095312] INFO QueryCall - - Request: RAz1ogtMxSTKSOYwHAfD5M3Y-vd1vd46OZta_vvbqh8kY/find-uri-references?ref=https%3A%2F%2Fw3id.org%2Fnp%2FRA4MprIemmu0Qr8FoKo2rEMZYpXk9mRxCdQ4HrVEAUuKc
nanodash-1  | 2026-01-23 10:28:46.382 [Thread-3095312] INFO QueryCall - - Response size: -1
nanodash-1  | 2026-01-23 10:28:46.383 [Thread-3095313] ERROR QueryCall - Request to https://query.nanodash.net/ was not successful: Socket closed
nanodash-1  | 2026-01-23 10:28:46.458 [Thread-3095311] INFO ApiCache - updateResponse find-uri-references?ref=https%3A%2F%2Fw3id.org%2Fnp%2FRA4MprIemmu0Qr8FoKo2rEMZYpXk9mRxCdQ4HrVEAUuKc
nanodash-1  | 2026-01-23 10:28:47.479 [http-nio-8080-exec-7] ERROR DefaultExceptionMapper - Unexpected error occurred
nanodash-1  | org.apache.wicket.behavior.InvalidBehaviorIdException: Cannot find behavior with id '0' on component 'com.knowledgepixels.nanodash.page.ExplorePage:' in page '[Page class = com.knowledgepixels.nanodash.page.ExplorePage, id = 0, render count = 0]'. Perhaps the behavior did not properly implement getStatelessHint() and returned 'true' to indicate that it is stateless instead of returning 'false' to indicate that it is stateful.
nanodash-1  | 	at org.apache.wicket.Behaviors.getBehaviorById(Behaviors.java:363)
nanodash-1  | 	at org.apache.wicket.Component.getBehaviorById(Component.java:4480)
nanodash-1  | 	at org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:216)
nanodash-1  | 	at org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:202)
nanodash-1  | 	at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:913)
nanodash-1  | 	at org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:63)
nanodash-1  | 	at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:294)
nanodash-1  | 	at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:255)
nanodash-1  | 	at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:277)
nanodash-1  | 	at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:208)
nanodash-1  | 	at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:307)
nanodash-1  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:109)
nanodash-1  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)
nanodash-1  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:79)
nanodash-1  | 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:483)
nanodash-1  | 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:116)
nanodash-1  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
nanodash-1  | 	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:666)
nanodash-1  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
nanodash-1  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
nanodash-1  | 	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:396)
nanodash-1  | 	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
nanodash-1  | 	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:903)
nanodash-1  | 	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1780)
nanodash-1  | 	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
nanodash-1  | 	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:948)
nanodash-1  | 	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:482)
nanodash-1  | 	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:57)
nanodash-1  | 	at java.base/java.lang.Thread.run(Thread.java:1474)

[tkuhn]

Related issue of pages disconnecting is resolved with 9f77daf.

This one is probably solved by that too, but I'll leave this open for now to see...

[tkuhn]

This bug seems indeed fixed. So closing this issue.