sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: GPU Delegate for Object detection and Image classification from Tensorflow lite for Android 
Labels: type:support,comp:lite,TFLiteGpuDelegate

I'm using Android Kotlin code for object detection and image classification 
https://github.com/tensorflow/examples/tree/master/lite/examples

var currentDelegate: Int = 1, 
 
 val optionsBuilder =
            ObjectDetector.ObjectDetectorOptions.builder()
                .setScoreThreshold(threshold)
                .setMaxResults(maxResults)

        // Set general detection options, including number of used threads
        val baseOptionsBuilder = BaseOptions.builder()

val compatList = CompatibilityList()
                if (compatList.isDelegateSupportedOnThisDevice) {
                    val delegateOptions = compatList.bestOptionsForThisDevice
                    baseOptionsBuilder.useGpu()
                    Utils.readLog(TAG, "Using GPU delegate with options: $delegateOptions")
                } else {
                    baseOptionsBuilder.setNumThreads(4)
                }
                
optionsBuilder.setBaseOptions(baseOptionsBuilder.build())

try {
            objectDetector =
                ObjectDetector.createFromFileAndOptions(
                    context,
                    modelName,
                    optionsBuilder.build()
                )
        } catch (e: IllegalStateException) {
            objectDetectorListener?.onError(
                "Object detector failed to initialize. See error logs for details"
            )
            Utils.readLog(TAG, " " + e.message)
        }
        

//Image Classification 
try {
            imageClassifier =
                ImageClassifier.createFromFileAndOptions(
                    context,
                    modelName,
                    optionsBuilder.build()
                )
        } catch (e: IllegalStateException) {
            imageClassifierListener?.onError(
                "Image classifier failed to initialize. See error logs for details"
            )
            Utils.readLog(TAG, "TFLite failed to load model with error: " + e.message)
        }
        
        
Here I'm Using above code baseOptionsBuilder using same for both object detection and image classification but if i'm using currentDelegate = 1 for both it is lagging a lot and object detection and image classification is not working with GPU. 

Is there anything else that i can use to make it work?
Repository: flutter
Issue: [Accessibility] : AlertDialog semanticLabel not read in iOS 18
Labels: platform-ios,a: accessibility,e: OS-version specific,has reproducible steps,P1,team-ios,triaged-ios,found in release: 3.27,found in release: 3.28

### Steps to reproduce

The semanticLabel of my AlertDialog is not read by VoiceOver in iOS 18. It's working well on iOS 17 and above, and on Android.
I'm facing the issue with Flutter 3.24 and 3.27

### Expected results

semanticLabel should be read when AlertDialog is focused

### Actual results

semanticLabel is not read when AlertDialog is focused

### Code sample

<details open><summary>Code sample</summary>

```dart
showDialog(
    useRootNavigator: true,
    barrierDismissible: false,
    context: context,
    builder: (dialogContext) {
      return AlertDialog(
        semanticLabel: "Alert !",
        title: Text("My tittle"),
        content: Text("My content"),
        actions: [TextButton(label: Text("OK"), onPressed: context.pop))]
        scrollable: true,
      );
    },
  );
```

</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.1, on macOS 15.1 24B83 darwin-x64, locale fr-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.4)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: ant-design
Issue: Modal 组件弹出和收起都会有抽搐屏幕闪烁的问题
Labels: unconfirmed

### Reproduction link

