sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Error using `node:dgram` with link-local IPv6 addresses
Labels: bug,node compat

Repro:

```js
import { strictEqual } from "node:assert";
import { createSocket } from "node:dgram";
import { networkInterfaces } from "node:os";
import process from "node:process";

const isWindows = process.platform === "win32";

function linklocal() {
  for (const [ifname, entries] of Object.entries(networkInterfaces())) {
    for (const { address, family, scopeid } of entries) {
      if (family === "IPv6" && address.startsWith("fe80:")) {
        return { address, ifname, scopeid };
      }
    }
  }
}
const iface = linklocal();

if (!iface) {
  process.exit(0);
}

const address = isWindows ? iface.address : `${iface.address}%${iface.ifname}`;
const message = "Hello, local world!";

// Create a client socket for sending to the link-local address.
const client = createSocket("udp6");

// Create the server socket listening on the link-local address.
const server = createSocket("udp6");

server.on(
  "listening",
  () => {
    const port = server.address().port;
    client.send(message, 0, message.length, port, address);
  },
);

server.on(
  "message",
  (buf, info) => {
    const received = buf.toString();
    strictEqual(received, message);
    // Check that the sender address is the one bound,
    // including the link local scope identifier.
    strictEqual(
      info.address,
      isWindows ? `${iface.address}%${iface.scopeid}` : address,
    );
    server.close();
    client.close();
  },
);

server.bind({ address });
```

Output:

```
error: Uncaught Error: bind UNKNOWN fe80::1%lo0
    at __node_internal_captureLargerStackTrace (ext:deno_node/internal/errors.ts:93:9)
    at __node_internal_exceptionWithHostPort (ext:deno_node/internal/errors.ts:217:10)
    at node:dgram:273:20
    at Array.processTicksAndRejections (ext:deno_node/_next_tick.ts:36:15)
    at eventLoopTick (ext:core/01_core.js:165:29)
```

Expect no output, and for the program to exit cleanly.
Repository: pytorch
Issue: DISABLED test_metadata_consistency_check (__main__.DTensorMeshTest)
Labels: oncall: distributed,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_metadata_consistency_check&suite=DTensorMeshTest&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/27821123604).

Over the past 3 hours, it has been determined flaky in 3 workflow(s) with 4 failures and 3 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_metadata_consistency_check`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/opt/conda/envs/py_3.8/lib/python3.8/site-packages/torch/testing/_internal/common_distributed.py", line 537, in wrapper
    self._join_processes(fn)
  File "/opt/conda/envs/py_3.8/lib/python3.8/site-packages/torch/testing/_internal/common_distributed.py", line 760, in _join_processes
    self._check_return_codes(elapsed_time)
  File "/opt/conda/envs/py_3.8/lib/python3.8/site-packages/torch/testing/_internal/common_distributed.py", line 814, in _check_return_codes
    raise RuntimeError(
RuntimeError: Process 2 terminated or timed out after 305.00653409957886 seconds
```

</details>


