sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Missing `icudtl.dat`
Labels: waiting for customer response,in triage

### Steps to reproduce

1. Install flutter on an arm64 linux device (specifically using `apk` on PostmarketOS)
2. `flutter run` (for my example i used https://github.com/henry-hiles/brook)

### Actual results

A error occurs (see logs)

### Logs

<details open>
<summary>Logs</summary>

```console
Launching lib/main.dart on Linux in debug mode...
Building Linux application...                                   
ninja: entering directory 'build/linux/arm64/debug'
CMake Error at cmake_install.cmake:88 (file):
  file INSTALL cannot find
  "/home/quadradical/Documents/Code/brook/linux/flutter/ephemeral/icudtl.dat":
  No such file or directory.


ninja: job failed: cd /home/quadradical/Documents/Code/brook/build/linux/arm64/debug && /usr/bin/cmake -P cmake_install.cmake
ninja: subcommand failed
Error: Build process failed

```

</details>


### Flutter Doctor output

<details open>
<summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.0, on postmarketOS edge 6.13.0-rc2-sdm845, locale C)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/to/linux-android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (not installed)
[✓] Connected device (1 available)
[✓] Network resources

! Doctor found issues in 3 categories.
```

</details>
Repository: godot
Issue: Cannot select first character of a wrapped line in RichTextLabel
Labels: bug,topic:gui

### Tested versions

- Reproducible in v4.3.stable.official.77dcf97d8

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 32.0.15.6094) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)

### Issue description

https://github.com/user-attachments/assets/fcc75f09-d32a-46f6-bc3b-059766613cdc

The first character of text on a wrapped line of RichTextLabel cannot be selected unless text from the preceding line is selected.

Starting in the middle of a wrapped line and selecting backwards, the selection stops just before the first character. Trying to select from the beginning of a wrapped line begins the selection from the second character.

Unwrapped lines function as expected, the issue only occurs on wrapped lines.

### Steps to reproduce

1. Create a RichTextLabel with text selection enabled.
2. Enter enough text to cause lines to wrap
3. Try to highlight the first character of a wrapped line.

### Minimal reproduction project (MRP)

[rtldemo.zip](https://github.com/user-attachments/files/18312961/rtldemo.zip)
Repository: godot
Issue: Viewport rotation gizmo can no longer have its current axis clicked to reverse it
Labels: bug,topic:editor,usability,regression,topic:3d

- *Related to https://github.com/godotengine/godot-proposals/discussions/11497.*

### Tested versions

- Reproducible in: 4.3.stable
- Not reproducible in: 3.6.stable

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (NVIDIA; 32.0.15.6636) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

In 4.3, nothing happens when clicking the axis that is currently viewed frontally:

https://github.com/user-attachments/assets/b5228504-b6d3-44d2-88fd-f5f6f38efe20

In 3.6, clicking it reverses it (e.g. you'll see X- instead of X+).

As a workaround, you can click the axis next to it twice, but this is less convenient and doesn't match Blender behavior.

### Steps to reproduce

- Click on the rotation gizmo to view an axis frontally.
- Click it again, and notice that nothing happens (it should get reversed instead, i.e. you view the same axis from behind).

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: export vscode glob implementation library
Labels: feature-request

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
It's very useful to do some filters with include and exclude options when I do search/replace in vscode.
![Image](https://github.com/user-attachments/assets/c7496956-bae4-45e8-88b1-4f31d0a687aa)

And I want to develop a extension and I hope my extension has same behavior when do some filter to files like below .
```typescript
...
function filter(links: vscode.Location[], include: string, exclude: string): vscode.Location[] {
	return links.filter(item => {
		let includeMatch = true;
		if (include && include !== '') {
			match = glob.match(include, item.uri.toString());
		}
		let excludeMatch = true;
		if (exclude && exclude !== '') {
			excludeMatch = !glob.match(exclude, item.uri.toString());
		}
		return includeMatch && excludeMatch;
	});
}
....
```


And I found the (vscode glob pattern document)[https://code.visualstudio.com/docs/editor/glob-patterns], it seems that vscode implement its glob pattern, and doesn't exported in its [api](https://github.com/microsoft/vscode/blob/main/src/vscode-dts/vscode.d.ts)? (or I don't find it)

So, could vscode export its glob api, and the extensions can behave same with the vscode.
Repository: deno
Issue: deno check. RangeError: Maximum call stack size exceeded
Labels: needs info,tsc

Version: Deno 2.1.4

I'm trying to type check a file with `deno check --config=web.jsonc ./src/index.tsx`. After a short delay the following error is thrown

```
error: Uncaught RangeError: Maximum call stack size exceeded
    at resolveNameHelper (ext:deno_tsc/00_typescript.js:1:1)
    at resolveEntityName (ext:deno_tsc/00_typescript.js:1:1)
    at trackExistingEntityName (ext:deno_tsc/00_typescript.js:1:1)
    at tryVisitTypeQuery (ext:deno_tsc/00_typescript.js:1:1)
    at visitExistingNodeTreeSymbolsWorker (ext:deno_tsc/00_typescript.js:1:1)
    at visitExistingNodeTreeSymbols (ext:deno_tsc/00_typescript.js:1:1)
    at visitNode (ext:deno_tsc/00_typescript.js:1:1)
    at tryReuseExistingTypeNodeHelper (ext:deno_tsc/00_typescript.js:1:1)
    at tryReuseExistingNonParameterTypeNode (ext:deno_tsc/00_typescript.js:1:1)
    at createAnonymousTypeNode (ext:deno_tsc/00_typescript.js:1:1)