[https://ant-design.antgroup.com/components/modal-cn#modal-demo-confirm](https://ant-design.antgroup.com/components/modal-cn#modal-demo-confirm)

### Steps to reproduce

点击时 屏幕分辨率为：2560 * 1440 会发现以上描述的现象 但是在同等条件下 分辨率为：1920*1080屏幕下是正常无症状

### What is expected?

在2k的分辨率屏幕正常显示无闪烁

### What is actually happening?
[现象.zip](https://github.com/user-attachments/files/18297870/default.zip)


在2k的分辨率屏幕正常显示有闪烁

| Environment | Info |
| --- | --- |
| antd | 5.22.5 |
| React | 18 |
| System | windows |
| Browser | chrome 131.0.6778.205 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Missing `Send` on "recursive" `Future`
Labels: T-compiler,C-bug,A-async-await,needs-triage

Yesterday in the rust community discord, we came across the following (minimized) example.
I don't understand why these futures aren't `Send`. Obviously, `bar` can only be `Send` if `foo` is as well. However, while `bar` requires `foo` to be `Send` in order to successfully type-check, it's `Send`ness shouldn't depend on it.

I tried this code:
```rust
fn spawn<T: Send>(_: T) { }

async fn foo() {
    spawn(bar())
}

async fn bar() {
    foo().await;
}
```

I expected to see this happen: I believe the code should compile.

Instead, this happened:
```
error: future cannot be sent between threads safely
 --> <source>:4:5
  |
4 |     spawn(bar())
  |     ^^^^^^^^^^^^ future returned by `bar` is not `Send`
  |
  = note: cannot satisfy `impl Future<Output = ()>: Send`
note: future is not `Send` as it awaits another future which is not `Send`
 --> <source>:8:5
  |
8 |     foo().await;
  |     ^^^^^ await occurs here on type `impl Future<Output = ()>`, which is not `Send`
note: required by a bound in `spawn`
 --> <source>:1:13
  |
1 | fn spawn<T: Send>(_: T) { }
  |             ^^^^ required by this bound in `spawn`
```

### Meta
`rustc --version --verbose`:
```
rustc 1.85.0-nightly (4363f9b6f 2025-01-02)
binary: rustc
commit-hash: 4363f9b6f6d3656d94adbcabba6348a485ef9a56
commit-date: 2025-01-02
host: x86_64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.6
```
This also happens on stable `rustc 1.83.0`.
Before `rustc 1.75` the type checker encounters a cycle instead.
With `-Znext-solver` there's an ICE.
Repository: next.js
Issue: Next.js 15 `<Link>` scroll to top does not work if `loading.tsx` is present
Labels: Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/youthful-davinci-xs9gmf

### To Reproduce

1) Run the server in production mode (`npm run build && npm run start`).
2) Navigate to the "/withloading" page.
3) Scroll to the bottom and click the "Next" button.
4) The page does not scroll to the top.

### Current vs. Expected behavior

The page should scroll to the top when pressing the "Next" and "Previous" buttons on the "withloading" page, but it does not.


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 8198
  Available CPU cores: 4
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.1.1-canary.24 // Latest available version is detected (15.1.1-canary.24).
  eslint-config-next: N/A
  react: 19.0.0-beta-04b058868c-20240508
  react-dom: 19.0.0-beta-04b058868c-20240508
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next start (local)

### Additional context

This bug only occurs with `next start` and not with `next dev`. It is also present only in Next.js 15 and works fine in Next.js 14. As far as I know, it doesn't matter what is returned by `loading.tsx`, as returning anything at all will result in this bug.
Repository: ollama
Issue: Ollama - Gentoo Linux support 
Labels: feature request

Hello, world !

**Gentoo portage of Ollama**, binary release. 
RTX4060-i7 works perfectly !

