dependabot[bot] opened a new pull request, #28154: URL: https://github.com/apache/beam/pull/28154
Bumps [github.com/tetratelabs/wazero](https://github.com/tetratelabs/wazero) from 1.4.0 to 1.5.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tetratelabs/wazero/releases";>github.com/tetratelabs/wazero's releases</a>.</em></p> <blockquote> <h2>v1.5.0</h2> <p>Hey, do you know what time is it? ⏰ Yes! Time for another wazero release! 🎉</p> <p>Notably, as <a href="https://github.com/tetratelabs/wazero/releases/tag/v1.4.0";>previously announced</a>, this release drops support to Go 1.18. But you must be here for the goodies: don't you worry, we have you covered: there's a whole lot of updates especially for you Emscripten fanatics!</p> <p>Time flies when you are having fun: <a href="https://events.linuxfoundation.org/wasmcon/";>WasmCon 2023 is only a few days away (5-6 September)</a>. Remember, our very own <a href="https://github.com/evacchi";><code>@​evacchi</code></a> will be there to talk about wazero, so if you are going to be there, don't be shy and say hi!</p> <h2>Improved Emscripten support</h2> <p>Contributor <a href="https://github.com/jerbob92";><code>@​jerbob92</code></a> together with <a href="https://github.com/mathetake";><code>@​mathetake</code></a> brought quite some improvements to our Emscripten support.</p> <ul> <li>There is now improved support to <code>longjmp</code>, especially useful to exception handling (<a href="https://redirect.github.com/tetratelabs/wazero/pull/1611";>tetratelabs/wazero#1611</a>).</li> <li>We are now allowing a host function to make a nested invocation to another host function (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1626";>#1626</a>, <a href="https://redirect.github.com/tetratelabs/wazero/issues/1636";>#1636</a>).</li> <li>We are exposing some new experimental APIs (<a href="https://redirect.github.com/tetratelabs/wazero/pull/1637";>tetratelabs/wazero#1637</a>) to support a go implementation of <a href="https://emscripten.org/docs/porting/connecting_cpp_and_javascript/embind.html";>Emscripten's Embind</a>.</li> </ul> <p>What is Embind? In <a href="https://github.com/jerbob92";><code>@​jerbob92</code></a>'s words:</p> <blockquote> <p>Embind allows developers to write C++ code and directly interact with that code from Javascript in the browser. It also allows to call Javascript methods directly from C++. [...] [The Wazero implementation] is trying to be a 1-on-1 implementation of the JS version in Emscripten so that the same codebase can be used for both Web and WASI WebAssembly builds.</p> </blockquote> <p>Embind support lives in its own module and you can check it out at <a href="https://github.com/jerbob92/wazero-emscripten-embind";>jerbob92/wazero-emscripten-embind</a>!</p> <h2>Go Version Upgrade</h2> <p>As you may already know, we follow the Go support policy: i.e., we support each major Go release until there are two newer major releases: in <a href="https://github.com/tetratelabs/wazero/releases/tag/v1.4.0";>v1.4.0</a> we added support to Go 1.21, while keeping support to Go 1.18 for a little while more. The time has come to say goodbye to Go 1.18: it's been an honor and a privilege, sir. 🫡</p> <p><a href="https://github.com/evacchi";><code>@​evacchi</code></a> (<a href="https://redirect.github.com/tetratelabs/wazero/pull/1622";>tetratelabs/wazero#1622</a>) and <a href="https://github.com/ncruces";><code>@​ncruces</code></a> (<a href="https://redirect.github.com/tetratelabs/wazero/pull/1620";>tetratelabs/wazero#1620</a>) upgraded the code paths that were relying on old workarounds or simply pointed to an older version.</p> <h2>Other Contributions</h2> <ul> <li> <p>While working on Emscripten support, <a href="https://github.com/jerbob92";><code>@​jerbob92</code></a> discovered that looking up and calling a non-existing function may SIGILL on some platforms (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1621";>#1621</a>). Together with <a href="https://github.com/evacchi";><code>@​evacchi</code></a>, they conducted some detective work and realized that the SIGILL was really due to a cross-compilation bug of a humble <code>nil</code> dereference panic <a href="https://github.com/mathetake";><code>@​mathetake</code></a> released a workaround (<a href="https://redirect.github.com/tetratelabs/wazero/pull/1623";>tetratelabs/wazero#1623</a>) while the bug is fixed upstream.</p> </li> <li> <p><a href="https://github.com/mathetake";><code>@​mathetake</code></a> updated our CI to align our test suites to their upstream (<a href="https://redirect.github.com/tetratelabs/wazero/pull/1617";>tetratelabs/wazero#1617</a>, <a href="https://redirect.github.com/tetratelabs/wazero/pull/1619";>tetratelabs/wazero#1619</a>, <a href="https://redirect.github.com/tetratelabs/wazero/pull/1650";>tetratelabs/wazero#1650</a>).</p> </li> <li> <p>Some minor issues in path handling were fixed by <a href="https://github.com/evacchi";><code>@​evacchi</code></a> in <a href="https://redirect.github.com/tetratelabs/wazero/pull/1648";>tetratelabs/wazero#1648</a></p> </li> <li> <p>We also welcome first-time contributor <a href="https://github.com/philippgille";><code>@​philippgille</code></a> who made a fix to our README! (<a href="https://redirect.github.com/tetratelabs/wazero/pull/1629";>tetratelabs/wazero#1629</a>)</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tetratelabs/wazero/commit/9e4b8ea8c61d1f4d8c8cab40228627280322dba0";><code>9e4b8ea</code></a> wazevo: passes: br_table, loads, select, store, and other spectests (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1658";>#1658</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/8d1fd509d3e1f3be2e5d5ef0537c44ff435c5093";><code>8d1fd50</code></a> wazevo: pass br, break-drop, and block spectests (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1657";>#1657</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/f96f097b39f0894058c387d0444bd6de75e28eb4";><code>f96f097</code></a> wazevo: pass memory_grow.wast (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1656";>#1656</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/a5b30a508c47017fa585173a2ed4535484e86200";><code>a5b30a5</code></a> wasi: fix symlink-related issues with path handling (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1648";>#1648</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/1223d11d6a62d10e4075d644ba5122a8b0c55984";><code>1223d11</code></a> wazevo: pass memory_size.wast (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1653";>#1653</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/d0a3c2d6ebfcc1b18b295bc22acde44a78f3f54f";><code>d0a3c2d</code></a> wazevo: passes local_get.wast (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1652";>#1652</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/8c245b750c552d8d0a530682f66bc25758fd8eb1";><code>8c245b7</code></a> wazevo: passes address, binary, data, nop, etc spec tests (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1651";>#1651</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/adaa417c2f3947168235e7abc8db992c51cf7542";><code>adaa417</code></a> wazevo: pass address.wast (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1649";>#1649</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/320d2aa231f6ab8d08ca9629e19689b2768e3055";><code>320d2aa</code></a> ci: pins the version of wasi-testsuits (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1650";>#1650</a>)</li> <li><a href="https://github.com/tetratelabs/wazero/commit/967d8df56d018386a821a3c340d4f085aa9750bd";><code>967d8df</code></a> Sets up spectest infra for wazevo (<a href="https://redirect.github.com/tetratelabs/wazero/issues/1647";>#1647</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tetratelabs/wazero/compare/v1.4.0...v1.5.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- 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]
