<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in errors.rs</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>fce17390 - Migrate wiggle and wiggle generate to `wasmtime::error` (#12276)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#fce17390</link>
        <description>Migrate wiggle and wiggle generate to `wasmtime::error` (#12276)

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Thu, 08 Jan 2026 19:38:05 +0000</pubDate>
        <dc:creator>Nick Fitzgerald &lt;fitzgen@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>90ac295e - Update Wasmtime to the 2024 Rust Edition (#10806)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#90ac295e</link>
        <description>Update Wasmtime to the 2024 Rust Edition (#10806)* Update Wasmtime to the 2024 Rust EditionNow that our MSRV supports the 2024 edition it&apos;s possible to make thisswitch. This commit moves Wasmtime to the 2024 Edition to keepup-to-date with Rust idioms and access many of the edition featuresexclusive to the 2024 edition.prtest:full* Reformat with the 2024 edition

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Mon, 19 May 2025 16:40:55 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>45b60bd6 - Start using `#[expect]` instead of `#[allow]` (#9696)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#45b60bd6</link>
        <description>Start using `#[expect]` instead of `#[allow]` (#9696)* Start using `#[expect]` instead of `#[allow]`In Rust 1.81, our new MSRV, a new feature was added to Rust to use`#[expect]` to control lint levels. This new lint annotation willsilence a lint but will itself cause a lint if it doesn&apos;t actuallysilence anything. This is quite useful to ensure that annotations don&apos;tget stale over time.Another feature is the ability to use a `reason` directive on theattribute with a string explaining why the attribute is there. Thisstring is then rendered in compiler messages if a warning or errorhappens.This commit migrates applies a few changes across the workspace:* Some `#[allow]` are changed to `#[expect]` with a `reason`.* Some `#[allow]` have a `reason` added if the lint conditionally fires  (mostly related to macros).* Some `#[allow]` are removed since the lint doesn&apos;t actually fire.* The workspace configures `clippy::allow_attributes_without_reason = &apos;warn&apos;`  as a &quot;ratchet&quot; to prevent future regressions.* Many crates are annotated to allow `allow_attributes_without_reason`  during this transitionary period.The end-state is that all crates should use`#[expect(..., reason = &quot;...&quot;)]` for any lint that unconditionally firesbut is expected. The `#[allow(..., reason = &quot;...&quot;)]` lint should be usedfor conditionally firing lints, primarily in macro-related code.The `allow_attributes_without_reason = &apos;warn&apos;` level is intended to bepermanent but the transitionary`#[expect(clippy::allow_attributes_without_reason)]` crate annotationsto go away over time.* Fix adapter buildprtest:full* Fix one-core build of icache coherence* Use `allow` for missing_docsWork around rust-lang/rust#130021 which was fixed in Rust 1.83 and isn&apos;tfixed for our MSRV at this time.* More MSRV compat

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Mon, 02 Dec 2024 17:19:20 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>a0442ea0 - Enforce `uninlined_format_args` for the workspace (#9065)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#a0442ea0</link>
        <description>Enforce `uninlined_format_args` for the workspace (#9065)* Enforce `uninlined_format_args` for the workspace* fix: failing `Monolith Checks` job* fix: formatting

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Mon, 05 Aug 2024 09:59:59 +0000</pubDate>
        <dc:creator>Hamir Mahal &lt;hamirmahal@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f1411653 - Remove the borrow checking from `wiggle` entirely (#8702)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#f1411653</link>
        <description>Remove the borrow checking from `wiggle` entirely (#8702)* Remove the borrow checking from `wiggle` entirelyThis commit is a refactoring of the `wiggle` crate which powers the`*.witx`-based bindings generation of Wasmtime for wasip1 support.Originally `wiggle` had a full-blown runtime borrow checker whichverified that borrows were disjoint when appropriate. In #8277 this wasremoved in favor of a more coarse &quot;either all shared or all mutable&quot;guarantee. It turns out that this exactly matches what the Rust typesystem guarantees at compile time as well.This commit removes all runtime borrow checking in favor of compile-timeborrow checking instead. This means that there is no longer thepossibility of a runtime error arising from borrowing errors. Currentbindings in Wasmtime needed no restructuring to work with this new API.The source of the refactors here are all in the `wiggle` crate. Changesinclude:* The `GuestPtr` type lost its type parameter. Additionally it only  contains a `u32` pointer now instead.* The `GuestMemory` trait is replaced with a simple `enum` of  possibilities.* Helper methods on `GuestPtr` are all moved to `GuestMemory`.* A number of abstractions were simplified now that borrow checking is  no longer necessary.* Generated trait methods now all take `&amp;mut GuestMemory&lt;&apos;_&gt;` as an  argument.These changes were then propagated to the `wasmtime-wasi` and`wasi-common` crates in their preview0 and preview1 implementations ofWASI. All changes are just general refactors, no functional change isintended here.* Review comments* Fix publishing of wiggle-macro crate* Fix wiggle docs

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Fri, 31 May 2024 17:22:23 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>22433ed7 - wiggle: new error configuration for generating a &quot;trappable error&quot; (#5276)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#22433ed7</link>
        <description>wiggle: new error configuration for generating a &quot;trappable error&quot; (#5276)* Add a new &quot;trappable&quot; mode for wiggle to make an error typestart refactoring how errors are generated and configuredput a pin in this - you can now configure a generated errorbut i need to go fix NamesNames is no longer a struct, rt is hardcoded to wigglerest of fixes to pass testsits called a trappable error nowdon&apos;t generate UserErrorConversion trait if emptymention in macro docs* undo omitting the user error conversion trait when empty

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Wed, 16 Nov 2022 16:54:41 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;phickey@fastly.com&gt;</dc:creator>
    </item>
<item>
        <title>2afaac51 - Return `anyhow::Error` from host functions instead of `Trap`, redesign `Trap` (#5149)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#2afaac51</link>
        <description>Return `anyhow::Error` from host functions instead of `Trap`, redesign `Trap` (#5149)* Return `anyhow::Error` from host functions instead of `Trap`This commit refactors how errors are modeled when returned from hostfunctions and additionally refactors how custom errors work with `Trap`.At a high level functions in Wasmtime that previously worked with`Result&lt;T, Trap&gt;` now work with `Result&lt;T&gt;` instead where the error is`anyhow::Error`. This includes functions such as:* Host-defined functions in a `Linker&lt;T&gt;`* `TypedFunc::call`* Host-related callbacks like call hooksErrors are now modeled primarily as `anyhow::Error` throughout Wasmtime.This subsequently removes the need for `Trap` to have the ability torepresent all host-defined errors as it previously did. Consequently the`From` implementations for any error into a `Trap` have been removedhere and the only embedder-defined way to create a `Trap` is to use`Trap::new` with a custom string.After this commit the distinction between a `Trap` and a host error isthe wasm backtrace that it contains. Previously all errors in hostfunctions would flow through a `Trap` and get a wasm backtrace attachedto them, but now this only happens if a `Trap` itself is created meaningthat arbitrary host-defined errors flowing from a host import to theother side won&apos;t get backtraces attached. Some internals of Wasmtimeitself were updated or preserved to use `Trap::new` to capture abacktrace where it seemed useful, such as when fuel runs out.The main motivation for this commit is that it now enables hosts tothread a concrete error type from a host function all the way through towhere a wasm function was invoked. Previously this could not be donesince the host error was wrapped in a `Trap` that didn&apos;t provide theability to get at the internals.A consequence of this commit is that when a host error is returned thatisn&apos;t a `Trap` we&apos;ll capture a backtrace and then won&apos;t have a `Trap` toattach it to. To avoid losing the contextual information this commituses the `Error::context` method to attach the backtrace as contextualinformation to ensure that the backtrace is itself not lost.This is a breaking change for likely all users of Wasmtime, but it&apos;shoped to be a relatively minor change to workaround. Most use cases canlikely change `-&gt; Result&lt;T, Trap&gt;` to `-&gt; Result&lt;T&gt;` and otherwiseexplicit creation of a `Trap` is largely no longer necessary.* Fix some doc links* add some tests and make a backtrace type public (#55)* Trap: avoid a trailing newline in the Display implwhich in turn ends up with three newlines between the end of thebacktrace and the `Caused by` in the anyhow Debug impl* make BacktraceContext pub, and add tests showing downcasting behavior of anyhow::Error to traps or backtraces* Remove now-unnecesary `Trap` downcasts in `Linker::module`* Fix test output expectations* Remove `Trap::i32_exit`This commit removes special-handling in the `wasmtime::Trap` type forthe i32 exit code required by WASI. This is now instead modeled as aspecific `I32Exit` error type in the `wasmtime-wasi` crate which isreturned by the `proc_exit` hostcall. Embedders which previously testedfor i32 exits now downcast to the `I32Exit` value.* Remove the `Trap::new` constructorThis commit removes the ability to create a trap with an arbitrary errormessage. The purpose of this commit is to continue the prior trend ofleaning into the `anyhow::Error` type instead of trying to recreate itwith `Trap`. A subsequent simplification to `Trap` after this commit isthat `Trap` will simply be an `enum` of trap codes with no extrainformation. This commit is doubly-motivated by the desire to always usethe new `BacktraceContext` type instead of sometimes using that andsometimes using `Trap`.Most of the changes here were around updating `Trap::new` calls to`bail!` calls instead. Tests which assert particular error messagesadditionally often needed to use the `:?` formatter instead of the `{}`formatter because the prior formats the whole `anyhow::Error` and thelatter only formats the top-most error, which now contains thebacktrace.* Merge `Trap` and `TrapCode`With prior refactorings there&apos;s no more need for `Trap` to be opaque orotherwise contain a backtrace. This commit parse down `Trap` to simplyan `enum` which was the old `TrapCode`. All various tests and such wereupdated to handle this.The main consequence of this commit is that all errors have a`BacktraceContext` context attached to them. This unfortunately meansthat the backtrace is printed first before the error message or trapcode, but given all the prior simplifications that seems worth it atthis time.* Rename `BacktraceContext` to `WasmBacktrace`This feels like a better name given how this has turned out, andadditionally this commit removes having both `WasmBacktrace` and`BacktraceContext`.* Soup up documentation for errors and traps* Fix build of the C APICo-authored-by: Pat Hickey &lt;pat@moreproductive.org&gt;

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Wed, 02 Nov 2022 16:29:31 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>0290a835 - wiggle: make wasmtime a mandatory dep, get rid of own Trap enum (#5137)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#0290a835</link>
        <description>wiggle: make wasmtime a mandatory dep, get rid of own Trap enum (#5137)* wiggle: no longer need to guard wasmtime integration behind a featurethis existed so we could use wiggle in lucet, but lucet is long EOL* replace wiggle::Trap with wiggle::wasmtime_crate::Trap* wiggle tests: unwrap traps because we cant assert_eq on them* wasi-common: emit a wasmtime::Trap instead of a wiggle::Trapformally add a dependency on wasmtime here to make it obvious, thoughwe do now have a transitive one via wiggle no matter what (and thereforecan get rid of the default-features=false on the wiggle dep)* wasi-nn: use wasmtime::Trap instead of wiggle::Trapthere&apos;s no way the implementation of this func is actuallya good idea, it will panic the host process on any error,but I&apos;ll ask @mtr to fix that* wiggle test-helpers examples: fixes* wasi-common cant cross compile to wasm32-unknown-emscripten anymorethis was originally for the WASI polyfill for web targets. Those daysare way behind us now.* wasmtime wont compile for armv7-unknown-linux-gnueabihf either

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Thu, 27 Oct 2022 16:28:10 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;phickey@fastly.com&gt;</dc:creator>
    </item>
<item>
        <title>7a1b7cdf - Implement RFC 11: Redesigning Wasmtime&apos;s APIs (#2897)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#7a1b7cdf</link>
        <description>Implement RFC 11: Redesigning Wasmtime&apos;s APIs (#2897)Implement Wasmtime&apos;s new API as designed by RFC 11. This is quite a large commit which has had lots of discussion externally, so for more information it&apos;s best to read the RFC thread and the PR thread.

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Thu, 03 Jun 2021 14:10:53 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>1c4af27f - delete GuestErrorConversion from docs, tests</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#1c4af27f</link>
        <description>delete GuestErrorConversion from docs, tests

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Wed, 24 Mar 2021 05:20:29 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;pat@moreproductive.org&gt;</dc:creator>
    </item>
<item>
        <title>c4d8e232 - wiggle tests: fixes for new syntax</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#c4d8e232</link>
        <description>wiggle tests: fixes for new syntax

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Fri, 05 Mar 2021 01:27:34 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;pat@moreproductive.org&gt;</dc:creator>
    </item>
<item>
        <title>fa98f0bc - Fix wiggle tests</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#fa98f0bc</link>
        <description>Fix wiggle tests

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Wed, 17 Feb 2021 21:42:41 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>ec1bfeef - fix tests</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#ec1bfeef</link>
        <description>fix tests

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Wed, 06 Jan 2021 21:49:44 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;pat@moreproductive.org&gt;</dc:creator>
    </item>
<item>
        <title>b06ed39c - Fixes #2418: Enhance wiggle to generate its UserErrorConverstion trait with a function that returns Result&lt;abi_err, String&gt; (#2419)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#b06ed39c</link>
        <description>Fixes #2418: Enhance wiggle to generate its UserErrorConverstion trait with a function that returns Result&lt;abi_err, String&gt; (#2419)* Enhance wiggle to generate its UserErrorConverstion trait with a function that returnsa Result&lt;abi_err, String&gt;.  This enhancement allows hostcall implementations using wiggleto return an actionable error to the instance (the abi_err) or to terminate the instanceusing the String as fatal error information.* Enhance wiggle to generate its UserErrorConverstion trait with a function that returnsa Result&lt;abi_err, String&gt;.  This enhancement allows hostcall implementations using wiggleto return an actionable error to the instance (the abi_err) or to terminate the instanceusing the String as fatal error information.* Enhance the wiggle/wasmtime integration to leverage new work in ab7e9c6.  Hostcallimplementations generated by wiggle now return an Result&lt;abi_error, Trap&gt;.  As aresult, hostcalls experiencing fatal errors may trap, thereby terminating thewasmtime instance.  This enhancement has been performed for both wasi snapshot1and wasi snapshot0.* Update wasi-nn crate to reflect enhancement in issue #2418.* Update wiggle test-helpers for wiggle enhancement made in issue #2418.* Address PR feedback; omit verbose return statement.* Address PR feedback; manually format within a proc macro.* Address PR feedback; manually format proc macro.* Restore return statements to wasi.rs.* Restore return statements in funcs.rs.* Address PR feedback; omit TODO and fix formatting.* Ok-wrap error type in assert statement.

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Tue, 24 Nov 2020 20:06:57 +0000</pubDate>
        <dc:creator>Tanya L. Crenshaw &lt;56939192+fst-crenshaw@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>de7ff38f - add a second case for multiple error mappings</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#de7ff38f</link>
        <description>add a second case for multiple error mappings

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Sat, 30 May 2020 21:06:48 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;pat@moreproductive.org&gt;</dc:creator>
    </item>
<item>
        <title>9085fc9f - error conversion code: update test to actually execute it</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#9085fc9f</link>
        <description>error conversion code: update test to actually execute it

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Sat, 30 May 2020 20:50:02 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;pat@moreproductive.org&gt;</dc:creator>
    </item>
<item>
        <title>9038f916 - wiggle: allow user-configurable error transformations</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wiggle/tests/errors.rs#9038f916</link>
        <description>wiggle: allow user-configurable error transformations

            List of files:
            /wasmtime-44.0.1/crates/wiggle/tests/errors.rs</description>
        <pubDate>Fri, 29 May 2020 19:55:57 +0000</pubDate>
        <dc:creator>Pat Hickey &lt;pat@moreproductive.org&gt;</dc:creator>
    </item>
</channel>
</rss>