Test file path: `distributed/_tensor/test_dtensor.py`

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @clee2000
Repository: go
Issue: net: TestCloseWrite/tcp failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestCloseWrite/tcp"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741576610546473377)):

    === RUN   TestCloseWrite/tcp
    === PAUSE TestCloseWrite/tcp
    === CONT  TestCloseWrite/tcp
        net_test.go:174: got (0, read tcp 127.0.0.1:52579->127.0.0.1:52578: i/o timeout); want (0, io.EOF)
        net_test.go:117: got (0, read tcp4 127.0.0.1:52578->127.0.0.1:52579: i/o timeout); want (0, io.EOF)
    --- FAIL: TestCloseWrite/tcp (480.71s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ollama
Issue: Grammar support
Labels: feature request

Hello,

I understand the developers are very busy but there are several pull requests open for grammar support and it appears to be as simple as passing the value through to llama.cpp . Is it possible to get one of these pull requests merged so that it is possible to use more than just JSON.

Is there another way to support a format similar to ChatML instead of grammar, this is what I'm looking to achieve.
Repository: ant-design
Issue: Typography.Paragraph 是否可以加个去掉 marginBottom 的功能
Labels: 💡 Feature Request,Inactive,unconfirmed

### What problem does this feature solve?
`Typography.Paragraph` 有省略功能，就会用到一些场景下，但是他有个 `marginBottom: 1em` 的样式，导致样式对不齐，有些场景，不需要 `margin`。
https://stackblitz.com/edit/react-ktpvrx?file=demo.tsx
![image](https://github.com/user-attachments/assets/4d1a15f3-a484-4bdd-b25f-d5271b5b9474)


### What does the proposed API look like?

```tsx
      <Typography.Paragraph noStyle ellipsis={{ rows: 2, tooltip: {} }}>
             哈哈哈哈哈哈哈哈哈哈哈
      </Typography.Paragraph>
```
或
```tsx
      <Typography.Ellipsis rows={2} tooltip >
             哈哈哈哈哈哈哈哈哈哈哈
      </Typography.Ellipsis>
```

或
```tsx
      <Typography.Text ellipsis={{ rows: 2, tooltip: true }} >
             哈哈哈哈哈哈哈哈哈哈哈
      </Typography.Text>
```



<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ant-design
Issue: [Design Token] colorIcon doesn't work for clear icon of Input, Select and Mentions
Labels: Inactive,improvement

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-xpf1wn?file=demo.tsx)

### Steps to reproduce

Hover one of Input, Select and Mentions

### What is expected?

Clear icon color should be `red` when hover it
![image](https://github.com/user-attachments/assets/6012903d-f740-49ac-93b1-ee907a9b6f5a)

### What is actually happening?

Clear icon color is still default color when hover it
![image](https://github.com/user-attachments/assets/a9bb1922-7d2f-4025-84bf-1457f65040c0)

### Extra info

| Component | Code |
| --- | --- |
| Input | ![image](https://github.com/user-attachments/assets/4e933872-d5cd-4b89-a1a5-e1be65fc64a2) |
| Select | ![image](https://github.com/user-attachments/assets/34fdc023-7007-4557-a50a-6e1b9fddeaeb) |
| Mentions | ![image](https://github.com/user-attachments/assets/47c0e6ef-44a6-4a56-a7c4-ade166bc30f9) |

| Environment | Info |
| --- | --- |
| antd | 5.19.3 |
| React | 18.3.1 |
| System | MacOS |
| Browser | Chrome 120.0.6099.225 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: Provide an esm build for `@next/env`
Labels: bug,linear: next

### Link to the code that reproduces this issue

https://github.com/AhmedBaset/next-env-repro-esm

### To Reproduce

1. Run `node script.js`
2. Run `node script.mjs`

### Current vs. Expected behavior

`@next/env` doesn't work correctly with esm.

This cjs works as expected
```js
require("@next/env").loadEnvConfig(process.cwd());
console.log(process.env.TEST);
```

But this doesn't
```js
import { loadEnvConfig } from "@next/env";
loadEnvConfig(process.cwd());

console.log(process.env.TEST);
```
It throws:
```bash
import { loadEnvConfig } from "@next/env";
         ^^^^^^^^^^^^^
SyntaxError: Named export 'loadEnvConfig' not found. The requested module '@next/env' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@next/env';
const { loadEnvConfig } = pkg;
```

Let's try both cjs and esm in REPL
```bash
Welcome to Node.js v20.12.2.
Type ".help" for more information.

> require("@next/env")
Object [Module] {
  initialEnv: [Getter],
  updateInitialEnv: [Getter],
  processEnv: [Getter],
  resetEnv: [Getter],
  loadEnvConfig: [Getter]
}

> require("@next/env").default
undefined

> await import("@next/env")
[Module: null prototype] {
  default: Object [Module] {
    initialEnv: [Getter],
    updateInitialEnv: [Getter],
    processEnv: [Getter],
    resetEnv: [Getter],
    loadEnvConfig: [Getter]
  }
}
```

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 15774
  Available CPU cores: 12
Binaries:
  Node: 20.12.2
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // There is a newer version (14.2.5) available, upgrade recommended!
  eslint-config-next: N/A
  react: 18.3.0-canary-14898b6a9-20240318
  react-dom: 18.3.0-canary-14898b6a9-20240318
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

`@next/env`

### Which stage(s) are affected? (Select all that apply)

ESM modules

### Additional context

_No response_

As a stopgap workaround, we use esm/cjs conditionally

```js
import nextEnv from "@next/env";
import type { Config } from "drizzle-kit";

if (nextEnv && "loadEnvConfig" in nextEnv) {
  nextEnv.loadEnvConfig(process.cwd());
} else {
  // eslint-disable-next-line
  require("@next/env").loadEnvConfig(process.cwd());
}
```
Repository: ant-design
Issue: [Design Token] colorIcon doesn't work for Card, Cascader, Dropdown, Form, Input, Tabs, Tag and Upload
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-xpf1wn-x3e8dv?file=demo.tsx)

### Steps to reproduce

View the demo

### What is expected?

icon color should be `red`
![image](https://github.com/user-attachments/assets/97f93e17-8027-4bb2-97f8-b1d1768a654f)

### What is actually happening?

icon color is still default color
![image](https://github.com/user-attachments/assets/67d0e254-458f-41a6-b833-cccd9b42e081)

### Extra Info

![image](https://github.com/user-attachments/assets/5bf944e1-10d0-48a2-b74c-f85930a339db)

| Environment | Info |
| --- | --- |
| antd | 5.19.3 |
| React | 18.3.1 |
| System | MacOS |
| Browser | Chrome 120.0.6099.225 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: DISABLED test_scatter_fallback_abi_compatible_cuda (__main__.AOTInductorTestABICompatibleCuda)
Labels: triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor,module: aotinductor

Platforms: inductor, rocm



This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_scatter_fallback_abi_compatible_cuda&suite=AOTInductorTestABICompatibleCuda&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/27798437885).

Over the past 3 hours, it has been determined flaky in 3 workflow(s) with 3 failures and 3 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_scatter_fallback_abi_compatible_cuda`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/inductor/test_torchinductor.py", line 11014, in new_test
    return value(self)
  File "inductor/test_aot_inductor.py", line 2225, in test_scatter_fallback
    self.check_model(Model(), inputs)
  File "inductor/test_aot_inductor.py", line 122, in check_model
    self.assertEqual(actual, expected, atol=atol, rtol=rtol)
  File "/opt/conda/envs/py_3.8/lib/python3.8/site-packages/torch/testing/_internal/common_utils.py", line 3721, in assertEqual
    raise error_metas.pop()[0].to_error(
AssertionError: Tensor-likes are not equal!

Mismatched elements: 0 / 15 (0.0%)
Greatest absolute difference: 0 at index (0, 0)
Greatest relative difference: 0.0 at index (0, 0)

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ROCM=1 python test/inductor/test_aot_inductor.py -k AOTInductorTestABICompatibleCuda.test_scatter_fallback_abi_compatible_cuda

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `inductor/test_aot_inductor.py`

cc @clee2000 @ezyang @anijain2305 @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: go
Issue: crypto/tls: TestCrossVersionResume/TLSv12 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/tls" && test == "TestCrossVersionResume/TLSv12"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741637454497568001)):

    === RUN   TestCrossVersionResume/TLSv12
        handshake_test.go:495: failed to call cli.Close: close tcp 127.0.0.1:19506->127.0.0.1:31191: connection reset by peer
    --- FAIL: TestCrossVersionResume/TLSv12 (0.12s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Feature request: syntax-highlighting in Notebook output cells for extension-contributed custom-language grammars with `text/x-mylanguageid`
Labels: feature-request,notebook-output

As of today, authors of custom `NotebookController`s/`NotebookSerializer`s already can produce Notebook output cells as syntax-highlighted code in [one of a predefined hardcoded set of supported languages](https://github.com/microsoft/vscode/blob/6c907814bfc223e842aa0d82e69a467ce4f76223/extensions/markdown-language-features/package.json#L40-L119) only.

So if you're outputting data structures pretty-printed/syntaxed in a custom language your extension serves (with a grammar and LSP / IntelliSense), you'll have to pick one of that above-linked listing of predefined `text/x-languageid`s that comes closest to your syntax , or the one that "messes it up the least".

The idea of this feature request: just like Notebook **input** cells can _already, today_ fully benefit from extension-contributed custom-language IntelliSense **and** syntax-highlighting of their own extension-contributed language grammars, so should the **output** cell syntax-highlighting also support _any_ language grammar registered with VSCode (whether built-in or extension-provided), not just the above-linked "blessed predefined hardcoded set" of them.

Previous discussion motivating the feature request [here](https://github.com/microsoft/vscode-discussions/discussions/1251), CC @rebornix
Repository: pytorch
Issue: DataLoader worker exited unexpectedly
Labels: module: dataloader,triaged

### 🐛 Describe the bug

Traceback (most recent call last):
  File "/root/FlowFormer-Official/train_FlowFormer.py", line 174, in <module>
    train(cfg)
  File "/root/FlowFormer-Official/train_FlowFormer.py", line 84, in train
    for i_batch, data_blob in enumerate(train_loader):
  File "/root/miniconda3/envs/flownet2/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 631, in __next__
    data = self._next_data()
  File "/root/miniconda3/envs/flownet2/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1329, in _next_data
    idx, data = self._get_data()
  File "/root/miniconda3/envs/flownet2/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1295, in _get_data
    success, data = self._try_get_data()
  File "/root/miniconda3/envs/flownet2/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1146, in _try_get_data
    raise RuntimeError(f'DataLoader worker (pid(s) {pids_str}) exited unexpectedly') from e
RuntimeError: DataLoader worker (pid(s) 2535, 2850, 3039, 3228, 3354, 3480, 4498, 4561, 4687, 5128, 6267, 6708, 6771, 6897, 6960, 7212, 7275, 7338, 7464, 7590, 7905, 8913, 9039, 9165, 9354, 10425) exited unexpectedly

### Versions

Actually， when i only used two images ,it works.But when i use three images ,it failed. I tried to set the num_workers = 0,but it reported the error. So i dont know how to deal with it.Please help me.

cc @andrewkho @gokulavasan @SsnL @VitalyFedyunin @dzhulgakov
Repository: flutter
Issue: [rfw] Incorrect type in DynamicMap
Labels: package,team-ecosystem,P2,p: rfw,triaged-ecosystem

### Steps to reproduce

In rfw, `DynamicMap` is defined as

```dart
typedef DynamicMap = Map<String, Object?>;
```

### Expected results

The documentation says:

> The data obtained at runtime is known as configuration data and is represented by `DynamicContent` objects. It uses a data structure similar to JSON (but it distinguishes int and double and **does not support `null`**).

(emphasis mine)

### Actual results

`Object?` does support `null`. This type should not be used here.
Repository: godot
Issue: GDScript debugger shows incorrect values for very large positive and negative integers
Labels: bug,topic:gdscript,topic:editor

### Tested versions

- Reproduceable: v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated AMD Radeon RX 6900 XT (Advanced Micro Devices, Inc.; 32.0.11021.1011) - 12th Gen Intel(R) Core(TM) i7-12700K (20 Threads)

### Issue description

When displaying the values of integers, the GDScript debugger will show incorrect values when the integer is greater than `9223372036854775800` or less than `-9223372036854775800`. Indeed, the debugger will simply limit itself to those two values when the threshold is exceeded.

Integers in GDScript are documented to support values between `-9223372036854775808` and `9223372036854775807`. The behavior of GDScript itself appears to be correct, as printing integers containing those maximum and minimum values produces the correct output.

### Steps to reproduce

In the following function, insert a breakpoint before the first `print()` statement. Run the script in debug mode, and examine the values of `very_large` and `very_negative` in the debugger. Compare what's displayed in the debugger to the output produced by the `print()` statements.

```gdscript
func _ready():
	var very_large = 9223372036854775807
	var very_negative = -9223372036854775808
	print(very_large)
	print(very_negative)
```

### Minimal reproduction project (MRP)

[large-int-repro.zip](https://github.com/user-attachments/files/16358338/large-int-repro.zip)
Repository: go
Issue: net/http: TestTimeoutHandlerEmptyResponse/h2 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestTimeoutHandlerEmptyResponse/h2"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741563858236689873)):

    === RUN   TestTimeoutHandlerEmptyResponse/h2
    === PAUSE TestTimeoutHandlerEmptyResponse/h2
    === CONT  TestTimeoutHandlerEmptyResponse/h2
        serve_test.go:2730: got res.StatusCode 503, want 200
    --- FAIL: TestTimeoutHandlerEmptyResponse/h2 (1.62s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/tools/internal/refactor/inline: offer an option to inline all calls in a file
Labels: NeedsInvestigation,Tools,Refactoring

At the moment the inliner operates on one call at a time this limits the cleanup work the inliner can do when you want to inline all calls in a single file.

One example for such cleanups are import renames and removals. Since #67281 is fixed it now works for individual calls. However, if there are multiple calls in a single file, the problems remains. The inliner analyzer generates one diagnostic per call and the attached suggested fix needs to be self contained and correct when applied in isolation. This means if there are two calls, the inliner cannot avoid the import rename and cannot remove the import of the old package because it would make it impossible to apply the suggested fixes in isolation. Example:

```
-- path/to/old/dependency/dep.go --
package dependency
import "path/to/new/dependency"
// inlineme
func Foo() { dependency.Foo() }

-- path/to/new/dependency/dep.go --
package dependency
func Foo() {}

-- some/user/main.go --
package main
import "path/to/old/dependency"
func main() {
  dependency.Foo() // one diagnostic here
  dependency.Foo() // another diagnostic here
}
```

To solve this problem the inliner could offer a mode in which it generated one diagnostic per file with a suggested fix that inlines all calls (potentially of different functions).
Repository: vscode
Issue: Scroll momentum transferred between different scrollables
Labels: bug,trackpad/scroll

<!-- ⚠️⚠️ 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?: Yes/No

<!-- 🪓 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.91.1
- OS Version: macOS Sonoma 14.5 (23F79)
- Mouse: Apple Magic Mouse v1

Steps to Reproduce:

1. Open many tabs, to trigger overflowing into a horizontally-scrollable list
2. Open a long editor, to allow for building up scroll momentum while scrolling
3. Scroll very fast in long editor, and quickly move mouse pointer up to tabs while editor is still scrolling
4. The vertical "scroll momentum" is transferred to the tab list and becomes a fast horizontal scroll, leading to the bad UX (the tab list scrolls  away from the intended target of the user)

This happens to me multiple times a day, leading to a feeling of a very broken UX of VS Code, where there's a high uncertainty that I cannot reliably target and click on a tab (scrolling quickly in long editors is a common action for me, and I'm guessing for others too).

This does NOT happen with trackpads, because moving the cursor stops the scrolling of the editor.

https://github.com/user-attachments/assets/12548751-69a7-4901-b2c7-e31a44c88894