[https://ftp.pingwho.org/pub/gentoo/ftp/overlay/pingwho-overlay/app-misc/ollama-bin/](https://ftp.pingwho.org/pub/gentoo/ftp/overlay/pingwho-overlay/app-misc/ollama-bin/)

Enjoy !
Repository: svelte
Issue: Cannot import TS types from Svelte components in `.svelte.ts files`
Labels: documentation,types / typescript

### Describe the bug

I cannot import types exported in a `<script module lang="ts">` block in a `.svelte.ts` file (I can import them in other .svelte files).

TS complains that: 
>TS2614: Module '".svelte"' has no exported member 'ListRecord'. Did you mean to use 'import ListRecord from ".svelte"' instead?

Indeed, importing from `"*.svelte"` does actually work, but my editor thinks it's an error (and it sure does look wrong).

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-umuyfhqp?file=src%2Froutes%2FOtherTest.svelte.ts

### Logs

_No response_

### System Info

```shell
System:
    OS: Linux 5.15 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
    Memory: 7.56 GB / 11.69 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 22.12.0 - /run/user/1000/fnm_multishells/1080_1735405309856/bin/node
    Yarn: 1.22.22 - /run/user/1000/fnm_multishells/1080_1735405309856/bin/yarn
    npm: 10.9.0 - /run/user/1000/fnm_multishells/1080_1735405309856/bin/npm
  npmPackages:
    svelte: ^5.0.0 => 5.15.0
    webpack: ^5.11.0 => 5.97.1
```


### Severity

blocking all usage of svelte
Repository: angular
Issue: Provide example with track function in `@for` docs
Labels: area: docs

### Describe the problem that you experienced

Documentation for `@for` control flow syntax might be improved with examples on how to use track functions. I've noticed that many developers when switching from `ngFor` to `@for` continue to use track function and provide it as a reference to a function which is incorrect.

For example, developers are switching from `<div *ngFor="let item of items; trackBy: myCustomFn">` to `@for (item of items, track myCustomFn)` which is incorrect. Another problem is that only starting from Angular 18 you'll see a warning that this is incorrect, while previous versions would silently use incorrect tracking.

In the documentation it's stated that you need to use expression there, but small explicit example would make things much better.

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

https://angular.dev/api/core/@for

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: PowerToys
Issue: Certain controlling elements do not respect application language setting
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

- Set system language to Chinese
- Set PowerToys' "Application Language" to English
- Flip through settings page

![Case 1](https://github.com/user-attachments/assets/76bfff37-741d-45ab-939c-8b99f5fe197f)
![Case 2](https://github.com/user-attachments/assets/e40087f1-a006-4754-af8e-cbc3e8aff12a)


### ✔️ Expected Behavior

All texts should follow "Application Language" setting

### ❌ Actual Behavior

Some of them are following system language setting instead

### Other Software

_No response_
Repository: PowerToys
Issue: NEW+ appears twice in the context menu
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

New+

### Steps to reproduce

I am now seeing two instances of the NEW+ menu item when I right-click on a folder.
BOTH work fine, but jut one will do!

![Image](https://github.com/user-attachments/assets/76697bc9-cff9-4a8e-96f4-8b98fe7f2950)


### ✔️ Expected Behavior

Just one instance of the NEW+ menu item.

### ❌ Actual Behavior

I am now seeing two instances of the NEW+ menu.

### Other Software

Edition	Windows 11 Pro
Version	23H2
Installed on	‎2022-‎09-‎21
OS build	22635.4655
Serial number	5CG0444HZL
Experience	Windows Feature Experience Pack 1000.22700.1065.0

Windows 11 Insider Preview Build 22635.4655 (Beta Channel)
Repository: ui
Issue: [bug]: Default fromField name not removed in Date Picker without hard reload
Labels: bug

### Describe the bug

When using the ShadCN UI **Date Picker** component, modifying the **fromField** name updates the value correctly, but the default fromField name is not removed unless a **hard reload** is performed. This behavior causes confusion and makes the component behave unexpectedly during development.

### Affected component/components

<DatePicker fromField="customFieldName" />

### How to reproduce

1. Integrate the ShadCN Date Picker component into a React project.
2. Assign a custom value to the fromField prop.
3. Observe that the new value is added, but the default fromField name remains.
4. Perform a hard reload of the development site.
5. Notice that the default name is now removed as expected.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Framework: React
ShadCN Version: 0.9.4
Browser: Chrome
Operating System: macOS
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: deno
Issue: Support "https" dependencies in package.json
Labels: suggestion,node compat

```
$ deno --version
deno 2.1.4 (stable, release, aarch64-apple-darwin)
v8 13.0.245.12-rusty
typescript 5.6.2
```

My `package.json` contains

```
{
  // ...
  "devDependencies": {
    // ...
    "odh-dashboard-frontend": "https://github.com/opendatahub-io/odh-dashboard.git#semver:v2.29.0&path:/frontend",
```

This package installs fine with `pnpm`, but with `deno install`, it is not installed, and I get a Warning about it.

```
$ deno install
Warning Not implemented scheme 'https'
    at file:///Users/jdanek/IdeaProjects/notebooks/tests/deno/package.json
```

Possibly related issue
* https://github.com/denoland/deno/issues/19158
Repository: PowerToys
Issue: Crashing on start: System.TypeInitializationException
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1.0

### Installation method

WinGet

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Just trying to start. Did install a few plugins

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

[2025-01-03.txt](https://github.com/user-attachments/files/18300231/2025-01-03.txt)
Repository: flutter
Issue: [Proposal]Add support for fixed or sticky headers in Table
Labels: c: new feature,framework,would be a good package,c: proposal,P3,workaround available,team-framework,triaged-framework

### Use case

The Table widget in Flutter does not currently support fixing all columns while scrolling horizontally. This feature is essential for scenarios where users need to navigate large tables while keeping all data in view and aligned.

### Proposal

Enhance the `Table` widget to support fixing all columns during horizontal scrolling.

**Key Features:**

- Allow all columns in the `Table` widget to remain fixed while scrolling vertically.
- Maintain alignment between headers and rows during scrolling.
- Provide seamless integration with existing table features such as styling and data binding.

**Visualization**
A table where all columns remain fixed in place while the user scrolls vertically. This ensures that all data remains visible, aligned, and accessible at all times.
Repository: ollama
Issue: Ollama should avoid calling hallucinated tools
Labels: bug

### What is the issue?

Sometimes the model seems to hallucinate and call a tool on the client that doesn't exist. In my opinion since Ollama has the list of tools being callable it should check that the tool being called is in this list before calling it.
This is described also there:
https://github.com/langchain4j/langchain4j/issues/1052

### OS

Linux, Docker

### GPU

Other

### CPU

Intel

### Ollama version

0.5.4
Repository: storybook
Issue: [Bug]: automigrate fails on EXDEV error
Labels: bug,help wanted,windows,automigrations

### Describe the bug

Running the command automigrate on windows, it tries to move the logfile from user's temp folder to the current project folder by renaming it. This fails, if temp folder and project folder are on different drives/partitions with the error: 
`Error: EXDEV: cross-device link not permitted, rename 'C:\Users\[USER]\AppData\Local\Temp\435cc8918d4e493a2eb400fc4351782f\migration-storybook.log' -> '.\migration-storybook.log'`

### Reproduction link

NONE

### Reproduction steps

_No response_

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
  Binaries:
    Node: 22.12.0 - C:\Program Files\nodejs\node.EXE
    npm: 11.0.0 - ~\AppData\Roaming\npm\npm.CMD <----- active
  Browsers:
    Edge: Chromium (128.0.2739.79)
  npmPackages:
    @storybook/addon-a11y: ^8.4.7 => 8.4.6
    @storybook/addon-coverage: ^1.0.4 => 1.0.4
    @storybook/addon-docs: ^8.4.7 => 8.4.6
    @storybook/addon-essentials: ^8.4.7 => 8.4.6
    @storybook/addon-interactions: ^8.4.7 => 8.4.6
    @storybook/addon-jest: ^8.4.7 => 8.4.6
    @storybook/addon-links: ^8.4.7 => 8.4.6
    @storybook/angular: ^8.4.7 => 8.4.6
    @storybook/core-server: ^8.4.7 => 8.4.6
    @storybook/test-runner: 0.19.0 => 0.19.0
    storybook: ^8.4.7 => 8.2.8
  npmGlobalPackages:
    @storybook/cli: 8.4.7
```

### Additional context

_No response_
Repository: go
Issue: proposal: change GORISCV64=rva20u64 to include compressed instructions
Labels: Proposal

### Proposal Details

When the proposal for `GORISCV64` was being discussed, the situation regarding compressed instructions for RISC-V was somewhat unclear and there were discussions about potentially reusing the encoding space. As such, the decision was to make the default `GORISCV64` value be `rva20u64` but explicitly exclude compressed instructions, effectively giving `rv64g`:

  https://github.com/golang/go/issues/61476#issuecomment-1782053089

There has since been a decision regarding the future of the C extension, with it remaining a mandatory part of RVA20 and RVA22:

  https://lists.riscv.org/g/tech-profiles/topic/rvi_bod_decision_regarding/102522954

This means that all general purpose RISC-V hardware that Go will run on must support compressed instructions.

This proposal is to change Go's meaning of `GORISCV64=rva20u64` to include compressed instructions, instead of continuing to prohibit them.
Repository: PowerToys
Issue: powertoys - workspaces - onenote app layout overrides the workspaces layout?
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Workspaces

### Steps to reproduce

Create a workspace that includes onenote
Manually launch onenote
Arrange the manually launched onenote in a size/position that is different from the workspace layout size/position
Close onenote
Launch the workspace
Workspace will launch onenote, but the size/position will be determined by onenote's last size/position and NOT by the workspace layout size/position

UPDATED NOTE:    I'm actually not sure how the OneNote size/position is determined.  It does not seem to be OneNote's last size/position after all. All I know is that the Workspace layout does NOT seem to fully work




### ✔️ Expected Behavior

I expect the workspace layout size/position to win out over the size/position that onenote seems to remember.

See screenshot of how I set the layout in Workspaces

![Image](https://github.com/user-attachments/assets/2e702141-8c22-492d-91b6-5c0f17db77e2)


### ❌ Actual Behavior

Onenote seems to remember the size/position it was in last, and this size/position seems to override the workspace layout

See screenshot of what actually happens

![Image](https://github.com/user-attachments/assets/c4d6ba37-0be6-4c87-a620-d0764189ecd4)


### Other Software

_No response_
Repository: neovim
Issue: :checkhealth can create a bug report
Labels: enhancement,plugin,runtime

# Problem

Bug reports sometimes are missing info. Should be easier to create a well-formed bug report using info available to `:checkhealth`.

# Expected behavior

Some sort of command, probably buffer-local in a `:checkhealth` buffer, like `gX` ? Or `:checkhealth bug`.

The command starts a github bug report by visiting a URL like this, contains all relevant info:

https://github.com/neovim/neovim/issues/new?labels=bug&title=user+docs+HTML%3A+gui.txt+&body=%23%23%20Problem%3A%0D%0D%23%23%20Steps%20to%20reproduce:%0D%0D%60%60%60%0DTODO%0D%60%60%60%0D%0D%23%23%20Expected%20behavior:%0D%0D%23%23%20System%20info:%0D%0D
Repository: rust
Issue: Upstream LLVM libunwind patch for SGX
Labels: C-cleanup,A-LLVM,O-SGX

Our LLVM fork currently carries a single patch, which adds support for SGX to libunwind: https://github.com/rust-lang/llvm-project/commit/29e82b2592450c43f7d0db2a18a7793c55c4957e

This patch should be upstreamed to LLVM (in some form that is acceptable for upstream).

cc @jethrogb @AdrianCX