Fix binary selection

[samoylovfp]

Checklist

• Updated CHANGELOG.md describing pertinent changes.
• Updated README.md with pertinent info (may not always apply).
• Updated site content with pertinent info (may not always apply).
• Squash down commits to one or two logical commits which clearly describe the work you've done. If you don't, then Dodd will 🤓.

I don't think updating README or site is warranted here.
@thedodd please squash the commits if you think it is beneficial

[samoylovfp]

Example of the error triggering:

[samoylovfp]

Is anything still required from me to get this merged?

[thedodd]

Looks great! @samoylovfp I'm not sure why CI is not triggering. Do you mind rebasing your branch? Hopefully that will allow CI to be triggered.

[samoylovfp]

Will do in a couple of hours

…

On Thu, Mar 23, 2023, 16:52 Anthony Dodd ***@***.***> wrote: Looks great! @samoylovfp <https://github.com/samoylovfp> I'm not sure why CI is not triggering. Do you mind rebasing your branch? Hopefully that will allow CI to be triggered. — Reply to this email directly, view it on GitHub <#476 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEB4TM7CI77BUDNTVTO34KLW5RPS3ANCNFSM6AAAAAATQWQOCI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[samoylovfp]

Really stretching the definition of a "couple", but here we are

[samoylovfp]

Planning to fix the tests during the next weekend

[thedodd]

@samoylovfp as it turns out, at least one of the test failures (building the webworker-gloo example) demonstrates that your changeset does what it says on the tin:

found more than one binary crate: ["webworker-gloo", "worker"], consider adding `<link data-trunk rel="rust" data-bin={bin} />` to the index.html

[samoylovfp]

Whew, good thing the test was there!

Here's how I understood the issue:
webworker-gloo example is working fine in the main branch because cargo always first builds the library and then the binary and the master version of trunk picks up the last of artifacts returned by cargo. Now that cargo_build checks the total number, it started failing.

So I made cargo_build filter out only the binary artifacts for the validation and for choosing which one to use as the wasm entrypoint.

[thedodd]

Gonna merge this after CI goes green.