-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
No print output from within Spin app #123
Comments
Umm it might be that we didn't pass in stdin, stdout, stderr for wiring up the std io. |
I will take this as an action item to make our integration tests more robust on detecting HTTP headers. |
Can you try it now? I think #121 resolved it |
@Mossaka, the problem still exists: #[http_component]
fn handle_spin_dapr(req: Request) -> Result<Response> {
println!("{:?}\n", req);
... When running with the shim, I only get this and no other output. Serving http://0.0.0.0:80
Available Routes:
spin-dapr: http://0.0.0.0:80 (wildcard) With Serving http://127.0.0.1:3000
Available Routes:
spin-dapr: http://127.0.0.1:3000 (wildcard)
Request { method: POST, uri: /, version: HTTP/1.1, headers: {"host": "localhost:3000", "user-agent": "curl/7.88.1", "accept": "*/*", "spin-path-info": "/", "spin-full-url": "http://localhost:3000/", "spin-matched-route": "/...", "spin-base-path": "/", "spin-raw-component-route": "/...", "spin-component-route": "", "spin-client-addr": "127.0.0.1:44264"}, body: Some(b"") } |
Is this from |
I believe so. Will take a look today |
Hi,
While testing the shims on the
main
branch I found that I can't see print from within the HTTP handler anymore.Simple example:
With v0.8.0 I can see the headers printed to the container log on every request. When using the shim from
main
there is no output. @Mossaka I guess it is related to the LibContainer change.Btw. It's awesome that we have a Redis trigger now 😊
The text was updated successfully, but these errors were encountered: