sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Next/font does not work with Turbopack in a containerized development environment
Labels: bug,Font (next/font),Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/jmotes/next-font-bug/

### To Reproduce

Run these commands to build the image and launch the app:

```
docker build -t next-font-bug .
docker run -p 3000:3000 next-font-bug
```

### Current vs. Expected behavior

Current behavior:

```
 ⚠ [next]/internal/font/google/inter_59dee874.module.css
Error while requesting resource
There was an issue establishing a connection while requesting https://fonts.googleapis.com/css2?family=Inter:wght@100..900&display=swap.
```

Expected: load up the Google Font correctly.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: arm64
  Version: #1 SMP Sun Jun 23 23:24:08 UTC 2024
  Available memory (MB): 7933
  Available CPU cores: 10
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Font (next/font), Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

The issue is only reproducible when using `next dev --turbo`. While setting up the minimal reproduction I noticed that the `node:20-alpine` image works just fine, however we can also reproduce the issue with a `wordpress:php8.2-apache` based container too (with Node 20 installed in it), which is where we load up our VS Code Workspace.

This has been mentioned before in issues like https://github.com/vercel/next.js/issues/47802
Repository: terminal
Issue: Draw a horizontal line / ruler between commands (read: blocks )
Labels: Issue-Feature,Area-UserInterface,Area-TerminalControl,Product-Terminal

# Description of the new feature/enhancement

I recently decided to start developing my dream terminal for Windows. However, since I'm not a professional developer and the development will take quite a long time, I thought: "Why let the concepts go to waste?" Perhaps this will be at least somewhat useful for Windows Terminal developers.

## Concepts:

