sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: Bug:
Labels: Status: Unconfirmed

React version: 19.0.0

My code is not shown in the error stack. How can I know what caused the error?

![Image](https://github.com/user-attachments/assets/887bf94c-990a-4979-8dcc-d607361e00ec)

```
Uncaught Error: Objects are not valid as a React child (found: object with keys {message, data, description}). If you meant to render a collection of children, use an array instead.
    React 11
        throwOnInvalidObjectType
        reconcileChildFibersImpl
        createChildReconciler
        reconcileChildren
        beginWork
        runWithFiberInDEV
        performUnitOfWork
        workLoopSync
        renderRootSync
        performWorkOnRoot
        performWorkOnRootViaSchedulerTask
    performWorkUntilDeadline scheduler.development.js:44
    js scheduler.development.js:219
    js scheduler.development.js:364
    __require chunk-DC5AMYBS.js:9
    js index.js:6
    __require chunk-DC5AMYBS.js:9
    React 2
        js
        js
    __require chunk-DC5AMYBS.js:9
    js React
    __require chunk-DC5AMYBS.js:9
    <anonymous> react-dom_client.js:17892
react-dom-client.development.js:4446:12
    React 11
        throwOnInvalidObjectType
        reconcileChildFibersImpl
        createChildReconciler
        reconcileChildren
        beginWork
        runWithFiberInDEV
        performUnitOfWork
        workLoopSync
        renderRootSync
        performWorkOnRoot
        performWorkOnRootViaSchedulerTask
    performWorkUntilDeadline scheduler.development.js:44
    (Async: EventHandlerNonNull)
    js scheduler.development.js:219
    js scheduler.development.js:364
    __require chunk-DC5AMYBS.js:9
    js index.js:6
    __require chunk-DC5AMYBS.js:9
    React 2
        js
        js
    __require chunk-DC5AMYBS.js:9
    js React
    __require chunk-DC5AMYBS.js:9
    <anonymous> react-dom_client.js:17892
```

I have more than 75 thousand lines of code in my React app. How can I find where is the problem in my code?
Repository: transformers
Issue: Convert RT-DETR model to coreml
Labels: Vision

Hello,

I am currently working on an iOS application that requires object detection functionality, and I’m interested in using the RT-DETR model for this purpose. I would like to ask if anyone has experience or knows of a way to transfer the RT-DETR model into the CoreML format to be used on iOS devices.

Thank you in advance!
Repository: ollama
Issue: Add an ability to inject env variables to modelfile system message.
Labels: feature request

Hi All.
I`ve realized that that there is no way to make ollama models to know current date and time if it runs on ms windows. So I believe that would be useful if there would be possibility to use OS variables in the modelfile. Especially for date and time it would be better if model could obtain that data dynamically, just when it needed.

Use case: model could answer what date and time it is.
Repository: PowerToys
Issue: the FN lock function disabled
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

After using the keyboard mapping, the FN lock function of the computer itself will be disabled.

### ✔️ Expected Behavior

Maintain the original FN function or provide FN mapping.

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: vscode
Issue: Asset creation in cosmos db can fail after publishing
Labels: vscode-build,engineering

Build link https://monacotools.visualstudio.com/Monaco/_build/results?buildId=314603&view=logs&j=43b54640-f671-5524-8f7b-714d77229de9&t=7f630ceb-a7eb-52db-66b5-c361c37b9f4e

`vscode_client_win32_x64_archive` asset creation failed with

```
[vscode_client_win32_x64_archive] Deleting blob https://vscodeesrp.blob.core.windows.net/staging/6b601934-aa74-40f2-a610-a13b99cb8c0f
[vscode_client_win32_x64_archive] Deleted blob successfully
TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ESRPReleaseService.getReleaseStatus (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:225:21)
    at async ESRPReleaseService.createRelease (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:137:39)
    at async D:\a\_work\1\s\build\azure-pipelines\common\publish.js:543:13
    at async withLease (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:500:32)
    at async processArtifact (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:532:5)
    at async main (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:578:9) {
  [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: api.esrp.microsoft.com:443, timeout: 10000ms)
      at onConnectTimeout (node:internal/deps/undici/undici:2599:28)
      at Immediate._onImmediate (node:internal/deps/undici/undici:2568:35)
      at process.processImmediate (node:internal/timers:483:21) {
    code: 'UND_ERR_CONNECT_TIMEOUT'
  }
}
[vscode_client_win32_x64_archive] Error: [vscode_client_win32_x64_archive] Worker stopped with exit code 1
    at Worker.<anonymous> (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:647:32)
    at Worker.emit (node:events:518:28)
    at [kOnExit] (node:internal/worker:315:10)
    at Worker.<computed>.onexit (node:internal/worker:229:20)
Error: Some artifacts failed to publish
    at main (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:674:15)

```
Repository: angular
Issue: Improve error message `Cannot resolve type entity ${entity} to {symbol|declaration}`
Labels: area: packaging,area: compiler

### Command

build

### Description

I’m talking about this error, for instance, which people seem to encounter somewhat often [1–5]:

```
$ ng build
⠋ Generating browser application bundles (phase: building)...
✔ Browser application bundle generation complete.

./src/main.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Cannot resolve type entity i7.BusifiableButtonComponent to symbol
```

This error message is not very actionable.

[1] https://stackoverflow.com/questions/71675705/error-cannot-resolve-type-entity-i10-bidimodule-to-symbol-while-building-angula
[2] https://github.com/primefaces/primeng/issues/11581
[3] https://github.com/valor-software/ngx-bootstrap/issues/6662
[4] https://github.com/angular/angular/issues/46441
[5] https://onthecode.co.uk/blog/error-cannot-resolve-type-entity-i3-dialogmodule-to-symbol

### Describe the solution you'd like

The issue seems to always be related to a transitive dependency not being found. *If* that is the true meaning of the error, I suggest rewording the error message to reflect that. I don’t know how much information is available at this point. My dreamed-of error message would be something like this (drawing inspiration from [JoostK’s comment](https://github.com/angular/angular/issues/46441#issuecomment-1161376788)):

> The type ${entity} could not be found. It seems to be a transitive dependency via this import chain:
>  (root project) → (dependency) → (dependency) → ${entity}.
> This typically happens when a library is linked from another directory tree, where the necessary dependencies are not in a location the compiler can find, for instance when there is no corresponding node_modules directory from within that tree.
> Make sure that the library’s properly declares its dependencies and that they are installed.
> If it is due to symbolic links, then setting `projects.${project}.architect.build.options.preserveSymlinks: true` in the angular.json file may help. Otherwise, explicit path mappings for the unresolved dependency may also help.

At the very least, the file that imports the unresolvable entity should be displayed, again as suggested by [JoostK](https://github.com/angular/angular/issues/52520#issuecomment-1794326712).

### Describe alternatives you've considered

_No response_
Repository: kubernetes
Issue: k8s deployment remove duplicate `tolerations` but not `affinity`
Labels: kind/bug,sig/apps,needs-triage

### What happened?

If we create a deployment with duplicate toleration the pod spec doesn't reflect the duplicate values, but the same doesn't happen to duplicate node affinities,

Deployment tolerations:
```
      tolerations:
      - effect: NoSchedule
        key: "key1"
        operator: Equal
        value: "true"
      - effect: NoSchedule
        key: "key1"
        operator: Equal
        value: "true"

```

Pod tolerations:
```
  tolerations:
  - effect: NoSchedule
    key: "key1"
    operator: Equal
    value: "true"
```


Deployment Affinity == Pod affinity :
```
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: "key1"
                operator: Exists
              - key: "key1"
                operator: Exists
            - matchExpressions:
              - key: "key1"
                operator: Exists
              - key: "key1"
                operator: Exists
```


### What did you expect to happen?

Desired affinity:
```
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: "key1"
                operator: Exists
```

### How can we reproduce it (as minimally and precisely as possible)?

Create a normal deployment with placements(tolerations and affinity) 

### Anything else we need to know?

_No response_

### Kubernetes version
k8s.io/api v0.31.2
<details>

```console
$ kubectl version
# paste output here

```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: TypeScript
Issue: On magic disappearance of fields in the wild
Labels: Working as Intended

### 🔎 Search Terms

anonymous class this any

### 🕗 Version & Regression Information

I was unable to test this on prior versions because there is no tool to check for it online


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/MYewdgzgLgBAhjAvDMBTA7jYAbOEIwDeMEq2AZkjFABYCWEA3DAL6MBQokI2qAdNhABzABRw+pCkkTI4ASg6dw0GIJAAHKmkw48BQuxhGSZSsloMOxmDSoBGK8djJtWXPiKHrx28gBMjt7UVJLkgazsbOwA9NEwAAoAThqoiVAAnjAA5FBZMAAmIKgEYCCwqAAeDLBK3LwCwiJq6nxQre2+MjB+CkA

### 💻 Code

```ts
const a = new class { self = this; };
console.log(a.self === a);

const loop = new class {
    self = this;
    h = 1;
    t = new class {
        h = 2;
        t = self;
    }
};
// Property 't' does not exist 
console.log(loop.t.t.t.h === 2);
```


### 🙁 Actual behavior

Property 't' does not exist 

### 🙂 Expected behavior

No type error

### Additional information about the issue

_No response_
Repository: PowerToys
Issue: Host File Editor - comment line - position of additional content Top | Bottom | (New) Remain as is
Labels: Needs-Triage

### Description of the new feature / enhancement

Add one more option to remain the comments as is to the position of additional content. We may use it as a comment or grouping of the records.

### Scenario when this would be used?

updating the host file. It is either move the comments to top or bottom.

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: Next.js Link component causes navigation to a non-existent page in stories
Labels: bug,nextjs

### Describe the bug

When using the `Link` component from Next.js 15 within an `appDirectory` configuration, the component behavior is not properly overridden. This leads to navigating directly to nonexistent pages after clicking the link. 

This behavior does not occur with Next.js 14.

### Reproduction link

https://stackblitz.com/edit/github-6hzs76ok?file=src%2Fstories%2FHeader.tsx

### Reproduction steps

1. Go to the above link
2. Go to a story of the Header component
3. Click the link on the header, and the preview will crush

### 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.6.0-alpha.2 => 8.6.0-alpha.2 
    @storybook/addon-interactions: ^8.6.0-alpha.2 => 8.6.0-alpha.2 
    @storybook/addon-onboarding: ^8.6.0-alpha.2 => 8.6.0-alpha.2 
    @storybook/blocks: ^8.6.0-alpha.2 => 8.6.0-alpha.2 
    @storybook/nextjs: ^8.6.0-alpha.2 => 8.6.0-alpha.2 
    @storybook/react: ^8.6.0-alpha.2 => 8.6.0-alpha.2 
    @storybook/test: ^8.6.0-alpha.2 => 8.6.0-alpha.2 
    storybook: ^8.6.0-alpha.2 => 8.6.0-alpha.2
```

### Additional context

[Proper behavior with Next.js 14](https://stackblitz.com/edit/github-scn3vgkf?file=src%2Fstories%2FHeader.tsx,src%2Fstories%2FHeader.stories.ts&preset=node)
Repository: ui
Issue: [feat]: Catergory Bar in Charts
Labels: area: request

### Feature description

Tremor UI offers a chart type called Category Bar, which we previously used in our product.

![Image](https://github.com/user-attachments/assets/20394386-dfc0-41ef-b2a3-070446d27a7c)


 However, when we transitioned to Shadcn Chart, we noticed that this specific chart type is not available.


I wanted to check if there’s a possible workaround using the current bar chart component in Shadcn to replicate the functionality and appearance of the Category Bar from Tremor UI. 

Let me know if this is feasible or if there are alternative approaches we can explore.

### Affected component/components

Charts

### Additional Context

https://tremor.so/charts

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues and PRs
Repository: TypeScript
Issue: constraint of type parameter should make effect in method declaration
Labels: Duplicate

### 🔎 Search Terms

"constraint", "method declaration"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about "A method and a function property of the same type behave differently"



### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.8.0-dev.20250127#code/JYOwLgpgTgZghgYwgAgIIB4AqA+ZBvAKGWRgHtT0BVZCAD0hABMBnZHACloC5lKBKHnBABPAgF8CBGAFcQCMMFIgSABnZweGZmCigA5tgA0yAEab0IaQFsT0bH3xFip5AF5kcZAHovyZgAtSaQAbRmQoCAAHUigwGigoGNNpOMQwaThg4OFkEFIwADpJZ1MCslJ2AEYHH2RZZiCmcUkgA

### 💻 Code

```ts
interface A<T> {
  foo<U extends T>(x: U): any
}

function f0(a: A<string>, b: A<number>) {
    b = a // should report error but actually not.

    b.foo(1) // unsound
}
```


### 🙁 Actual behavior

check success

### 🙂 Expected behavior

`b = a` report `number` cannot assign to `string`.

### Additional information about the issue

_No response_
Repository: material-ui
Issue: CardActionArea does not comply with the HTML5 specification
Labels: component: card,status: waiting for maintainer

### Steps to reproduce

Steps:
1. Open this link to live example: [(MUI Card Docs)](https://mui.com/material-ui/react-card/#primary-action)
2. Open developer tools
3. Make sure that tag `<div>` is placed inside a tag `<button>`, which does not comply to HTML5's specification

Problem:
http://www.w3.org/TR/2012/WD-html5-20120329/the-button-element.html#the-button-element says that a `<button>` must contain only Phrasing content. Phrasing content is defined as including `<span>` but not `<div>`.

![Image](https://github.com/user-attachments/assets/8b8ff7e6-d0af-42ee-9a7c-4b922cf71702)


### Current behavior

`<CardActionArea>` when rendered becomes a `<button>` tag. If you add anything inside of it, e.g. `<CardContent>` or `<Box>`, it will happen that after rendering, you'll end up with a `<button>` tag, that has `<div>` inside of it.

### Expected behavior

All components from MUI should follow HTML5's validation rules, including `<CardActionArea>`.

### Context

I was using MUI's `<Card>` component, which had a `<CardActionArea>` component inside of it, with child components, such as `<CardHeader>` and `<CardContent>`, then I published my website to the server and tried to check for any HTML validation errors on https://validator.w3.org, which showed me errors related to `<Card>` component from MUI.

![Image](https://github.com/user-attachments/assets/479572ba-3532-49be-93d0-77605c79f6f5)

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.6.6 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @emotion/react: ^11.13.3 => 11.14.0
    @emotion/styled: ^11.13.0 => 11.14.0
    @mui/base:  5.0.0-beta.69
    @mui/core-downloads-tracker:  6.4.1
    @mui/icons-material: ^6.1.3 => 6.4.1
    @mui/lab: ^6.0.0-beta.22 => 6.0.0-beta.24
    @mui/material: ^6.1.3 => 6.4.1
    @mui/private-theming:  6.4.1
    @mui/styled-engine:  6.4.0
    @mui/system:  6.4.1
    @mui/types:  7.2.21
    @mui/utils:  6.4.1
    @types/react: ^18.3.11 => 18.3.18
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    typescript: ^5.7.3 => 5.7.3
```
</details>


**Search keywords**: W3C CardActionArea Card HTML5 SEO
Repository: rust
Issue: Tracking issue for release notes of #136127: Allow `*const W<dyn A> -> *const dyn A` ptr cast
Labels: relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #136127.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Allow `*const W<dyn A> -> *const dyn A` ptr cast](https://github.com/rust-lang/rust/pull/136127)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @WaffleLapkin -- origin issue/PR authors and assignees for starting to draft text
Repository: react
Issue: [Compiler Bug]: Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client. This can happen if a SSR-ed Client Component used
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/egorBezmen/next15-styled-components

### Repro steps

1) npm install
2) npm run dev
3) open [localhost](http://localhost:3000) 

<img width="1512" alt="Image" src="https://github.com/user-attachments/assets/53f68d57-6c50-4cf7-baf5-5aaf7ac4a7a6" />

https://github.com/vercel/next.js/tree/canary/examples/with-styled-components
I deployed the template project and enabled the option react-compiler
codesandbox - https://codesandbox.io/p/github/egorBezmen/next15-styled-components/main?import=true

### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1 / 19.0.0

### What version of React Compiler are you using?

19.0.0-beta-27714ef-20250124
Repository: vscode
Issue: Test: Electron 34 update
Labels: testplan-item

Refs: https://github.com/microsoft/vscode/issues/237437

- [ ] macOS @osortega
- [ ] linux @joshspicer
- [x] windows @lszomoru

Complexity: 3


[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23238839%0A%0A&assignees=deepak1556)

---

We plan to promote Electron 34 in the February 2025 milestone to insiders. The following tests cover some of the common UI bits that don't have smoke tests. You can download the nightly explorations builds from [here](https://builds.code.visualstudio.com/builds/exploration?released=true&dev=true) for testing.

**Testing:**

* **macOS:**
  * Enable Native Tabs (via settings: `window.nativeTabs: true`)
    - Ensure native tabs are enabled in the system preferences (System Preferences > General > Prefer tabs: "always":)
    - Launch application
    - Try opening new window from either command line (code-exploration <path-to-project>) or from the menu entry (Cmd + Shift + N)
    - Verify new window is launched as a new tab in the active instance of the application window is focused when starting from command line
    - open the code exploration application from finder or dock
    - open external terminal
    - run code-exploration
    - make sure the new window is put to foreground
  * Font rendering with non-default family name
    - Download and install `Inconsolata ExtraBold` from [font](https://fonts.google.com/specimen/Inconsolata)
    - In the editor set `"editor.fontFamily": "Inconsolata ExtraBold"`
    - Confirm that the font applies and compare it with insiders

* **windows:**
  * verify maximize and restore operations work as expected when OS task bar is auto-hidden for custom titlebar
  * Verify titlebar is not clipped off when exiting fullscreen
    - Maximize VS Code window
    - Press F11 or Ctrl+K Z twice to enter/exit full screen.
    - Verify titlebar is not cropped

* **linux:**
  * Verify clicking on native menu does not crash the application 
     - Switch to native title bar `"window.titleBarStyle": "native"`
     - Click on any of the menu options `File`, `Edit` etc
     
 * **All OS:**
   * Check out the `electron-34.x.y` branch locally and verify you can run out of sources, set a breakpoint and debug using the VS Code launch configurations and VS Code debugger