domhanak commented on PR #2800:
URL: 
https://github.com/apache/incubator-kie-tools/pull/2800#issuecomment-2572809821

   - Run `kn workflow deploy --wait` on fresh project.
   Results in couple of errors:
   ```
   E0106 11:07:16.646991 1105259 portforward.go:385] "Unhandled Error" 
err="error copying from remote stream to local connection: readfrom tcp4 
127.0.0.1:8080->127.0.0.1:37664: write tcp4 127.0.0.1:8080->127.0.0.1:37664: 
write: broken pipe" logger="UnhandledError"
   E0106 11:07:47.017745 1105259 portforward.go:374] "Unhandled Error" 
err="error creating forwarding stream for port 8080 -> 8080: Timeout occurred" 
logger="UnhandledError"
   E0106 11:07:48.546951 1105259 portforward.go:351] "Unhandled Error" 
err="error creating error stream for port 8080 -> 8080: Timeout occurred" 
logger="UnhandledError"
   ```
   Other than that, it works as expected.
   When I press CTLR+C the deployment stays, but the devui openned by the 
plugin is inaccessible now.
   
   
   - Running `kn workflow deploy  -m 
<PATH_TO_GENERATED_MANIFESTS_WITH_PREVIEW_PROF> --wait`
   Results in:
   ```
   🔨 Applying YAML file 
/home/dhanak/git-workspace/incubator-kie-tools/packages/kn-plugin-workflow/dist/new-project/manifests/01-sonataflow_hello.yaml
    - ✅ Manifest 01-sonataflow_hello.yaml successfully deployed in namespace 
default
   Error: ❌ ERROR: applying deploy: ❌ ERROR: failed to wait for deployment and 
open dev ui: ❌ ERROR: failed to read SonataFlow file: open : no such file or 
directory
   ```
   
   Let me know if this should work or not , the second problem could be out of 
scope for this use case.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to