> ![Blocks](https://github.com/microsoft/terminal/assets/42640/d247c0c6-6dc1-4dfc-bdd3-d0c571acba72)
> Dividing results into blocks

> ![History](https://github.com/microsoft/terminal/assets/42640/163a4cf2-a3f3-4c45-86db-a6f846984e62)
> Commands history

> ![Autocomplete](https://github.com/microsoft/terminal/assets/42640/57d091c9-5a78-4299-b35f-451c86a44c32)
> Autocomplete

> ![Terminika](https://github.com/microsoft/terminal/assets/42640/a1880e9f-8ab0-48e0-a796-0c709fb39b71)
> Default window with entered command

## P.S.
If anyone can give me a hint on how to theoretically capture process output and divide it into blocks from the output stream of a Windows pseudoconsole, I would be very grateful.

Thank you for your attention.
Repository: rust
Issue: confusing error when trying to call a not-in-scope method that shares a name with a field
Labels: A-diagnostics,T-compiler

### Code

```Rust
struct Struct { x: u8 }

mod m {
    trait GetX {
        fn x(&self) -> u8;
    }
    
    impl GetX for super::Struct {
        fn x(&self) -> u8 {
            self.x
        }
    }
}

pub fn show_x(st: Struct) {
    println!("{}", st.x())
}
```


### Current output

```Shell
error[E0599]: no method named `x` found for struct `Struct` in the current scope
  --> src/lib.rs:16:23
   |
1  | struct Struct { x: u8 }
   | ------------- method `x` not found for this struct
...
16 |     println!("{}", st.x())
   |                       ^ field, not a method
   |
   = help: items from traits can only be used if the trait is implemented and in scope
help: remove the arguments
   |
16 -     println!("{}", st.x())
16 +     println!("{}", st.x)
   |
help: trait `GetX` which provides `x` is implemented but not in scope; perhaps you want to import it
   |
1  + use crate::m::GetX;
   |
```


### Desired output

```Shell
error[E0599]: no method named `x` found for struct `Struct` in the current scope
  --> src/lib.rs:16:23
   |
1  | struct Struct { x: u8 }
   | ------------- method `x` not found for this struct
...
16 |     println!("{}", st.x())
   |                       ^ field, method not in-scope
   |
   = help: items from traits can only be used if the trait is implemented and in scope
help: trait `GetX` which provides `x` is implemented but not in scope; perhaps you want to import it
   |
1  + use crate::m::GetX;
   |
help: remove the arguments
   |
16 -     println!("{}", st.x())
16 +     println!("{}", st.x)
   |
```


### Rationale and extra context

_No response_

### Other cases

```Rust
there should also be a unit test to make sure the output makes since when the field is not available directly, but instead by `Deref` coercion.  it is extremely confusing to see "field, not a method" when a type's documentation lists it as a method, but not a field.
```


### Rust Version

```Shell
rustc 1.81.0-nightly (8337ba918 2024-06-12)
binary: rustc
commit-hash: 8337ba9189de188e2ed417018af2bf17a57d51ac
commit-date: 2024-06-12
host: x86_64-unknown-linux-gnu
release: 1.81.0-nightly
LLVM version: 18.1.7
```


### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"surechen"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Flutter Web Apps fails to run in Brave Browser with Shields Up
Labels: platform-web,has reproducible steps,P3,team-web,triaged-web,found in release: 3.22,found in release: 3.23

### **Issue**
Flutter web applications are unable to run in the Brave browser when the shields are up. This issue impacts the usability and accessibility of Flutter web apps for users who prefer the Brave browser with its default privacy and security settings.

### **Steps to Reproduce**
1. Deploy a Flutter web app to a production environment.
2. Open the deployed Flutter web app in the Brave browser.
3. Ensure that the Brave browser shields are turned on (default setting).
4. Observe that the Flutter web app fails to load or function properly.

### **Expected Behavior**:
The Flutter web app should load and function correctly in the Brave browser with shields up, similar to how it operates in other major browsers (e.g., Chrome, Firefox, Safari).

### **Actual Behavior**:
The Flutter web app either fails to load entirely or exhibits significant functionality issues when accessed through the Brave browser with shields up.

### **Additional Information**:
- The issue is reproducible with multiple Flutter web apps.
- Disabling shields in the Brave browser resolves the issue, indicating that the problem is related to the browser's privacy and security settings.
- This issue is affecting a significant portion of users ( Approx. 67.7 million people ) who use Brave as their primary browser with shields enabled for enhanced privacy and security.
![Screenshot from 2024-06-30 23-55-41](https://github.com/flutter/flutter/assets/90713896/04bc62fb-dbca-4123-80c4-e9e2b8bcacde)


### **Environment**:
- Flutter version
   ```
   Flutter 3.19.0 • channel stable • https://github.com/flutter/flutter.git
  Framework • revision bae5e49bc2 (5 months ago) • 2024-02-13 17:46:18 -0800
  Engine • revision 04817c99c9
  Tools • Dart 3.3.0 • DevTools 2.31.1
   ```
- Brave browser version
   `Version 1.67.123 Chromium: 126.0.6478.126 (Official Build)`

- Operating System
   ```
   OS: Fedora Linux 40 (Workstation Edition) x86_64 
   Host: TUF Gaming FX505DT
   Kernel: 6.9.4-200.fc40.x86_64 
   ```
### **Workaround**:
Currently, the only workaround is to instruct users to disable shields in the Brave Browser, which is not ideal from a privacy and security perspective.

### **Request**:
Investigate the compatibility issues between Flutter web apps and the Brave browser with Shields Up, and provide a solution or guidance on how to ensure Flutter web apps can function correctly without compromising user privacy and security.

#### _**Given that approximately 67 million people are using the Brave browser, resolving this issue is crucial to maintain and expand the user base for Flutter web apps. This is a very severe issue, so please address it with High Priority and Urgency.**_
Repository: rust
Issue: Clang linker script support - incorrect argument
Labels: A-linkage,A-codegen,T-compiler,C-bug

Using `clang` as linker with any custom target (spec in json) that contains linker-script (field `link-script`) produces invocation like 
```bash
# clang or cc, or gcc
"clang" "--script" "/path/to/link-script/exported/from/my-target-json"
```

But `clang` doesn't support `--script` and returns error `clang: error: unsupported option '--script'`.
Instead of that, according [documentation](https://clang.llvm.org/docs/ClangCommandLineReference.html#cmdoption-clang-T-script), we just need to pass it with `-T`, 
e.g.: `-T/path/to/link-script.ld`.

How to reproduce:

1. Prepare spec json file for your custom target. It could be anything, just one thing matter - add `link-script` field. Something like this:
    ```json
    {
      "llvm-target": "Your-HOST-target",
      "link-script": "ENTRY(main)",
      "linker": "clang"
    }
    ```

2. Compile anything targeting to your custom target, e.g.: `--target=./your-target.json`

Expected result:
Clang should be invoked with `-T<link-script>` instead of `--script <link-script>`.


I can reproduce with target-spec with explicitly set linker as `clang`, `gcc`, `arm-none-eabi-gcc` and `cc`.


### Meta

`rustc --version --verbose`:
```
rustc 1.80.0-nightly (72fdf913c 2024-06-05)
binary: rustc
commit-hash: 72fdf913c53dd0e75313ba83e4aa80df3f6e2871
commit-date: 2024-06-05
host: aarch64-apple-darwin
release: 1.80.0-nightly
LLVM version: 18.1.6
```
Repository: godot
Issue: TextEdit: Text not shown with too many tabs and `indent_wrapped_lines`
Labels: bug,topic:gui

### Tested versions

Godot v4.3.beta (4ab8fb809)

### System information

Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 (NVIDIA; 31.0.15.5186) - Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 Threads)

### Issue description

- related https://github.com/godotengine/godot/pull/88546
- I found this while looking into https://github.com/godotengine/godot/issues/93762

If you have `indent_wrapped_lines` enabled and a line after many tabs, it doesn't get wrapped anymore. It tries to put the text after the indentation to match the first line, but there is too much and the text can't be shown. 
It should reset the indent count if there is too many.

![image](https://github.com/godotengine/godot/assets/10054226/b2b86d9a-c7d8-4f4e-9ddf-0c854a1d1d83)



### Steps to reproduce

1. Make sure word wrap and `indent_wrapped_lines` is on.
2. Have a script with text after many tabs or spaces so it goes out of view, like `																														 	#test`

### Minimal reproduction project (MRP)

N/A
Repository: ollama
Issue: CUBLAS_STATUS_ALLOC_FAILED with deepseek-coder-v2:16b
Labels: bug,nvidia,memory

### What is the issue?

when running deepseek-coder-v2:16b on NVIDIA GeForce RTX 3080 Laptop GPU, I have this crash report:
```
Error: llama runner process has terminated: signal: aborted (core dumped) CUDA error: CUBLAS_STATUS_ALLOC_FAILED
  current device: 0, in function cublas_handle at /go/src/github.com/ollama/ollama/llm/llama.cpp/ggml-cuda/common.cuh:826
  cublasCreate_v2(&cublas_handles[device])
GGML_ASSERT: /go/src/github.com/ollama/ollama/llm/llama.cpp/ggml-cuda.cu:100: !"CUDA error"
```
if I run "16b-lite-instruct-q8_0" version, it works just fine.

### OS

Linux

### GPU

Nvidia, AMD

### CPU

AMD

### Ollama version

0.1.48
Repository: angular
Issue: ADEV: Angular DevTools page is missing a section about hydration support
Labels: P3,area: docs

### Describe the problem that you experienced

In Angular v17.2.0, we've introduced hydration support in DevTools, see additional info in [this blogpost](https://blog.angular.dev/angular-v17-2-is-now-available-596cbe96242d). It'd be great to add a section to the existing DevTools page on ADEV to describe this feature (including a couple screen shots):

- Illustrate how to check a status of each component
- Illustrate hydration mismatch errors
- Mention hydration overlay

### Enter the URL of the topic with the problem

https://angular.dev/tools/devtools
Repository: angular
Issue: ADEV: rework "Programmatically rendering components" section to mention `@defer`
Labels: P3,area: docs-infra

### Describe the problem that you experienced

Since v18, `@defer` became a stable feature and can be used in many use-cases where `NgComponentOutlet` and `ViewContainerRef` were previously used. The "Programmatically rendering components" section can be reworked to show an example of NgComponentOutlet (we can probably drop the `ViewContainerRef` example, potentially moving it to the "Usage notes" of the `ViewContainerRef.createComponent` function itself) and after that we can show how defer loading can be achieved via `@defer`.

### Enter the URL of the topic with the problem

https://angular.dev/guide/components/programmatic-rendering
Repository: pytorch
Issue: MPS Sparse Support
Labels: module: sparse,triaged,enhancement,module: mps

### 🚀 The feature, motivation and pitch

I would like to be able to use `torch.sparse` on Metal, which currently breaks:
```
import torch

assert(torch.backends.mps.is_available())
mps_device = torch.device("mps")

crow_indices = torch.tensor([0, 2, 4], dtype=torch.int32).to(mps_device)
col_indices = torch.tensor([0, 1, 0, 1], dtype=torch.int32).to(mps_device)
values = torch.tensor([1, 2, 3, 4], dtype=torch.float32).to(mps_device)
csr = torch.sparse_csr_tensor(crow_indices, col_indices, values, dtype=torch.float32)
```
with the following error:
```
% python3 file.py
Traceback (most recent call last):
  File "file.py", line 9, in <module>
    csr = torch.sparse_csr_tensor(crow_indices, col_indices, values, dtype=torch.float32)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NotImplementedError: Could not run 'new_compressed_tensor' from the 'mps:0' device.)
```

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen
Repository: pytorch
Issue: Concatenating CSR matrices fails
Labels: module: sparse,triaged

### 🐛 Describe the bug

The [torch.sparse documentation](https://pytorch.org/docs/stable/sparse.html#other-functions) claims to support (among others), `cat`, `stack`, `vstack`, and `hstack`. None of these functions work on CSR matrices, failing with `RuntimeError: Sparse CSR tensors do not have is_contiguous`.

```python
import torch

crow_indices = torch.tensor([0, 2, 4], dtype=torch.int32)
col_indices = torch.tensor([0, 1, 0, 1], dtype=torch.int32)
values = torch.tensor([1, 2, 3, 4], dtype=torch.float32)
A = torch.sparse_csr_tensor(crow_indices, col_indices, values, dtype=torch.float32)

# Each of these fail
print(torch.hstack((A, A)))
print(torch.vstack((A, A)))
print(torch.cat((A, A), dim=0))
print(torch.cat((A, A), dim=1))
print(torch.stack((A, A)))
```
Here is the backtrace for the first failure:
```bash
% python3 file.py
file.py:6: UserWarning: Sparse CSR tensor support is in beta state. If you miss a functionality in the sparse tensor support, please submit a feature request to https://github.com/pytorch/pytorch/issues. (Triggered internally at /Users/runner/work/pytorch/pytorch/pytorch/aten/src/ATen/SparseCsrTensorImpl.cpp:55.)
  A = torch.sparse_csr_tensor(crow_indices, col_indices, values, dtype=torch.float32)
Traceback (most recent call last):
  File "file.py", line 9, in <module>
    print(torch.hstack((A, A)))
          ^^^^^^^^^^^^^^^^^^^^
RuntimeError: Sparse CSR tensors do not have is_contiguous
```

### Versions

Collecting environment information...
PyTorch version: 2.3.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.4.1 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.3.9.4)
CMake version: version 3.29.2
Libc version: N/A

Python version: 3.12.3 (main, Apr  9 2024, 08:09:14) [Clang 15.0.0 (clang-1500.1.0.2.5)] (64-bit runtime)
Python platform: macOS-14.4.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M1 Pro

Versions of relevant libraries:
[pip3] numpy==2.0.0
[pip3] torch==2.3.1
[conda] Could not collect

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: tauri
Issue: [feat] Catch tauri errors
Labels: type: feature request

### Describe the problem

Some users have an old version of webview2. if it's too old, the internal function create_webview will fail to run, tauri will log the error, but the app will still run in the background without show any error or crash the thread.

### Describe the solution you'd like

Let me catch such errors. currently I don't get anything from it. I even have a panic hook, but it doesn't kick in since seems like the event loop just keep runing.

### Alternatives considered

-

### Additional context

https://github.com/thewh1teagle/vibe/issues/153#issuecomment-2198800744
Repository: pytorch
Issue: vmap + autograd.Function [generate_vmap_rule=True] + torch.compile don't work together
Labels: triaged,oncall: pt2,module: dynamo,module: pt2-dispatcher,dynamo-autograd-function

### 🚀 The feature, motivation and pitch

Run `pytest test/inductor/test_flex_attention.py -k test_autograd_function_in_score_mod`

comment out https://github.com/pytorch/pytorch/blob/a21d4363d2ef325c0808ed6a03f8def15c0abd7e/test/inductor/test_flex_attention.py#L1056

<img width="1477" alt="image" src="https://github.com/pytorch/pytorch/assets/6355099/19fdb24f-e500-4b6f-be9a-212b4ff8fd34">


cc: @zou3519 @oulgen 

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @zou3519 @bdhirsh @anijain2305
Repository: node
Issue: TypeError: ssl.destroySSL is not a function
Labels: tls

### Version

v20.13.1

### Platform

```text
4.14.345-262.561.amzn2.x86_64 #1 SMP Fri May 31 18:15:42 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Running inside Docker image built from docker.io/node:20.13.1-bookworm-slim
```


### Subsystem

tls

### What steps will reproduce the bug?

_No response_

### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior? Why is that the expected behavior?

_No response_

### What do you see instead?

```
node:_tls_wrap:650
      ssl.destroySSL();
          ^

TypeError: ssl.destroySSL is not a function
    at TCP.done (node:_tls_wrap:650:11)
```

### Additional information

Randomly throughout the day, multiple Node.js instances from our fleet of servers are simultaneously terminating after throwing the error with the provided stack trace pointing towards [this ssl.destroySSL() call in _tls_wrap.js](https://github.com/nodejs/node/blob/v20.13.1/lib/_tls_wrap.js#L650).

We're not 100% sure that this is a bug in Node.js since we weren't able to pinpoint this issue to a specific part of our codebase and couldn't find a reproduction case yet but we plan on rolling out an update that enables the `NODE_DEBUG=tls` option to gather more information.
Repository: TypeScript
Issue: Extend type predicate inference to work with certain type variables
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

type predicate inference generic

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

When a function would normally serve as a type predicate for a discriminated union, but the exact cases being selected by the type predicate are dictated by a type variable, it'd be nice if the type predicate could still be inferred.

### 📃 Motivating Example

```ts
type Thing = A | B | C
type A = { kind: 'A', id: string, /* ... */ }
type B = { kind: 'B', id: string, /* ... */ }
type C = { kind: 'C', id: string, /* ... */ }

function filterByKind<T extends Thing['kind']>(things: Thing[], kind: T) {
  return things.filter((it) => it.kind === kind);
}

// The below would ideally be typed as `A[]`, as the function passed to 
// `filter` would have an inferred type predicate of `it is Thing & { kind: T }`
const x = filterByKind([], 'A');

const someKind = Math.random() < .5 ? 'A' : 'B';
const y = filterByKind([], someKind); // (A | B)[]
```

### 💻 Use Cases

I think this comes up somewhat rarely, and the workaround is to simply manually write out the generic type predicate, but, at my company, we did find cases like this when we looked at our type predicates as part of upgrading to TS 5.5