0v0

You can take the package from the Ubuntu PPA, which is generally updated quickly, and rebuild for Debian using the instructions here.

fn foo(x: i32) {
    match x {
        const { 3.pow(3) } => println!("three cubed"),
        _ => {}
    }
}

But it looks like inline_const_pat is still unstable, only inline_const in expression position is now stabilized.

It's because it has to work in pattern contexts as well, which are not expressions.

According to Wikipedia:

In March or April 2023, it dimmed to magnitude 12.3. A similar dimming occurred in the year before the 1946 outburst, indicating that it will likely erupt between April and September 2024.

You can give chisel a try. It tunnels all traffic over http/https, and the client can then create port forwards, just as with ssh, to access other services.

Yes, for example, syncing on a kernel panic could lead to data corruption (which is why we don't do that). For the same reason REISUB is not recommended anymore: The default advice for a locked-up system should be SysRq B.

Edit i2psnark.upbw.max in i2psnark.config (this can be in a number of locations based on install type and platform - just search for it).

Or you can remove the maxlength and size attributes from the text input, it will save just fine.

https://linux-tc-notes.sourceforge.net/tc/doc/cls_u32.txt:

The base operation of the u32 filter is actually very simple. It extracts a bit field from a 32 bit word in the packet, and if it is equal to a value supplied by you it has a match. The 32 bit word must lie at a 32 bit boundary.

There is no central naming authority in I2P. All hostnames are local. (Naming and Address Book)

Therefore, if an url doesn't work, it isn't in your local address book.

You can add mappings yourself if you know the destination or b32 address, or make use of subscriptions. In this case, add http://i2p-projekt.i2p/hosts.txt and http://notbob.i2p/hosts.txt to your address book subscriptions, the latter contains the destination for mysu.i2p.

Try perhaps the solution in https://unix.stackexchange.com/questions/648084/docker-interface-tears-down-wifi-internet

Try removing all the superfluous default routes.

I think glider can do this, with -strategy rr (Round Robin mode). I have not used it in this way myself, so you might need to experiment a little. Proxychains can also do this, but it doesn't present a socks5 interface itself (it uses LD_PRELOAD, so it won't work everywhere).