sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Typescript gets confused when renaming by only changing filename case of imported file on Windows
Labels: Bug

### 🔎 Search Terms

windows rename already included

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
- I was unable to test this on prior versions because _______


### ⏯ Playground Link

_No response_

### 💻 Code

file `src/vector.js`
```js
export default class Vector {}
```

file `test/vector.test.js`
```js
import Vector from '../src/vector.js'
new Vector();
```


now rename the file
```sh
mv src/vector.js src/Vector.js
```
and update the file `test/vector.test.js`
```js
import '../src/Vector.js'
new Vector();
```


### 🙁 Actual behavior

There is an error message:
![Image](https://github.com/user-attachments/assets/419a8eb6-1f2c-472b-91c9-98f572c97d4d)


### 🙂 Expected behavior

No error message, as the imported file name matches the actual file name.

### Additional information about the issue

`tsconfig.json`
```json
{
    "compilerOptions": {
      "target": "ES2017",
      "module": "commonjs",
      "lib": ["es2017", "dom", "DOM.Iterable"],
      "allowJs": true,
      "checkJs": true,
      "skipLibCheck": true,
      "declaration": true,
      "noEmit": true,
      "strict": true,
      "baseUrl": ".",
      "typeRoots": [
        "./node_modules/@types",
      ],
      "esModuleInterop": true
    },
    "include": [
      "src/**/*.js",
      "test/**/*.js",
    ]
}
```
Repository: rust
Issue: Cannot use unicode identifiers in `--extern` flags
Labels: A-metadata,A-Unicode,T-compiler,C-feature-request,A-crates

I tried this code:

```console
> rustc --crate-name öwö --crate-type lib - <<<'pub fn öwö() {}'
> rustc --crate-name ūwū --crate-type bin --extern öwö=liböwö.rlib - <<<'fn main() { öwö::öwö(); }'
```

I expected to see this happen: successful compilation

Instead, this happened:

```
error: crate name `öwö` passed to `--extern` is not a valid ASCII identifier
```

### Meta
`rustc --version --verbose`:
```
rustc 1.85.0 (c44b3d50f 2024-12-03)
binary: rustc
commit-hash: c44b3d50fea96a3e0417e8264c16ea21a0a3fca2
commit-date: 2024-12-03
host: x86_64-unknown-linux-gnu
release: 1.85.0
LLVM version: 19.1.4
```
Repository: PowerToys
Issue: Specific key remapping not working
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

![Image](https://github.com/user-attachments/assets/1c4a5d7b-4ab6-4aa4-8375-43e0e74a8d7b)


### ✔️ Expected Behavior

Remapping a key to sent this shortcut:
Browser favorite button on keyboard --> CTRL (left) + ALT (left) + Home

### ❌ Actual Behavior

The command is not registered and doesn't work when hitting the remapped key.
Hitting the physical keys works instead:
CTRL (left) + ALT (left) + Home

### Other Software

This shortcut is useful when running a RDP session on full screen, to move the focus to the host machine instead of the remote session, and hit afterwards different shortcuts which will take action on the host.
Repository: vscode
Issue: VSCode shows a loading spinner on pasting anything
Labels: info-needed,typescript


Type: <b>Bug</b>

This doesn't reproduce all the time. It happens randomly. I disabled extensions using start extension bisect and it's still happening. There's a related old issue that got closed #210540

VS Code version: Code - Insiders 1.97.0-insider (b425f4802fcbcccb11ad991208fa262c06255be3, 2024-12-13T05:04:19.453Z)
OS version: Windows_NT x64 10.0.22635
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-12700F (20 x 2112)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.84GB (6.37GB free)|
|Process Argv|--folder-uri file:///d%3A/TEC/Spartans --crash-reporter-id 2a515175-97ab-457e-94e2-d5dadae50b98|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (38)</summary>

Extension|Author (truncated)|Version
---|---|---
markdown-mermaid|bie|1.27.0
vscode-tailwindcss|bra|0.12.16
npm-intellisense|chr|1.4.5
path-intellisense|chr|2.10.0
vscode-eslint|dba|3.0.10
gitlens|eam|2024.12.1304
prettier-vscode|esb|11.0.0
vscode-expo-tools|exp|1.5.0
codespaces|Git|1.17.3
copilot|Git|1.251.1262
copilot-chat|Git|0.24.2024121301
remotehub|Git|0.65.2024112101
vscode-pull-request-github|Git|0.103.2024121117
go|gol|0.42.1
todo-tree|Gru|0.0.226
i18n-ally|lok|2.12.0
dotenv|mik|1.0.1
python|ms-|2024.23.2024121201
vscode-pylance|ms-|2024.12.1
jupyter|ms-|2025.1.2024121301
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
remote-ssh|ms-|0.116.0
remote-ssh-edit|ms-|0.87.0
remote-wsl|ms-|0.88.5
remote-explorer|ms-|0.4.3
remote-repositories|ms-|0.43.2024112101
material-icon-theme|PKi|5.15.0
vscode-yaml|red|1.15.0
rust-analyzer|rus|0.3.2212
code-spell-checker|str|4.0.21
even-better-toml|tam|0.19.2
vscode-mdx|uni|1.8.11
explorer|vit|1.8.3
vscode-wakatime|Wak|24.9.2
markdown-all-in-one|yzh|3.6.2

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vsc_aacf:30263846
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
2i9eh265:30646982
962ge761:30841072
pythonnoceb:30776497
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dvdeprecation:31040973
dwnewjupytercf:31046870
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
cf971741:31144450
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
2j25a237:31183119
5b1c1929:31184661

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: `torch.linalg.qr_ex` and `torch.linalg.lstsq_ex`
Labels: triaged,enhancement,module: linear algebra

### 🚀 The feature, motivation and pitch

PyTorch already includes multiple linear algebra functions that return the `info` error code from the underlying LAPACK call: [`torch.linalg.cholesky_ex`](https://pytorch.org/docs/stable/generated/torch.linalg.cholesky_ex.html), [`torch.linalg.solve_ex`](https://pytorch.org/docs/stable/generated/torch.linalg.solve_ex.html) and [`torch.linalg.ldl_factor_ex`](https://pytorch.org/docs/stable/generated/torch.linalg.ldl_factor_ex.html#torch.linalg.ldl_factor_ex).

The motivation behind this feature request aligns with one of the motivations that I believe led to exposing the previous functions: a fast and clean way to handle decomposition errors during the function call.

### Alternatives

To my knowledge, there is currently no workaround to handle decomposition errors from [`torch.linalg.qr`]() and [`torch.linalg.lstsq`](https://pytorch.org/docs/stable/generated/torch.linalg.lstsq.html). 

As noted in the [docs](https://pytorch.org/docs/stable/generated/torch.linalg.qr.html#:~:text=The%20QR%20decomposition%20is%20only%20well%2Ddefined%20if%20the%20first%20k%20%3D%20min(m%2C%20n)%20columns%20of%20every%20matrix%20in%20A%20are%20linearly%20independent.%20If%20this%20condition%20is%20not%20met%2C%20no%20error%20will%20be%20thrown%2C%20but%20the%20QR%20produced%20may%20be%20incorrect%20and%20its%20autodiff%20may%20fail%20or%20produce%20incorrect%20results.), `torch.linalg.qr` fails silently, and `torch.linalg.lstsq` also may fail silently despite what is mentioned in the [docs](https://pytorch.org/docs/stable/generated/torch.linalg.lstsq.html#:~:text=residuals%3A%20the%20squared,future%20PyTorch%20release):
> *residuals*: the squared residuals of the solutions, that is, $\lVert AX - B\rVert_{F}^{2}$. It has shape equal to the batch dimensions of $A$. It is computed when $m > n$ and every matrix in $A$ is full-rank, **otherwise, it is an empty tensor**. If $A$ is a batch of matrices and any matrix in the batch is not full rank, **then an empty tensor is returned**. This behavior may change in a future PyTorch release

Example:
```python
B, N, D = 20, 10, 3
dev = torch.device("cuda")
a = torch.rand(B, N, D, device=dev)
a[..., 0] = a[..., 1] # force rank deficient matrix
assert (torch.linalg.matrix_rank(a) < D).any(-1)
b = torch.rand(B, N, device=dev)
sol = torch.linalg.lstsq(a, b)
print(f"Empty residuals: {sol.residuals.numel()==0}. Shape: {sol.residuals.shape}")
```


### Additional context

_No response_

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: excalidraw
Issue: Option to Lock Sizes within a Group
Labels: enhancement

Currently, when a group of items is scaled, all items inside the group are scaled proportionally. There is no feature to lock the dimensions of specific items within the group.

Feature Request:
Add an option to lock the dimensions of individual items in a group so they remain unchanged during group scaling. This would provide more flexibility when working with grouped elements, especially when certain items need to maintain their original size.
Repository: react
Issue: [React 19] `renderToString`'s output missing some rendered elements
Labels: React 19

## Summary

The bug can be seen on [stackblitz](https://stackblitz.com/edit/stackblitz-starters-a7nkhwt8?description=Starter%20project%20for%20Node.js,%20a%20JavaScript%20runtime%20built%20on%20Chrome%27s%20V8%20JavaScript%20engine&file=index.js&title=node.new%20Starter). 

It looks like some timing issue so reproducing might require a few runs. However, I'm able to repro this each time - the problem is that different elements are missing each~ time. 

An example excerpt from the logged output:
```html
<div class="some-key-ervrair" data-id="101">woah there<span>hello world</span><div class="some-key-4a2dabr" data-id="100">woah there<span>hello world</span>woah there<span>hello world</span><div class="some-key-9nbpw7" data-id="97">woah there<span>hello world</span><div class="some-key-ta4dr8b" data-id="96">woah there<span>hello world</span>
```

We can see here that it skips over 99 and 98 elements, going straight from 100 to 97. 

The code used on stackblitz:
```js
const renderToString = require('react-dom/server').renderToString;
const jsx = require('react').createElement;

const BigComponent = ({ count } /*: { count: number } */) => {
  if (count === 0) return null;

  const start = Date.now();
  while (true) {
    if (Date.now() - start > 5) {
      break;
    }
  }

  return jsx(
    'div',
    {
      className: `some-key-${Math.random().toString(36).slice(6)}`,
      'data-id': count,
    },
    'woah there',
    jsx('span', {}, 'hello world'),
    jsx(BigComponent, { count: count - 1 })
  );
};

console.log(renderToString(jsx(BigComponent, { count: 200 })));
```
Repository: react-native
Issue: 0.75.4 - Android 15 for StatusBarModule (EdgeToEdge)
Labels: Platform: Android,Component: StatusBar,Needs: Author Feedback,Needs: Repro

### Description

Your app uses deprecated APIs or parameters for end-to-end display

One or more APIs you use or parameters you set for end-to-end screen and window display have been discontinued in Android 15. Your application uses the following deprecated APIs or parameters:

android.view.Window.getStatusBarColor
android.view.Window.setStatusBarColor

These start from:

com.facebook.react.modules.statusbar.StatusBarModule$setColor$1.runGuarded
com.facebook.react.modules.statusbar.StatusBarModule.getTypedExportedConstants

https://developer.android.com/about/versions/15/behavior-changes-15?hl=tr#edge-to-edge


### React Native Version

0.75.4

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: Windows 10 10.0.19045
  CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
  Memory: 15.45 GB / 31.96 GB
Binaries:
  Node:
    version: 22.9.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 10.9.1
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "31"
      - "35"
    Build Tools:
      - 34.0.0
      - 35.0.0
    System Images:
      - android-24 | Google Play Intel x86 Atom
      - android-26 | Google APIs Intel x86 Atom
      - android-27 | Intel x86 Atom
      - android-27 | Google APIs Intel x86 Atom
      - android-27 | Google Play Intel x86 Atom
      - android-28 | Google Play Intel x86 Atom
      - android-34 | Google Play Intel x86_64 Atom
      - android-35 | Google Play Intel x86_64 Atom
      - android-35 | Pre-Release 16 KB Page Size Google Play ARM Intel x86_64
        Atom
    Android NDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-242.23339.11.2421.12700392
  Visual Studio: Not Found
Languages:
  Java: 17.0.9
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```
![2024-12-17_09-50-22](https://github.com/user-attachments/assets/de623853-85ac-4435-af04-932b0d3f70ef)
Repository: godot
Issue: Godot 4.3 crashes when trying to open AssetLib
Labels: bug,topic:editor,crash

### Tested versions

Reproducible in: 
Godot v4.3.stable from godotengine.org

Not reproduced in: 
Godot v4.3.stable (77dcf97d8) - Freedesktop SDK 24.08 (Flatpak runtime) - Wayland - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) - 12th Gen Intel(R) Core(TM) i7-12700H (20 Threads)

### System information

Godot v4.3.stable - TUXEDO OS 3 22.04.5 - Wayland - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 Ti Laptop GPU - 12th Gen Intel(R) Core(TM) i7-12700H (20 Threads)

### Issue description

When trying to access AssetLib, Godot crashes. It did not crash until I clicked "Go online". After this, it will always close the program every time I access it, whether it is from inside a project or from the project overview.

The Flatpak-version does not reproduce this issue. I can't use this however, as I am unable to get my discrete GPU to be recognized and it instead uses the integrated Intel-chip.

### Steps to reproduce

1. Open Godot v4.3.stable
2. Click on AssetLib from either inside a project or from the project overview.
3. Click "Go online"
4. Godot crashes

### Minimal reproduction project (MRP)

It is project independent.
Repository: godot
Issue: ctrl+f in editor has delay before switching, in which key presses can be captured by the code window
Labels: bug,topic:editor,usability,topic:input

### Tested versions

v4.3.stable.official [77dcf97d8]


### System information

windows 11 (also present on earlier)

### Issue description

When pressing ctrl+f to search in the editor, there is sometimes a delay before the focus switches, so some characters are typed into the code window instead of the search bar.

### Steps to reproduce

* type in code editor
* press ctrl+f, and immediately start typing a query
* sometimes there's a brief delay, and the first several characters of the search query are entered into code editor instead
* the rest of the characters appear in the search field

### Minimal reproduction project (MRP)

any text file in editor
Repository: flutter
Issue: Update the DeviceLab README.md with updated warnings and info on how to run tests on a local machine
Labels: framework,P2,team-framework,triaged-framework,d: docs/

### Use case

### Use case: Engineers get up-to-date information from the DeviceLab readme

The https://github.com/flutter/flutter/blob/master/dev/devicelab/README.md file explains how to run DeviceLab tests locally. But it omits some important details that differ from the usual behaviour of running tests engineers are familiar with:

1. By default, the failing tests are autoretried. It makes sense to mention this as it is likely any engineer running the tests locally does not want that behaviour and wants to disable it.
2. The DeviceLab test runner automatically reboots the Android and iOS devices it runs tests on. While this behaviour currently can't be disabled, it still makes sense to tell engineers about it, as otherwise, devices (seemingly) randomly restarting looks like a serious bug.

As an engineer, it would be very useful to have these things mentioned in the documentation.

### Proposal

### Proposal: Update the DeviceLab readme

Update the DeviceLab Readme at https://github.com/flutter/flutter/blob/master/dev/devicelab/README.md and add a warning about reboots and a small section about disabling the automatic retries for failed tests.
Repository: storybook
Issue: [Bug]: global decorator are not updated in composed storybook
Labels: bug,needs triage

### Describe the bug

Adding [project level modes](https://www.chromatic.com/docs/modes/#project-level-modes) to let the user switch between light and dark mode works pretty well in a single storybook package.
When the user clicks the light/dark mode button, the content is re-rendered in the expected theme.

In a [package composition](https://storybook.js.org/docs/sharing/package-composition) however, the same is not true.
Clicking the button will update [the decorator](https://storybook.js.org/docs/writing-stories/decorators#global-decorators) in the URL (address bar), but the attribute in HTML remains unchanged.
The user has the refresh/reload the page (F5) in order to see the story in the expected theme.

### Reproduction link

https://stackblitz.com/edit/github-nk6zbbmz?file=.storybook-composed%2Fmain.js

### Reproduction steps

1. Got to the above link
2. Start the composited storybook: `yarn storybook`
3. Navigate to the composited storybook running on port 6006
4. Open the top Button Docs and switch between light and dark theme. It works
5. Open the bottom (under composite) Button Docs and switch between light and dark theme. Nothing happens unless you refresh the page.
> [!NOTE]
> Switching between light and dark mode in the composited stories directly under port 6007 works as expected

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.5.0-alpha.21 => 8.5.0-alpha.21 
    @storybook/addon-themes: 8.5.0-alpha.21 => 8.5.0-alpha.21 
    @storybook/blocks: ^8.5.0-alpha.21 => 8.5.0-alpha.21 
    @storybook/test: ^8.5.0-alpha.21 => 8.5.0-alpha.21 
    @storybook/web-components: ^8.5.0-alpha.21 => 8.5.0-alpha.21 
    @storybook/web-components-vite: ^8.5.0-alpha.21 => 8.5.0-alpha.21 
    storybook: ^8.5.0-alpha.21 => 8.5.0-alpha.21
```

### Additional context

_No response_
Repository: bitcoin
Issue: build: compiler flags in linker flags output
Labels: Build system

This is confusing / undermines the output printed, so it'd be good if it could be improved, or fixed entirely.

Seeing:
```bash
Linker flags .......................... <a bunch of compiler flags> i.e `-ftrivial-auto-var-init=pattern`
```
just doesn't make sense.
Repository: next.js
Issue: Cannot enable incremental PPR in a page file that is marked with 'use cache'
Labels: Partial Prerendering (PPR),dynamicIO

### Link to the code that reproduces this issue

https://github.com/focux/dynamicio-with-inc-ppr-repro

### To Reproduce

1. Start the app
2. Run `npm run build`

### Current vs. Expected behavior

When you try to build the app, it throws this error:
```
Error:   x Only async functions are allowed to be exported in a "use cache" file.

 | export const experimental_ppr = true;
```

I would expect the `use cache` directive to work with incremental PPR. It currently work when `ppr: true` and not incremental.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.22
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.1-canary.2 // Latest available version is detected (15.1.1-canary.2).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

dynamicIO, Partial Prerendering (PPR)

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: deno
Issue: Auto-merge lockfile conflicts
Labels: cli,suggestion

pnpm, npm (and maybe yarn?) all support merging lockfile conflicts automatically. Hand-merging deno lockfiles is a pain, because it sometimes includes versions and peers, and sometimes doesn't. I know I can just delete it, but that makes an unclean merge. I quite often corrupt the lockfile and have to restart, but it's feasible to be able to do it automatically.
Repository: go
Issue: proposal: crypto/x509: support for RFC 9336 Document Signing EKU
Labels: Proposal,Proposal-Crypto

### Proposal Details

RFC 9336 specifies a new EKU for document signing, allowing for a separate and distinct EKU from either code signing or smime email signing.  That document explains the reason for the new EKU.

Form a golang perspective, this requires entries in three tables in src/crypto/x509/x509.go for  id-kp-documentSigning, or OID 1.3.6.1.5.5.7.3.36.
Repository: bitcoin
Issue: cmake inconsistently overriding `-O3` (sometimes)
Labels: Build system

Using master @ d73f37dda221835b5109ede1b84db2dc7c4b74a1.

The following seems incorrect, because 
```bash
make -C depends/ NO_QT=1 NO_WALLET=1 NO_ZMQ=1 -j18 CFLAGS="-O3" CXXFLAGS="-O3"
cmake -B build --toolchain /root/ci_scratch/depends/aarch64-unknown-linux-gnu/toolchain.cmake
<snip>
C++ compiler flags .................... -O3 -O2 -g
Linker flags .......................... -O3 -O2 -g
```
is overriding the user-provided `-O3`.

If you configure by providing an explicit `-DCMAKE_BUILD_TYPE=RelWithDebInfo`, you get:
```bash
cmake -B build --toolchain /root/ci_scratch/depends/aarch64-unknown-linux-gnu/toolchain.cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo
C++ compiler flags .................... -O3
Linker flags .......................... -O3
```

No `-O2` at all, so the user provided `-O3` is used (also missing `-g` for debug info?).

If you configure with `-DCMAKE_BUILD_TYPE=Release`:
```bash
cmake -B build --toolchain /root/ci_scratch/depends/aarch64-unknown-linux-gnu/toolchain.cmake -DCMAKE_BUILD_TYPE=Release
C++ compiler flags .................... -O3 -O2
Linker flags .......................... -O3 -O2
```

Now we are back to (inconsistently) overriding the user.