sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `./x check std --target aarch64-apple-ios` fails when cross-checking due to missing `xcrun`
Labels: A-cross,T-bootstrap,A-linkers

On a non-mac host, checking std for an ios target fails with the following error:

```
> ./x check std --target aarch64-apple-ios                                                                                                                          
Building bootstrap
    Finished `dev` profile [unoptimized] target(s) in 0.8s


error occurred: Failed to find tool. Is `xcrun` installed? (see https://docs.rs/cc/latest/cc/#compile-time-requirements for help)


Build completed unsuccessfully in 0:00:01
```

Ideally I should be able to check any target from any host.
Repository: vscode
Issue: Explore app group containers for user data isolation
Labels: feature-request,macos

App group containers overview https://developer.apple.com/videos/play/wwdc2024/10123/?time=743

We cannot apply the isolation to all files in the user data since there are files shared by the runtime and also we need specific apis to read/write data to/from the container.

Upstream issue - https://issues.chromium.org/issues/366381674

See if we can move a subset of vscode owned data into the container as part of this exploration

/cc @isidorn
Repository: pytorch
Issue: Python 3.12 "from functorch.einops import rearrange" fails with "RuntimeError: First class dim doesn't work with python 3.12" 
Labels: triaged,module: regression,module: functorch

### 🐛 Describe the bug

