Sophie Dankel

@mitchmindtree Alright if I close this?

This doesn't seem compatible with tracing because with tracing there is no direct access to the stdout stream. With tracing you have to create an event which the subscriber listens...

I have the exact [same issue](https://github.com/FuelLabs/sway-vscode-plugin/actions/runs/4020292770/jobs/6908048942). I don't want to change the repo's tag formatting. Support for tag prefixes would allow me to use this github action.

@undergroundwires Are you accepting pull requests? I can try to implement this.

I'm on board with using DWARF format since it'll allow us to do a lot more with the debugger in the future. Using line-col everywhere seems good from the debugger...

A user was also confused by this: https://forum.fuel.network/t/forc-build-linter-issues-always-says-unused/2779 > It's reasonable to assume that storage variables that are only written but not read are generally indicative of a bug. I...

@eureka-cpu Could you share some examples of code where this is broken?

Happened again with additional logging: https://github.com/FuelLabs/sway/actions/runs/4347930396/jobs/7595847115 ``` ---- go_to_definition_for_paths stdout ---- thread 'go_to_definition_for_paths' panicked at 'Failed to deserialize response: Null input: Request { jsonrpc: Version, method: "textDocument/definition", params: Some( Object...

We could try switching to `cargo-nextest` to get retries on [flaky tests](https://nexte.st/book/retries.html) like this one. It should also speed up CI times in the `sway` repo overall.

We should rethink this solution in light of https://github.com/FuelLabs/sway/issues/4981