```

I'm working to make a minimum reproducible example, but that may take a while. In the meantime, I suspect there's more information to be gathered than the above stacktrace - which might be enough to find the issue - but I'm happy to provide that. Funnily enough, I can `deno check` all the immediate dependencies of `./src/index.tsx` and it works as expected each time. According to `deno info ./src/index.tsx` There are 179 unique dependencies, 611.24KB of size, and all of the files are local. I'm using `https://deno.land/x/esbuild@v0.24.0/mod.js` to transpile to javascript, and the generated code runs in the browser fine.
Repository: three.js
Issue: SVGLoader - Transforms don't apply to styles of a path
Labels: Loaders

### Description

When a path is scaled down with a transform the SVGLoader doesnt also scale the styles such as stroke-width




### Reproduction steps

![svg](https://github.com/user-attachments/assets/ce524dcd-a16e-451c-be96-d33f11894d5c)

Take this svg and load it into the webgl_loader_svg example

it should appear like 
![Screenshot 2025-01-06 at 4 25 49 PM](https://github.com/user-attachments/assets/b7185bf3-1d61-4cf7-b0e7-996296b2f1be)

But actually appears like 
![Screenshot 2025-01-06 at 4 25 39 PM](https://github.com/user-attachments/assets/6f1aa660-a226-42a1-b267-35c2661e1fcc)


As you can see the circle on the left is too thick

### Code

Save the first svg from the repro steps into `models/svg/svg.svg`
add `'svg': 'models/svg/svg.svg'` into the `webgl_loader_svg` example file



### Live example

N/A

### Screenshots

_No response_

### Version

0.152.2

### Device

_No response_

### Browser

Chrome

### OS

MacOS
Repository: angular
Issue: Unclear Refer to locales by ID and extract-i18n error message
Labels: area: i18n

### Describe the problem that you experienced

In the page https://angular.dev/guide/i18n/locale-id their is a table with French | France | fr-FR.

The link in
The [Angular repository](https://github.com/angular/angular/tree/main/packages/common/locales) includes common locales.
it is not obvious, where to look for the common locales.

But according to 
.../node_modules/@angular/common/locales/global/*.js
"fr-FR", "de-DE", "en-US",... is not a common locales.

The warning (during the build)
Locale data for 'fr-FR' cannot be found. Using locale data for 'fr'.
Is may either 
correct  than the documentation should use French | France | fr.
or it's misleading - it's a (red) warning - than the the documentation should mention this, (and it's more likely a issue for the toolkit)
or I'm missing something.

In the page https://angular.dev/guide/i18n/locale-id
"By default, Angular uses en-US as the source locale of your project."
differs from https://github.com/angular/angular/blob/main/packages/common/locales/generate-locales-tool/README.md
"A default locale used within @angular/core. This is the locale_en.ts file."
So locale_fr-FR.ts, locale_en-US.ts, ... does not exists, because of the later mentioned optimization.

IMHO: The warning while build is misleading and the documentation should explain the this..


### Enter the URL of the topic with the problem

https://angular.dev/guide/i18n/locale-id
Repository: transformers
Issue: Trainer: Use second last checkpoint if last checkpoint loading fails
Labels: Feature request

### Feature request

Currently, the checkpoint is saved in the [`_save_checkpoint()`](https://github.com/huggingface/transformers/blob/b2f2977533445c4f62bf58e10b1360e6856e78ce/src/transformers/trainer.py#L3197) method which saves the model, optimizer (optionally) and finally the Trainer state.

The [`resume_from_checkpoint()`](https://github.com/huggingface/transformers/blob/b2f2977533445c4f62bf58e10b1360e6856e78ce/src/transformers/trainer.py#L2070) function gets the checkpoint directory from the `get_last_checkpoint` function. Then, the model etc. are loaded using the `self._load_from_checkpoint()` function and trainer state is loaded using the `TrainerState.load_from_json` call. 

If training program ended abruptly in the middle of checkpointing, the directory is created but some of the files are missing. For ex. if the trainer state was not yet written, this throws an error during the `TrainerState.load_from_json` call and training is not able to resume at all.

Proposal: If either loading model or trainer state fails (in `resume_from_checkpoint()`) since the last directory is incomplete, then use the second last checkpoint folder for resuming.


### Motivation

Motivation: Currently, our job can be killed in the middle of checkpointing and is not able to resume since last checkpoint is incomplete. We need to manually delete the folder to resume from previous checkpoint. 

Some info (not sure if relevant): I use accelerate launch to launch the training. 

### Your contribution

I am willing to submit a PR for this if this feature seems acceptable.

~~We would need to wrap the 2 loads in a try/catch block and if either of them fail, re-run using the second last directory.~~
Looks like there are a lot of places where `load_from_checkpoint` is done, with exceptions for FSDP etc. which would complicate things. Maybe we can have a list of expected files and check for existence else load second last dir.
Repository: ant-design
Issue: Color picker presets support gradients
Labels: unconfirmed

目前 `5.22.7` 颜色选择器 presets 好像只支持当个颜色，是否可以考虑支持渐变色的预设？

如图：

<img width="750" alt="image" src="https://github.com/user-attachments/assets/1e09d9ef-0bd4-4cae-8ae9-fa290128a003" />



<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: fetch requests not cached between generateMetadata and page component as per docs
Labels: Metadata

### Link to the code that reproduces this issue

https://github.com/steveharrison/nextjs-fetch-caching

### To Reproduce

1. Run the demo server: `npm run server` and `npm run start`. It will start a server on port 9000.
2. Run the NextJS project: `cd nextjs-project` and `npm run dev`.
3. Load the NextJS project root page once (probably http://localhost:3000)
4. Refresh the page

Side note: If you skip step 4, I only get one 200 GET request logged on initial page load, although the Next.js logs say two cache misses, whereas I'd expect one cache hit given only one GET request was received?

``` GET / 200 in 1021ms
 │ GET http://localhost:9000/index.html 200 in 90ms (cache skip)
 │ │ Cache skipped reason: (auto no cache)
 │ GET http://localhost:9000/index.html 200 in 56ms (cache skip)
 │ │ Cache skipped reason: (auto no cache)
```


### Current vs. Expected behavior

Current behaviour: 2 requests get made to the demo server.
Expected behaviour: 1 request gets made to the demo server, as the documentation at https://nextjs.org/docs/app/building-your-application/caching#data-cache says that fetch requests get cached between generateMetadata and page components. I noticed that `cache` is manually used in this example: https://github.com/vercel/next.js/issues/62162, but the docs suggest this is not necessary.

I have disabled strict mode as well, in case duplicates were coming from that.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Nov 15 18:56:27 PST 2024; root:xnu-11215.61.2.501.1~1/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 21.7.1
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: 9.2.0
Relevant Packages:
  next: 14.2.10
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Not sure, Documentation, Metadata

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

next dev (local)

### Additional context

_No response_
Repository: electron
Issue: Wrong web browser opened when clicking links
Labels: platform/linux,bug :beetle:,has-repro-gist,33-x-y,34-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

33.3.0

### What operating system(s) are you using?

Ubuntu

### Operating System Version

24.04

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Links open in the configured default browser

### Actual Behavior

Links open in Chrome/Chromium instead, regardless of the configured default browser

### Testcase Gist URL

https://gist.github.com/Viicos/d77af018be1b7b27294a74c378731992

### Additional Information

This is a re-open of https://github.com/electron/electron/issues/42611 (by @bittylicious) after @viicos was so kind to add a repro gist (adding a gist was an absolute requirement by the Electron team on the original issue).

The original issue already well pointed out that this issue seems to be new with Ubuntu 24 and wasn't present on 22.

Workarounds presented in in the original issue:

* Uninstalling all chrome/chromium (then e.g. a firefox will be correctly opened)
* Adding the following to `~/.local/share/applications/mimeapps.list`

```
[Default Applications]
x-scheme-handler/http=firefox_firefox.desktop
x-scheme-handler/https=firefox_firefox.desktop
```

There are some additional details available in the original issue.
Repository: go
Issue: runtime: async preemption (or alternative) for wasm
Labels: NeedsDecision,arch-wasm,compiler/runtime

This is split from #65178, as the specific scheduler bug was fixed.

Due to its single-threaded nature, js/wasm have no sysmon thread, and thus no asynchronous preemption. Thus the pitfalls of Go prior to asynchronous preemption apply: tight loops that fail to yield may delay scheduling indefinitely.

This is a tracking issue for problems due to the lack of asynchronous preemption. As noted in #36365, due to the lack of threading, asynchronous preemption isn't possible today, but perhaps could be with wasm threads? Or we could have an alternative scheme for js/wasm (such as adding preemption points to loops).

(Plan9 is also missing async preemption, but that simply needs an implementation)
Repository: deno
Issue: ext/node: `assert.deepStrictEqual({}, Object.create(null))` should throw
Labels: bug,node compat

The following script throws in Node, but not in Deno:

```js
import assert from "node:assert"
assert.deepStrictEqual({}, Object.create(null))
```
Repository: rust
Issue: "This generic parameter must be used with a generic lifetime parameter" on RPIT with precise capturing
Labels: T-compiler,A-impl-trait,C-bug,S-has-mcve,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
struct Foo<'a> {
    children: Vec<&'a Foo<'a>>,
}

struct Bar;

impl<'a> Foo<'a> {
    fn failing<'p>(&'a self, param: &'p Bar) -> impl Iterator<Item = String> + use<'a, 'p> {
        self.children.iter().flat_map(|child| child.failing(param))
    }
}
```

I expected to see this happen:
the code compiles, since `param` gets used by all the `children`

_Or_, if the code actually violates ownership rules, get a clearer error message.

Instead, this happened:
compiler complains with "This generic parameter must be used with a generic lifetime parameter"

I've tried the following solutions:
1. use an anonymous lifetime instead of `'p`, like this:
```rust
fn failing(&'a self, param: &Bar) -> impl Iterator<Item = String> + use<'a, '_> { /* ... */ }
```
2. make the two lifetimes the same:
```rust
fn failing(&'a self, param: &'a Bar) -> impl Iterator<Item = String> + use<'a> { /* ... */ }
```
And still got the same bizarre error.


### Meta
```
rustc 1.82.0 (f6e511eec 2024-10-15) (built from a source tarball)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 18.1.8
```

also present on latest stable (1.83.0), beta (1.84.0-beta.6), and nightly (2025-01-05)

<details><summary>Backtrace</summary>
<p>

```
error[E0792]: expected generic lifetime parameter, found `'_`
   --> src/tree.rs:656:9
    |
655 |     fn failing<'p>(&'a self, param: &'p Bar) -> impl Iterator<Item = String> + use<'a, 'p> {
    |                                                                                    -- this generic parameter must be used with a generic lifetime parameter
656 |         self.children.iter().flat_map(|child| child.failing(param))
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```

</p>
</details>
Repository: vscode
Issue: Feature Proposal for Enhanced Collaborative Programming in VSCode
Labels: feature-request

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
1. Live Pair Debugging
Building on the current Live Share functionality, I propose adding a Live Pair Debugging feature. This would allow two or more collaborators to debug code together in real-time. Key functionalities could include:

Synchronized breakpoints, so all participants can view and control them.
Shared debugging sessions where participants can see variable states, stack traces, and logs simultaneously.
Optional permissions for the session host to manage who can make changes during the debugging process.
2. Code Review Inline Chat
This feature would enable inline discussions directly in the code editor. Collaborators could comment on specific lines or blocks of code, and these comments would appear as contextual notes within the editor. Key features could include:

A real-time chat thread embedded in the editor for each commented code block.
Notifications for new comments or replies during collaborative sessions.
Integration with Git or other version control systems to track comments across commits.
Benefits of These Features
Improves the efficiency of pair programming and team debugging.
Streamlines code review processes, making them faster and more interactive.
Encourages better communication and knowledge sharing within teams.
I believe these enhancements would significantly improve the collaborative programming experience in VSCode, particularly for remote and distributed teams.

Thank you for considering this suggestion. I’d be happy to discuss or elaborate further if needed.

Best regards,
[janeblue]
Repository: vscode
Issue: [themes] provide alternate color selections
Labels: feature-request,themes

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
I would really like if there was a way to switch between color sets within a single theme. You could make multiple themes, of course, but if you just want to give the user more options for something small like bracket colors, then it seems a bit inefficient and confusing to upload the same theme with small changes.
In short, Allow the user to switch between color sets within a color theme.

For example, the user could choose between bracket colorizations:
1. Blue brackets (default)
2. Red brackets
3. Green brackets
4. Red, blue, & green brackets
Repository: flutter
Issue: Photo Captured Using Flutter Camera Plugin (camera: ^0.11.0+2) Appears Tilted on some devices(Redmi Note 8 Pro, samsung A9, Pixel 8a)
Labels: e: device-specific,platform-android,p: camera,package,P1,team-android,triaged-android

![surajimagetiled](https://github.com/user-attachments/assets/473d3105-8590-42f5-b79c-9d3b122dab06)
Repository: neovim
Issue: neovim prints key release event characters after exiting in kitten ssh session
Labels: bug,tui,input

### Problem

 When exiting neovim in a remote kitten ssh session, sometimes the characters "3;1:3u" shows in terminal.

More information can be found at https://github.com/kovidgoyal/kitty/issues/8200

Not sure if https://github.com/neovim/neovim/pull/31727 is related?

### Steps to reproduce

1.  ssh to a remote machine using kitten ssh
2. start nvim nvim -u NONE
3. exit nvim
4. See the sequence "3;1:3u" (the key release event sequence)


### Expected behavior

No characters are printed

### Nvim version (nvim -v)

NVIM v0.11.0-dev-1465+ga09c7a5d57

### Vim (not Nvim) behaves the same?

no, vim 8.2.2121

### Operating system/version

Ubuntu 22.04.3 LTS

### Terminal name/version

kitty 0.38.1 (d23adce11c) created by Kovid Goyal

### $TERM environment variable

xterm-kitty

### Installation

Nightly releases