sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: [turbopack] emotion transform plugin drop `config.import_map` needlessly
Labels: Turbopack

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### 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): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: 14.2.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

with-emotion

### What browser are you using? (if relevant)

Chrome Version 129.0.6668.90 (Official Build) (arm64)

### How are you deploying your application? (if relevant)

Code Sandbox

### Describe the Bug

Trying to use a component selector inside `css` function imported from `@mui/material` or `@mui/material/styles`:
```tsx
import { css, styled } from "@mui/material/styles";

const OtherDiv = styled("div")`
  background: blue;
  width: 100px;
  height: 100px;
`;

const MyCustomDiv = styled("div")`
  width: 300px;
  height: 300px;
  background: red;

  ${() => css`
    &${OtherDiv} {
      background: black;
    }
  `}
`;

export default function Home() {
  return (
    <main>
      <MyCustomDiv>
        <OtherDiv />
      </MyCustomDiv>
    </main>
  );
}
```

The following error is thrown:
![CleanShot 2024-10-16 at 23 41 13@2x](https://github.com/user-attachments/assets/68368c6b-928a-4270-ae28-a1f515813005)

I have also tried to add `importMap` to the `emotion` property of the `compiler` option:
```ts
/** @type {import('next').NextConfig} */
const nextConfig = {
  compiler: {
    emotion: {
      importMap: {
        "@mui/system": {
          styled: {
            canonicalImport: ["@emotion/styled", "default"],
            styledBaseImport: ["@mui/system", "styled"],
          },
        },
        "@mui/material/styles": {
          styled: {
            canonicalImport: ["@emotion/styled", "default"],
            styledBaseImport: ["@mui/material/styles", "styled"],
          },
        },
        "@mui/material": {
          styled: {
            canonicalImport: ["@emotion/styled", "default"],
            styledBaseImport: ["@mui/material", "styled"],
          },
        },
      },
    },
  },
};

module.exports = nextConfig;
```


### Expected Behavior

It should work with Turbopack. It works with `next dev` but not with `next dev --turbo`

### To Reproduce

Here is a Code Sandbox with the reproduction:
https://codesandbox.io/p/devbox/zy4lww

Here is a GitHub repo with the reproduction
https://github.com/l0gicgate/nextjs-issue-71408
Repository: vscode
Issue: Support a chat participant getting an event when a link is clicked
Labels: chat

<!-- ⚠️⚠️ 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. -->

It'd be nice if when a user clicked a link in a chat window, that we had some event or telemetry to indicate the link was clicked. We could use this in concert with #231549 to know whether the links we're generating from the LLM are actually any good or not.

I see there's a proposed chat addition here:

https://github.com/microsoft/vscode/blob/997ad5efbfe3f33978700c100c0198ad17c01ae7/src/vscode-dts/vscode.proposed.chatParticipantAdditions.d.ts#L309

Which looks like it'd cover buttons, but links would be helpful too.
Repository: deno
Issue: Working with workspaces like yarn package manager
Labels: cli,suggestion

Yarn package manager for Nodejs has amazing CLI for working with monorepos - https://yarnpkg.com/features/workspaces

It would be great if Deno could implement it as well since it supports monorepos as of recent.

## [`yarn workspace`](https://yarnpkg.com/cli/workspace)

Run commands only for the specified workspace.

## [`yarn workspaces foreach`](https://yarnpkg.com/cli/workspaces/foreach)

Run package.json/deno.json scripts/tasks for all or filtered workspaces. The filteres are:
- `--all` - all workspaces
- `--since` - only changed packages compared to master or other specified branch/commit sha
- `--from` - package names matching a pattern
- `--exclude` - exclude packages

As well as its options for running scripts:
- `--parallel` - run all scripts in parallel
- `--topological` - run all scripts but first on its local dependencies

## [`yarn exec`](https://yarnpkg.com/cli/exec)

Execute shell script. This combined with above workspace CLI can be really powerfull.
Repository: ollama
Issue: Add nemotron-4-340b-instruct
Labels: model request

Since we recently discovered how good LLAMA 3.1 70B Nemotron is, maybe we could consider adding the 340B model... for those with abundant GPU resources - are there any?
Repository: react
Issue: [DevTools Bug]:  `gl.useProgram(program);` will cause react-refresh to perform incorrect code injection.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://github.com/Yukiniro/reproduce/tree/master/rspack-issue-hot-update-worker

### Repro steps

1. clone `https://github.com/Yukiniro/reproduce/tree/master/rspack-issue-hot-update-worker`
2. Run pnpm run dev
3. Go to http://localhost:8080/

```js
      const setup = () => {
        const offscreenCanvas = new OffscreenCanvas(100, 100);
        const gl = offscreenCanvas.getContext("webgl2");

        const program = gl.createProgram();
        gl.linkProgram(program);
        gl.useProgram(program);
      };
 ``` 
    will be transform to be:
    
```js
      var _s = $RefreshSig$();
      const setup = () => {
        _s();
        const offscreenCanvas = new OffscreenCanvas(100, 100);
        const gl = offscreenCanvas.getContext("webgl2");

        const program = gl.createProgram();
        gl.linkProgram(program);
        gl.useProgram(program);
      };
 ``` 
 Then, I use the `setup` string to create a worker.

```js
const worker = new Worker(URL.createObjectURL(new Blob([`(${setup})()`])));
console.log(worker);
```

There will throw a error in the worker becuase of `_s()`.

I am not sure if this is a bug. If not, what could I do sometion to skip the generation of `_s()`.
    

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: flutter
Issue: [ios][platform view]Simplify platform view's touch gesture logic
Labels: platform-ios,a: platform-views,P2,team-ios,triaged-ios

Touches can be consumed by either flutter widgets or platform views. The touch callback needs to be on platform thread, while the information of which component should receive the touch is in the framework on the UI thread. 

Previously we had separate platform thread and UI thread, so we came up with pretty convoluted logic with 2 gesture recognizers (["forwarding" and "delaying" recognizer](https://github.com/flutter/engine/blob/main/shell/platform/darwin/ios/framework/Source/FlutterPlatformViews_Internal.mm#L519)).  This code is complex and error prune, and already caused issues such as https://github.com/flutter/flutter/issues/136244

### Proposal

Now since we merged platform thread and UI thread, we should be able to greatly simplify the logic by synchronous state access.
Repository: Python
Issue: adaptive merge sort and stalin sort addition in sorting algorithms 
Labels: enhancement

### Feature description

I would like to add adaptive merge sort and stalin sort which are the different types of sorting in python and sometimes are helpful.
Kindly assign me the issue and check the PR:#11989 and PR:#11993
Repository: ant-design
Issue: Button添加一个 “asyncLoading” 的api
Labels: 💡 Feature Request

### What problem does this feature solve?

无需重复的写按钮loading逻辑，loading的时候会自带 “防抖” 功能

### What does the proposed API look like?

Button添加一个api，例如叫 asyncLoading，当我绑定的处理函数为 promise 并且asyncLoading为true时，会开启按钮的loading，当事件函数返回true的时候，暂停当前的按钮loading

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: SCM - Option to Reverse the Order of Elements in the Source Control Section
Labels: scm,under-discussion

<!-- ⚠️⚠️ 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 like to suggest an enhancement to the Source Control / Git tab in the “SOURCE CONTROL” section of VScode. The proposed feature is **an option** to reverse the order of the following elements:

- Commit Message
- Commit Button
- Stage Changes
- Changes

to:

- Changes
- Staged Changes
- Commit Message
- Commit Button

Arguments:

_Logical Order:_ This arrangement follows a logical top-down workflow. Users typically review changes first, stage them, write a commit message, and finally commit the changes. This sequence aligns with the natural progression of tasks in source control management.

_UI Design Consistency:_ This order is consistent with typical UI design principles, where actions are presented in the order they are performed. It enhances usability by reducing cognitive load and making the interface more intuitive.

This feature is particularly useful when multiple repositories are visible where I can be really hard to see which commit button and messages which relates to which repository. It helps in maintaining a clear and organized view, making it easier to manage changes across different repositories.

Implementing this feature would improve the overall user experience by aligning the interface with common workflows and design standards.
Repository: deno
Issue: Support Wrangler, the CLI for Cloudflare Workers
Labels: bug,node compat,node:vm

I checked the fix with Deno v2.0.1, but it seems that a different error has occurred.

[Closed] Support Wrangler, the CLI for Cloudflare Workers
https://github.com/denoland/deno/issues/25899

[Merged] fix(child_process): map node --no-warnings flag to --quiet
https://github.com/denoland/deno/pull/26288

Cloudflare Workers SDK
https://github.com/cloudflare/workers-sdk

```shell
$ deno run npm:wrangler

error: unexpected argument '--experimental-vm-modules' found

  tip: a similar argument exists: '--ext'
  tip: to pass '--experimental-vm-modules' as a value, use '-- --experimental-vm-modules'

Usage: deno run --quiet --ext <ext> [SCRIPT_ARG]...
```

```shell
$ deno --version

deno 2.1.4 (stable, release, aarch64-apple-darwin)
v8 13.0.245.12-rusty
typescript 5.6.2
```

```shell
$ npx wrangler --version

 ⛅️ wrangler 3.96.0
-------------------
```
Repository: TypeScript
Issue: NoInfer breaks discriminate union autocomplete
Labels: Suggestion,Experience Enhancement

### 🔎 Search Terms

no infer discriminate union

### 🕗 Version & Regression Information

Tested on version 5.6.3

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYOwLgpgTgZghgYwgAgILIN4ChnLATwAcIAuZAcjnIBodkA3OAGwFdTkBnMKUAcwG4sAXyxZQkWIhQAhTHQLEy5AEY06HYAC92IFgFtl0QSKwKUAVRDAA9iGQBeNMgA+yaYKwwWIBGBt3EJEIwAB4AFWQIAA9IEAATDmRLfwA+AApvfzIAOWsASRAYaHCUgEo5YVFAiGC0jDMlKiFSoA

### 💻 Code

```ts
interface A {
  type: 'a',
  value: string;
}

interface B {
  type: 'b',
  size: number;
}

type Union = A | B;

function accept<T extends Union>(union: NoInfer<T>) {

}

accept({type: 'a'})
```


### 🙁 Actual behavior

When trying to autocomplete after writing type `a` the autocomplete doesn't work (but the result does get type checked):
![Image](https://github.com/user-attachments/assets/06d3a7d8-05d1-4adc-b010-40053bd3e3d8)


### 🙂 Expected behavior

Even with `NoInfer` it should autocomplete the other properties of the "inferred" discriminate union case as it correctly type checks it if written wrong.

### Additional information about the issue

_No response_
Repository: ollama
Issue: Suggest adding shibing624/text2vec model
Labels: feature request

Text2vec is used as a vectorized model, but it is currently not found in the library. I don't know how to add the model
Repository: svelte
Issue: Svelte 5: Custom element's default <slot> not created when no initial children are passed
Labels: bug,custom element

### Describe the bug

When Svelte creates a custom element, if no child elements are initially passed in, the default `<slot>` tag will not be created, causing subsequently added child elements to not be rendered in the slot.

It seems that this part might be responsible:
https://github.com/sveltejs/svelte/blob/f579a3ba7d8f088d1d4f8625758e5e5598c9ebfa/packages/svelte/src/internal/client/dom/elements/custom-element.js#L267

 Hope this helps with troubleshooting the issue.

### Reproduction

https://github.com/CLDXiang/svelte-custom-element-no-default-slot-bug

Initial state:
<img width="587" alt="image" src="https://github.com/user-attachments/assets/ab7e63ab-c981-4cfc-903a-2601893f87a7">

Append some children:
<img width="579" alt="image" src="https://github.com/user-attachments/assets/285321b8-876c-4a84-ae99-8147bb2e4e99">


### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 15.0.1
    CPU: (20) x64 Intel(R) Core(TM) i9-10910 CPU @ 3.60GHz
    Memory: 158.62 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.20.4 - ~/.nvm/versions/node/v18.20.4/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v18.20.4/bin/npm
    pnpm: 9.12.1 - ~/.nvm/versions/node/v18.20.4/bin/pnpm
    bun: 1.0.11 - ~/.bun/bin/bun
  Browsers:
    Chrome: 129.0.6668.101
    Safari: 18.0.1
```


### Severity

annoyance
Repository: rust
Issue: x86-32 "f16" ABI needs SSE, incompatible with i586 targets
Labels: A-LLVM,C-bug,A-ABI,O-x86_32,F-f16_and_f128,S-waiting-on-LLVM

@beetrees [wrote](https://github.com/rust-lang/rust/issues/131799#issuecomment-2418896985)

> On 32-bit x86, [the ABI specifies that f16 gets returned in xmm0](https://gitlab.com/x86-psABIs/i386-ABI/-/blob/hjl/x86/master/low-level-sys-info.tex#L358-360), which is what Clang and GCC do (neither Clang nor GCC support _Float16 when SSE2 is disabled)

So... for the "Rust" ABI we can do our own thing bypassing this (likely similar fo `f32`/`f64`, we should just always return `f16` in via `PassMode::Indirect`), but what shall we do for the `extern "C"` ABI? We'll need a new dedicated compiler error (likely as part of the pass that we are adding [here](https://github.com/rust-lang/rust/pull/127731)) that rejects returning `f16` when the SSE registers are not available.

~~That will mean that libcore does not compile on i586 targets....~~ Actually libcore uses the "Rust" ABI so that one is fine. But if we have `extern "C"` float functions somewhere those would not be portable any more.

Cc @tgross35 @chorman0773
Repository: storybook
Issue: [Bug]: Angular APP_INITIALIZER not firing at Storybook 8
Labels: bug,angular

### Describe the bug

When using storybook 8 version in angular, the APP_INITIALZER dosen't work.

The problem looks the same as [the issue](https://github.com/storybookjs/storybook/issues/21121) before.

I tried to correct it by referring to what was on[ this link](https://github.com/storybookjs/storybook/issues/22674), but it still doesn't run.

I modified 'preview.ts' as below in this [stackblitz project,](https://stackblitz.com/edit/github-rkffss-81zfge) but it doesn't work.

```
const preview: Preview = {
  parameters: {
    actions: { argTypesRegex: '^on[A-Z].*' },
    controls: {
      matchers: {
        color: /(background|color)$/i,
        date: /Date$/i,
      },
    },
  },
  decorators: [
    moduleMetadata({
      providers: [
        {
          provide: APP_INITIALIZER,
          useFactory: () => {
            console.log('APP_INITIALIZER!!!!');
          },
          multi: true,
        },
      ],
    }),
  ],
};

export default preview;

```



### Reproduction link

https://stackblitz.com/edit/github-rkffss-81zfge

### Reproduction steps

1. Go here https://stackblitz.com/edit/github-rkffss-81zfge
2. and modify preview.ts 
```
const preview: Preview = {
  parameters: {
    actions: { argTypesRegex: '^on[A-Z].*' },
    controls: {
      matchers: {
        color: /(background|color)$/i,
        date: /Date$/i,
      },
    },
  },
  decorators: [
    moduleMetadata({
      providers: [
        {
          provide: APP_INITIALIZER,
          useFactory: () => {
            console.log('APP_INITIALIZER!!!!');
          },
          multi: true,
        },
      ],
    }),
  ],
};

export default preview;
```

3. I can't see the `APP_INITIALIZER!!!!`  log

### System

storybook@8.3.5

### Additional context

_No response_
Repository: vscode
Issue: Cannot be built in AIX 7.1
Labels: install-update,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Not sure

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.93.1
- OS Version: AIX 7.1 PPC64

Steps to Reproduce:

1. Login to AIX
2. Compile and install node 20.18.0
3. Clone and checkout 1.93.1 branch
4. Install all dependencies with `npm install --global --verbose`

Already known issues: [microsoft/vscode-policy-watcher](https://github.com/microsoft/vscode-policy-watcher/issues/34) and [PR](https://github.com/microsoft/vscode-policy-watcher/pull/35)

Upgrade of dependencies `@vscode/policy-watcher`(in `lib/vscode/package.json`) might solve this issue.
Repository: flutter
Issue: Possibility to anchor `showMenu` within its `RelativeRect`
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

When creating drop down buttons a very common use-case is to align them with the right edge of their parents, like this:

![image](https://github.com/user-attachments/assets/cc3bc4db-7b99-48e9-b8c0-07108c55dc65)

But as far as I'm aware it is not possible to do this consistently since you can't access the width of the menu until it has been laid out, so you will only be able to align it to the left:
![image](https://github.com/user-attachments/assets/6b8f4900-e097-48d5-b936-af00d8b05184)

```dart
showMenu(
  position: _menuPosition(context),
  ...
)

RelativeRect _menuPosition(BuildContext context) {
  final box = context.findRenderObject() as RenderBox;
  final overlay = Overlay.of(context).context.findRenderObject() as RenderBox;
  const offset = Offset.zero;

  return RelativeRect.fromRect(
    Rect.fromPoints(
      box.localToGlobal(
        box.size.bottomLeft(offset),
        ancestor: overlay,
      ),
      box.localToGlobal(
        box.size.bottomRight(offset),
        ancestor: overlay,
      ),
    ),
    offset & overlay.size,
  );
}
```

### Proposal

It would be great if there was an `menuAligment` argument to `showMenu` so that you could choose how to align the menu within the `RelativeRect`.
Repository: excalidraw
Issue: Add distribute tool for equidistant spacing
Labels: good first issue,UX/UI

I am missing the distribute feature from Inkscape. It would be awesome if that could be added.

See
https://inkscape-manuals.readthedocs.io/en/latest/align-and-distribute.html

![Image](https://github.com/user-attachments/assets/825f4ec4-0b58-4535-bc74-71a879db577f)
Repository: rust
Issue: A out-of-air lifetime that that may not live long vs. the implementation is not general enough
Labels: A-diagnostics,T-compiler,A-NLL,NLL-diagnostics,D-confusing,D-terse,A-higher-ranked

### Code
````rust
fn test<F>(f:F)
where F: for<'b> FnOnce(&'b i32){}


fn main(){
    test(|s:&'static i32|{});
}
````

### Current output
```
  --> src/main.rs:11:11
   |
11 |     test(|s:&'static i32|{});
   |           ^ help: if this is intentional, prefix it with an underscore: `_s`

error: lifetime may not live long enough
  --> src/main.rs:11:11
   |
11 |     test(|s:&'static i32|{});
   |           ^ - let's call the lifetime of this reference `'1`
   |           |
   |           requires that `'1` must outlive `'static`
```

### Desired output

> The implementation is not general enough

### Rationale and extra context

The closure parameter is explicitly specified as `&'static i32`, where does the lifetime `'l` come from? Moreover, the lifetime `'static` should outlive any lifetime, however, the diagnosis instead says
> lifetime may not live long enough

Presumably, the implementation of trait `FnOnce` for the closure type is only for `'static`, which is not general enough. 

### Other cases

_No response_

### Rust Version

rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-apple-darwin
release: 1.81.0
LLVM version: 18.1.7


### Anything else?

_No response_