Brooks Townsend

Thank you for filing this @mrshappy0 , I'm guessing you're on the latest versions of ComponentizeJS / componentize-py? I will take a look at this

I wasn't able to reproduce this for Typescript (e.g. it worked for me) but in Python I do get this error: ``` │ tmp/wtf/pd/build/http_hello_world_s.wasm component_id=python_hello_world-http_component err=failed to link item 46...

Oh great! Yes since it was a release candidate, it wasn't present in the latest `wash`, but that will be addressed now that https://github.com/wasmCloud/wasmCloud/releases/tag/v1.3.0 is out. Just need to run...

Closing because of #2459 , but @LUK3ARK please re-open if there's a piece that hasn't been addressed!

Last week in the community call, https://wasmcloud.com/community/2025/04/16/community-meeting/, we discussed taking the learnings from this exploration and putting them aside for now. @ossfellow please feel free to offer some more comments...

Will definitely need to attempt to reproduce this on Windows, maybe the way we're executing the custom command is not compatible with the Windows PATH 🤔

Yeah this seems super reasonable to setup as a part of the `wash dev` process like, every time 😄

I think really this should just have a quick release that updates the README in the chart to display on https://artifacthub.io/packages/helm/wasmcloud-chart/wasmcloud-chart that points to the new wasmcloud-host chart. On the...

the failing checks in this PR would be resolved by https://github.com/jbg/tokio-postgres-rustls/pull/24 once we can grab a release of tokio-postgres-rustls that depends on a certificate library with an approved license

So on the reverse end what's the best way to ensure that the newest provider-sdks are working well with the currently released version of the wasmCloud host? I like what...