I'm trying to build bolt with the following commands:
meson build
ninja -C build
I'm seeing this error:
ninja: Entering directory `build'
I'm trying to build bolt with the following commands:
meson build
ninja -C build
I'm seeing this error:
ninja: Entering directory `build'
Instructions on creating a macro to move a row down by one in google sheets. Or in other words, swap the contents of the row containing the current active cell with the contents of the row below the current active cell.
This macro also supports moving multiple rows of any selected range.
There's a potential glitch if repeating the macro quickly multiple times before the previous iteration completes. It seems that google allows the next iteration to start before the first completes, which can cause an unexpected row to be shifted.
The macro takes about 1 second to execute, which is not ideal. I'm not sure if there are any ways to speed this up.
Tools > Script Editor
<!-- This configuration file specifies the required security policies | |
for Bluetooth core daemon to work. --> | |
<!-- Debian-compatible additions to https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/src/bluetooth.conf?h=5.49 --> | |
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" | |
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> | |
<busconfig> | |
<!-- ../system.conf have denied everything, so we just punch some holes --> |
Updating registry at `~/.julia/registries/General` | |
Updating git-repo `https://github.com/JuliaRegistries/General.git` | |
[?25l[2K[?25hPkgBenchmark: Running benchmarks... | |
Activating new environment at `/tmp/jl_80elOh/Project.toml` | |
Resolving package versions... | |
Updating `/tmp/jl_80elOh/Project.toml` | |
[864edb3b] + DataStructures v0.17.0 [`~/temp/DataStructures.jl`] | |
Updating `/tmp/jl_80elOh/Manifest.toml` | |
[864edb3b] + DataStructures v0.17.0 [`~/temp/DataStructures.jl`] | |
[bac558e1] + OrderedCollections v1.1.0 |
julia> @code_llvm debuginfo=:none runbench_expand(UInt) | |
define i64 @julia_runbench_expand_17321(%jl_value_t addrspace(10)*) { | |
top: | |
br label %L2 | |
L2: ; preds = %L30, %top | |
%value_phi = phi i64 [ 0, %top ], [ %value_phi6, %L30 ] | |
%value_phi1 = phi i64 [ 1, %top ], [ %3, %L30 ] | |
br label %pass |
data Column v = Column String | |
data Table columnRow = Table {name :: String, columns :: Record columnRow} | |
data Select tableColumns selectedColumns = Select | |
(Record tableColumns -> Record selectedColumns) | |
(Table tableColumns) | |
data ToStr = ToStr |
Turns out std::span
has some deduction limitations. There's a pending paper proposing a fix which might be applied in C++26. In the meantime, we can use a helper factory function (e.g. as_span
below) to enable this missing deduction capability. We could alternatively apply the fix directly to pw::span
, but upstreaming will be controversial.
// as_span implementation snipped - view in godbolt link below
template<typename T>
void foo(std::span<const T>);
void test() {
// Can never deduce foo()
We have a few options for debug. One is to use a combo of openocd
and gdb
. The other is to use probe-rs
's cargo embed
.
These examples use this project template for reference: https://github.com/rp-rs/rp2040-project-template
Debugging works best with opt-level = 0
for [profile.dev]
in Cargo.toml
, otherwise we're limited in where we can set breakpoints, and there is some other unexpected behavior.
This requires a debug probe. There are many options, but a simple one is to just flash probe fw onto another rp2040. Note that the fw link there is not the latest release.
We're using a UPS to ensure the NAS cleanly shuts down upon power loss, otherwise there could be data loss, corruption, and HDD damage. I recently replaced the old and broken battery in the UPS and re-configured it with some better settings. Here are the setup notes:
UPS model:
cyber power EC650LCD