mitchmindtree

> I am curios about whether the transferability of name would create an attack vector in this case. It's worth keeping in mind we already face this issue with cargo...

Nice job on getting all this down @Voxelot! Sounding good to me. W.r.t. selection implementation: Perhaps we should consider maintaining a DAG representing transaction resource dependency as transactions enter the...

Also running into this issue on Nix + GNOME Wayland + pipewire (Kooha 2.2.3)

Related / blocked by https://github.com/FuelLabs/sway/issues/1527.

After a quick look I'm not too sure off the top of my head :thinking: Curiously, while `nix build .#tidal-listener` fails, doing `nix develop` and then `cd tidal-listener && cabal...

I kept your `--dynamic` hint in mind and had a look at `tidal-listener.cabal` file. It looks like commenting out these `ghc-options: -dynamic-too` lines in the `tidal-listener.cabal` file allows `nix build...

I can confirm that removing the `-dynamic-too` ghc option makes it possible to build and run `tidal-listener` successfully with Nix (on linux at least). Or were you referring to checking...

Hey folks, thanks a lot for reaching out and for digging into this nannou update! I've posted some thoughts on current status, direction, etc in #946 - feel free to...

Seems to also be the case on the following systems: - Ubuntu 18.04 with an i7 and a GTX970 graphics card (I think with proprietary drivers). - Win 10 with...

Nice work on writing this up @otrho! ### Upgradeable Contracts > Storage would be handled by the implementation. There would need be a mechanism to deploy version2 of the implementation...