add wasmcp blog post #152
add wasmcp blog post #152
Conversation
bowlofarugula
force-pushed
the
wasmcp
branch
from
654d95e to
4702a1c
Compare
|
Could we use this image or are movie scenes off limits lol
|
bowlofarugula
force-pushed
the
wasmcp
branch
8 times, most recently
from
fc98c33 to
96059c0
Compare
|
This is an awesome article, @bowlofarugula! Thank you so much for taking the time to write it. My only suggestion — would it make sense to add one short paragraph at the beginning of the article with some context on how this links to Spin/Wasm? Thank you! |
|
(as for the image, I'm all for good puns, but will defer to @michelleN on this one 😂) |
bowlofarugula
force-pushed
the
wasmcp
branch
from
7afbf4b to
7877cc9
Compare
|
@radu-matei Thank you for the review! Good call on adding some clarity up front. I've pushed an update with that change as well as a section explicitly showing how MCP components can be distributed on OCI registries this way. Also, I looked into the failing build and noticed that a job is tripping broken over links to OpenAI, which are apparently being blocked by them. I have confirmed these links are accessible in the browser. |
bowlofarugula
force-pushed
the
wasmcp
branch
5 times, most recently
from
bfdc537 to
d9180af
Compare
kate-goldenring
left a comment
kate-goldenring
left a comment
There was a problem hiding this comment.
Thank you for all of your work on this! I left a few preliminary comments. I think this is ready to mark as "Ready for Review".
bowlofarugula
force-pushed
the
wasmcp
branch
8 times, most recently
from
bc87ae2 to
e134dde
Compare
|
That failing build is due to OpenAI blocking some of the requests that job is making to validate links to their docs. Is there some way to override that check for specific links? |
|
@bowlofarugula I'm afraid the CI link checker is not smart enough to configure which links to check: we just need to exclude those failing links from checking. Sorry for the noise they're giving you; we will take a look but I'm afraid you'll have to ignore them for now. |
|
@itowlson ah no worries. Should I go ahead and update the job to exclude openai links from checking in this PR? Or do you want to just force merge given the job is marked as required? |
|
@bowlofarugula Ah, we'll force merge. I'm just doing a link checker fix now - thanks for the offer though! |
|
@itowlson sounds good. I can also just rebase if you get that merged before mine |
|
@bowlofarugula Links fix is merged 🤞 |
Signed-off-by: bowlofarugula <[email protected]>
…cp and spin up front. Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
…ch is a great resource for learning about function/tool calling more deeply. Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
Signed-off-by: bowlofarugula <[email protected]>
bowlofarugula
force-pushed
the
wasmcp
branch
4 times, most recently
from
270c783 to
a10d3f4
Compare
Signed-off-by: bowlofarugula <[email protected]>
bowlofarugula
force-pushed
the
wasmcp
branch
from
a10d3f4 to
867de70
Compare
4 participants
No description provided.