Python 3.12 Nightly binary (e.g.  wget https://download.pytorch.org/whl/nightly/cu126/torch-2.6.0.dev20241119%2Bcu126-cp312-cp312-linux_x86_64.whl )  fails with 

`import functorch 
from functorch.einops import rearrange`  

 python3 -c "import functorch; from functorch.einops import rearrange"  
/usr/local/lib/python3.12/dist-packages/torch/_subclasses/functional_tensor.py:295: UserWarning: Failed to initialize NumPy: No module named 'numpy' (Triggered internally at /pytorch/torch/csrc/utils/tensor_numpy.cpp:81.)
  cpu = _conversion_method_template(device=torch.device("cpu"))
RuntimeError: First class dim doesn't work with python 3.12

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/local/lib/python3.12/dist-packages/functorch/einops/__init__.py", line 1, in <module>
    from .rearrange import rearrange
  File "/usr/local/lib/python3.12/dist-packages/functorch/einops/rearrange.py", line 7, in <module>
    from functorch._C import dim as _C
ImportError: initialization failed
root@~# pip list |grep torch
pytorch-triton           3.1.0+cf34004b8a
torch                    2.6.0.dev20241119+cu126


It also reproduces with: 
pytorch-triton           3.2.0+git35c6c7c6
torch                    2.6.0.dev20241203+cu126 (i.e. nightly as of today)

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @Chillee @samdow @kshitij12345 @atalman @malfet @ptrblck @eqy @tinglvv @xwang233 

### Versions

e.g. 2.6.0.dev20241119+cu126 and  torch                    2.6.0.dev20241203+cu126
Repository: next.js
Issue: Next lint doesn't give warning of unused dependencies in other places than pages/components
Labels: bug,Linting

### Link to the code that reproduces this issue

https://github.com/Harsh-Sharma25/lint-issue-next

### To Reproduce

1. pnpm i
2. pnpm lint
& then if you run `pnpm eslint .` you will see the difference.

### Current vs. Expected behavior

When you run `pnpm lint` which in turn runs next lint it doesn't gives warning for missing dependencies in the hooks folder but if you define a hook inside pages then it does. `pnpm eslint .` seems to give proper warnings.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 16077
  Available CPU cores: 16
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: 9.14.2
Relevant Packages:
  next: 15.0.4-canary.37 // Latest available version is detected (15.0.4-canary.37).
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Linting

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

### Additional context

My original project is not on canary release, it is on 15.0.3 and it also doesn't use react 19 rc, which is when I encountered this issue. I've also tested with the eslint version: 9.15.0.
Repository: ui
Issue: [bug]:  Syntax Issue in Generated tailwind.config.ts from `pnpm dlx shadcn@latest init`
Labels: bug

### Describe the bug

The `tailwind.config.ts` generated by `pnpx shadcn@latest init` contains syntax issues, writing \n as a string.
![screenshot_2024-12-04_11-36-19](https://github.com/user-attachments/assets/475fbcd6-ee55-44cf-ad69-857a376afed7)


### Affected component/components

tailwind.config.ts

### How to reproduce

1. create-remix
2. npx shadcn@latest init
3. select new york , neutral.
4. check tailwind.config.ts

### Codesandbox/StackBlitz link

https://stackblitz.com/edit/remix-run-remix-fop74u?file=tailwind.config.ts

### Logs

_No response_

### System Info

```bash
linux,zed editor.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [bug]: Website broken: https://ui.shadcn.com/blocks
Labels: bug

### Describe the bug

Blocks part of the documentation website does not work (https://ui.shadcn.com/blocks).

All blocks are blanks, console log gets filled with "Minified React error ..." messages.

### Affected component/components

Website documentation

### How to reproduce

1. Go to https://ui.shadcn.com/blocks
2. Try to view any block

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Tested in Chrome (including incognito) and Safari
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ollama
Issue: Multiple ollama_llama_server process are created and then not released
Labels: bug

### What is the issue?

In the process of use, after a period of time through nvidia-smi view, there will be multiple processes using the GPU, but only one of these processes actually works. You can confirm this by using the ollama ps command
![screen_shot](https://github.com/user-attachments/assets/d5799b73-6ed0-4b0b-8c61-fcc2531e0e50)
Refer to the above pic, only the 2115700 process is valid, and it is clear that there are two other processes 1990922,2036868 that occupy a fixed size GPU memory, and another process 2117261 is still running..

### OS

Linux

### GPU

Nvidia

### CPU

Other

### Ollama version

0.3.5
Repository: rust
Issue: `macro!();` statements sometimes don't seem to include `;` in `stmt.span` (HIR)
Labels: A-diagnostics,T-compiler,A-HIR,C-bug,E-needs-investigation

cc #133833 and #133834 in suggestions such as

```rs
#![crate_type = "lib"]

fn foo() -> String {
    let mut bar = {
        unknown_macro!();
    };
    return bar;
}
```

Opened while looking at #133843 to not lose the FIXME.
Repository: transformers
Issue: `trainer.evaluate` always creates a new MLFlow run, separate from the one used during `train()`
Labels: bug

### System Info

`transformers` version: 4.46.1
`mlflow==2.18.0`

I have confirmed this on my local machine (mac) and our training cluster (8x H100 using standard nvcr image), using a local and external MLFlow tracking server, so this is not likely to be very environment dependent outside the above.

### Who can help?

_No response_

### Information

- [ ] The official example scripts
- [X] My own modified scripts

### Tasks

- [X] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

```py
from time import sleep

from transformers import Trainer, TrainingArguments, AutoModelForSequenceClassification, AutoTokenizer
from datasets import load_dataset
import mlflow
import os


with mlflow.start_run() as run:
    run_id = run.info.run_id
os.environ["MLFLOW_RUN_ID"] = run_id
print("Original run id:", run_id)

# Load a pre-trained model and tokenizer
model_name = "distilbert-base-uncased"
model = AutoModelForSequenceClassification.from_pretrained(model_name, num_labels=2)
tokenizer = AutoTokenizer.from_pretrained(model_name)

# Load a small dataset
dataset = load_dataset("imdb", split="train[:100]")

# Tokenize the dataset
def tokenize(batch):
    return tokenizer(batch['text'], padding=True, truncation=True, max_length=128)

tokenized_dataset = dataset.map(tokenize, batched=True)

# Define training arguments
training_args = TrainingArguments(
    output_dir="./results",
    evaluation_strategy="epoch",
    per_device_train_batch_size=8,
    per_device_eval_batch_size=8,
    num_train_epochs=1,
    logging_steps=1,
    report_to="mlflow"
)

# Initialize Trainer
trainer = Trainer(
    model=model,
    args=training_args,
    train_dataset=tokenized_dataset,
    eval_dataset=tokenized_dataset,
)

# Train the model
trainer.train()

# Evaluate the model
eval_results = trainer.evaluate()
print(eval_results)

sleep(10)
runs_dir = "./mlruns/0"
runs = [x for x in os.listdir(runs_dir) if x != "meta.yaml"]
for run_id in runs:
    print(f"Metric files for {run_id}")
    metrics_path = os.path.join(runs_dir, run_id, "metrics")
    print(*os.listdir(metrics_path), sep="\n")
    print("="*16)
```
Running the above script should confirm that two separate runs are created, and that metrics files are placed in each.

### Expected behavior

I expected that all logging would be pushed to the existing run ID (unless there is a reason that this is not the case).

Apologies if this is documented behaviour, but I could not find a reason.
Repository: vscode
Issue: $CURRENT_TIME_UTC in snippet
Labels: feature-request,snippets

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

Hello,

I appreciate the functionality in vscode that enables the insertion of variables within snippets, particularly the $CURRENT_* variables that allow for the effective inclusion of date and time. This feature, including the timezone offset for indicating the current timezone, is quite useful. However, I am keen on having an additional variable, $CURRENT_*_UTC, which would provide the current date and time based on Coordinated Universal Time (UTC).
Repository: kubernetes
Issue: When kube-apiserver list is used, the maximum message size is 4 GB. A single message may exceed the limit.
Labels: kind/support,needs-sig,needs-triage

### What happened?

When I create more than 10000 secrets, and per secret size is more than 400KB,than kube-apiserver will report warning,and my cluster can't work well
![image](https://github.com/user-attachments/assets/a1221f65-9018-444a-984a-65741667c708)
The page size of kube-apiserver list is 10000. Can I change the page size adaptively each time?
![image](https://github.com/user-attachments/assets/052ff946-fd2c-4eda-bce9-a5aac93e21cf)


### What did you expect to happen?

cluster work well

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

create secret more than 10000,and per secret size more than 400kb

### Anything else we need to know?

_No response_

### Kubernetes version

<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: rust
Issue: Incorrect rustdoc rendering of const generic default
Labels: T-rustdoc,C-bug,A-const-generics,A-cross-crate-reexports

I tried this code:

https://doc.rust-lang.org/nightly/std/mem/trait.TransmuteFrom.html

```rust
pub unsafe trait TransmuteFrom<Src, const ASSUME: Assume = { Assume::NOTHING }> where Src: ?Sized {}
```

I expected to see this happen: Renders identically to the above in the rustdoc output.

Instead, this happened: Renders as

```rust
pub unsafe trait TransmuteFrom<Src, const ASSUME: Assume = core::::mem::transmutability::TransmuteFrom::{constant#0}> where Src: ?Sized {}
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version`:
```
1.85.0-nightly (c44b3d50f 2024-12-03)
```
Repository: ui
Issue: [bug]: Issue Initializing ```shadcn``` in ```Next.js``` When axios Is Installed
Labels: bug

### Describe the bug

When initializing `shadcn` in a Next.js project, the process fails if `axios` is installed beforehand. The error indicates that the socket connection was unexpectedly closed during the registry check. Removing `axios` resolves the issue, and `shadcn` initializes successfully.  

---

### Bug Description  
- **Error Message:**  
   ```  
   The socket connection was closed unexpectedly. For more information, pass `verbose: true` in the second argument to fetch().  
   ```  
- The problem seems to stem from a conflict between `axios` and the shadcn initialization process.  

---


### Affected component/components

Core shadcn initialization script

### How to reproduce

1. Set up a new Next.js project.  
2. Install `axios` using Bun:  
   ```bash  
   bun add axios  
   ```  
3. Attempt to initialize `shadcn` using:  
   ```bash  
   bunx --bun shadcn@latest init -d  
   ```  
4. Observe the error.  

#### Resolution Steps:  
1. Remove `axios` using:  
   ```bash  
   bun remove axios  
   ```  
2. Retry the shadcn initialization:  
   ```bash  
   bunx --bun shadcn@latest init -d  
   ```  


### Codesandbox/StackBlitz link

N/A

### Logs

```bash
**Before removing `axios`:**  
  
✔ Preflight checks.  
✔ Verifying framework. Found Next.js.  
✔ Validating Tailwind CSS.  
✔ Validating import alias.  
✔ Writing components.json.  
⠹ Checking registry.  
The socket connection was closed unexpectedly. For more information, pass `verbose: true` in the second argument to fetch().  
```
  

**After removing `axios`:**  
```console  
✔ Preflight checks.  
✔ Verifying framework. Found Next.js.  
✔ Validating Tailwind CSS.  
✔ Validating import alias.  
✔ Writing components.json.  
✔ Checking registry.  
✔ Updating tailwind.config.ts  
✔ Updating app\globals.css  
✔ Installing dependencies.  
✔ Created 1 file:  
  - lib\utils.ts  

Success! Project initialization completed.  
You may now add components.  
```


### System Info

```bash
- **OS:** Windows 10 
- **Bun Version:** 1.1.36  
- **Node Version:** 20.12.2  
- **shadcn Version:** Latest (at the time of the issue)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: next.js
Issue: Client components wrapped in React.memo rendered by a server component remount unexpectedly
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/wispy-leftpad-9scxwl?workspaceId=ws_TBJMVdGvaGCmBYC6VerWKV

### To Reproduce

In the provided example, click the "router.refresh()" button to observe the unexpected remount behavior of memo-ed components.

Details are given directly in the provided example. For completeness, this is a copy of the explanation in the example:

<p>
        All components here are client components that use the same base
        component logging into the console when it is mounted and unmounted and
        updating an internal counting state every 500ms. All components are
        children of the same server component.
      </p>
      <div>
        The differences are:
        <ul>
          <li>Normal: Nothing special, only renders the base component</li>
          <li>Memo: Same as normal, but wrapped in React.memo</li>
          <li>
            Indirect Memo: Normal component that renders a second component that
            is wrapped in React.memo
          </li>
        </ul>
      </div>
      <p>
        When you hit the "router.refresh()" button, you can observe, that the
        "Memo" component is remounted (see console and resetted state), which is
        an unexpected behavior.
      </p>
      <p>
        You can observe that this is not happening for "Indirect Memo". It only
        seems to affect components wrappend in React.memo that are directly
        rendered from a server component.
      </p> 

### Current vs. Expected behavior

The component wrapped in React.memo remounts when the server component rerenders, here triggered with router.refresh().

The expected behavior would be, that it behaves like the other components and just rerenders, but not remounts.

### 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.0.4-canary.37 // Latest available version is detected (15.0.4-canary.37).
  eslint-config-next: N/A
  react: 19.0.0-rc-b01722d5-20241114
  react-dom: 19.0.0-rc-b01722d5-20241114
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

I tested this in next 14 and 15 (15.0.4-canary.37) and was able to reproduce it with both versions.
Repository: flutter
Issue: In reverse mode, the `localToGlobal` method of `SliverMainAxisGroup`'s children returned incorrect positions.
Labels: framework,f: scrolling,has reproducible steps,P2,has partial patch,team-framework,triaged-framework,found in release: 3.24,found in release: 3.27

### Steps to reproduce

```dart
import 'package:flutter/material.dart';

GlobalKey key = GlobalKey();
void main() {
  runApp(
    MaterialApp(
      home: Scaffold(
        body: Align(
          alignment: Alignment.topLeft,
          child: SizedBox(
            height: 400,
            child: CustomScrollView(
              reverse: true,
              slivers: [
                SliverMainAxisGroup(
                  slivers: [
                    SliverToBoxAdapter(child: Container(height: 70, color: Colors.red)),
                    SliverToBoxAdapter(
                      child: SizedBox(
                        height: 20,
                        child: Text("1", key: key),
                      ),
                    ),
                    SliverToBoxAdapter(child: Container(height: 700, color: Colors.blue)),
                  ],
                ),
              ],
            ),
          ),
        ),
        floatingActionButton: IconButton(
          onPressed: () {
            RenderBox rb = key.currentContext!.findRenderObject() as RenderBox;
            print(rb.localToGlobal(Offset.zero));
          },
          icon: const Icon(Icons.add),
        ),
      ),
    ),
  );
}
```
Run the code above and click the button.

### Expected results

Output: Offset(0.0, 310.0).

### Actual results

Output: Offset(0.0, 70.0).


### Screenshots or Video

![image](https://github.com/user-attachments/assets/138f1e16-039e-484a-b5e0-a7b438ef968d)


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel [user-branch], 3.27.0-1.0.pre.699, on macOS 15.1 24B83 darwin-arm64, locale zh-Hans-CN)
    ! Flutter version 3.27.0-1.0.pre.699 on channel [user-branch] at /Users/10906/source/repo/github/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[!] Xcode - develop for iOS and macOS (Xcode 16.1)
    ! CocoaPods 1.15.2 out of date (1.16.2 is recommended).
        CocoaPods is a package manager for iOS or macOS platform code.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/to/platform-plugins
      To update CocoaPods, see https://guides.cocoapods.org/using/getting-started.html#updating-cocoapods
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.95.3)
[✓] VS Code (version 1.94.2)
[!] Proxy Configuration
    ! NO_PROXY is not set
[✓] Connected device (5 available)
[✓] Network resources

! Doctor found issues in 3 categories.
```

</details>
Repository: react
Issue: Bug: useState apply updaters order does not comply with the documentation
Labels: Status: Unconfirmed

React version: 16 & 18

## Steps To Reproduce
1. Call setState(functional updater) twice
2. One of the updater will be calculated before re-render.

Link to code example: https://codesandbox.io/p/sandbox/quizzical-hugle-wsp7zh

## The expected behavior
As per the [documentation of setState](https://react.dev/reference/react/useState#setstate),
> If you pass a function as nextState, it will be treated as an updater function. It must be pure, should take the pending state as its only argument, and should return the next state. 
> **React will put your updater function in a queue and re-render your component. During the next render, React will calculate the next state by applying all of the queued updaters to the previous state.**

Expected behaviour is,
1. click on the button
2. enqueue two updater actions
3. the App component re-renders
4. (when visiting useState) apply two actions
5. get the updated new value
 
## The current behavior
However the current behavior is,
1. click on the button
2. one of the actions is calculated IMMEDIATELY, the rest are enqueued.
3. the App component re-renders
4. (when visiting useState) apply the remaining actions
5. get the updated new value

![image](https://github.com/user-attachments/assets/8a0ff342-b155-44bb-884d-9c44a13a4db9)


## Note
Only the *first* time not complying. From the second time it works expectedly.
![image](https://github.com/user-attachments/assets/f80e96ef-0396-452e-9e05-f4c922f15f90)