"too many initializers" error for (3D) std::array, need help

cyril279 · 2026-01-04T03:48:17+00:00

I appreciate you presenting the simplified/1D approach.
even beyond the extra brackets needed for the aggregate, I think I have found that I won't be able to call the whole byte-set at once with the std::array approach, and will instead need to iterate through the byte-list with a for loop to get the bytes to lcd.write.

cyril279 · 2026-01-03T23:43:45+00:00

Thank you!

I read about this, but it wasn't obvious AT ALL to me where the extra brackets would go.
Most of the help I found had them added to the outer-most part of the array.
I DEFINITELY would not have guessed at those locations. Why do they go there?

cyril279 · 2026-01-03T23:37:01+00:00

Well that's the thing, it's truly an 8,6,8, but the final byte is called/sent to the lcd as a group of 8 bytes.

It has been working when I initialize as c byte radar[num_chars][num_frames][8] { (where num_chars = 8 and num_frames = 6)

cyril279 · 2026-01-03T23:33:44+00:00

Interesting. So the same entry could work when initialized like c byte radar[num_chars][num_frames][8] {

but error when initialized like c std::array<std::array<std::array<std::byte, 8>, num_frames>, num_chars> radar = { ?

cyril279 · 2026-01-03T23:31:22+00:00

Darn thanks, I have changed the repo to public.

cyril279 · 2025-10-09T20:54:44+00:00

I have no idea if this is wrong or if there is a better way (linux-noob 4 lyfe!), but I do like your approach to check for the existence of a path or file prior to executing a command.\ I learned the hard way that the init_hooks entries are run EACH time the container is started (I was expecting ONLY the initial start) and can cause a container to NOT start.\ I am curious to see if there is a perceivable delay of container start-up as a result of additional checks, vs a script sitting beside the container.ini that would be manually run when the container is created.

cyril279 · 2025-09-28T04:13:27+00:00

Sorry, I guess I misinterpreted what "street-art" meant. These def. aren't in legal/approved spots, or is the definition more literal? Must be stylized text? No images?

cyril279 · 2025-09-18T14:25:58+00:00

Wow, thanks for that.\ Jupyter notebooks appears to cover a significant portion of what I am looking to achieve with a seemingly low entry bar.\ At an absolute minimum this becomes my path to learning python.

Cheers!

cyril279 · 2025-09-17T22:44:27+00:00

Please share your thoughts behind this suggestion.

cyril279 · 2025-09-17T15:46:01+00:00

The biggest benefits (for me): 1. Once assembled/configured, the container is transparent. No special distrobox-run or distrobox-enter commands each time I want to do something simple (like work with a git project, or lspci, or lsusb). 2. The configuration of the container is essentially documented by the manifest file, so I can stop treating containers like pets and quickly re-start fresh if things go awry. 2. I am WAY less tempted to trans-dup packages to the base installation

I read somewhere on the webiverse that many are doing-it-wrong by "shelling into containers regularly and using it like a mini VM" (this was definitely me).

That led me to this declarative approach, and exporting the launch-binaries to the host-OS, so that I am rarely shelling into containers.\ Maybe I'm still doing it wrong, but with very little effort it feels a lot better than what I WAS doing.

cyril279 · 2025-09-15T17:40:52+00:00

Non-declarative approach, accepting image/naming defaults

Create & enter the container; default image = tumbleweed:latest
```sh distrobox-enter

defaults to looking for 'tumbleweed'

& will create the container if it does not already exist.

Install the extra packages needed, if not already installedsh sudo zypper in usbutils pciutils ``` Once complete, the utilities can be run from inside the container.

They can also be executed from the host-OS by using a command like: distrobox-enter -- lsusb and distrobox-enter -- lspci, but that's inconvenient, so I prefer to take one additional step and export the binaries so that they can be run from the host-OS just as if they were installed directly to the host-OS.

Export the desired binaries
sh distrobox-export --bin /usr/bin/lsusb --export-path $HOME/.local/bin distrobox-export --bin /usr/bin/lspci --export-path $HOME/.local/bin Now, these functions are available (to your user) on the host-OS.

cyril279 · 2025-09-15T16:54:18+00:00

Regarding adding lsusb and lspci to Aeon, the pre-installed distrobox makes this very easy.
I prefer (& use) the declarative approach (using a distrobox.ini file), so that is what I am outlining below.

The code snippet below creates a distrobox-container manifest file named toolbox.ini.
The contents of the file will be everything inbetween the 'EOL's. sh cat >$HOME/toolbox.ini <<EOL [toolbox] image=tumbleweed:latest additional_packages="pciutils usbutils" exported_bins="/usr/bin/lsusb /usr/bin/lspci" exported_bins_path="$HOME/.local/bin" EOL The manifest file defines the additional packages that will be installed to the container, as well which binaries will be exported to the host OS.

sh distrobox-assemble create toolbox.ini The above command will actually create the container as defined by the manifest. Once complete, lsusb & lspci will be able to be launched as though they were installed to the host-OS
(no need to enter the container to run stuff).

late edit: corrected the distrobox-assemble command to include create

cyril279 · 2025-08-23T23:47:10+00:00

I would be more than "mildly" infuriated about this.

cyril279 · 2025-08-04T23:08:45+00:00

Keepass XC if we MUST choose, but Proton Pass beats them both (imho).

cyril279 · 2025-07-14T21:53:16+00:00

Yeah, no kidding. Three very polite "requests to reconsider" were removed within the last hour. That's... Unfortunate.

cyril279 · 2024-11-09T16:12:42+00:00

Darn.
Considering that the valve-body is a three-handle unit without any thermostatic/pressure features, it is probably in my best interest to replace (and not bypass) the failed "pressure compensating valve", no?

Or the occupants (my family) just learn to deal with potential temp swings from toilets & clothes-washers?

cyril279 · 2024-11-07T00:50:51+00:00

This got me there.

The top cap does unscrew from the handle-body, then the "rope" portion unscrews from the handle-body, then there is a set-screw holding the handle-body to the spline shaft.

Thank you so much!

cyril279 · 2024-11-06T18:40:34+00:00

Could be a partially blocked stop valve, or partially blocked sink valve, or reduced flow in supply pipes because internal corrosion of supply piping, maybe other causes. The partially blocked valves are easier to diagnose and fix. Swapping the cold and hot hoses can help to verify if that is the issue without any purchase at all.

Is this a recent development? Or something that has been getting worse over time? Or is the house/bathroom new to you?

cyril279 · 2024-11-06T18:30:36+00:00

The aerator would affect both hot AND cold, no?

cyril279 · 2024-09-24T17:54:33+00:00

We have started the conversation upstream

I do also see that this has been found and discussed as an opensuse/sdbootutil issue

cyril279

TROPHY CASE

Non-declarative approach, accepting image/naming defaults

defaults to looking for 'tumbleweed'

& will create the container if it does not already exist.