sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Renaming the distDir and using "output: export" seems to render "npm run start" unusable
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/npm-run-start-broken-t9z2fd

### To Reproduce

1. I start clean by deleting both the `.next` and `build` folders if present.
2. Run the "build" task; this runs `npm run build` which runs `next build`
3. `.next` and `build` folders are created successfully. Run the "prod" task; this runs `npm run start` which runs `next start`
4. Error propagates

### Current vs. Expected behavior

I am trying to test my production build locally. We are using static exports for our application and we have renamed the typical "out" folder to "build" in `next.config.mjs`. Everything builds successfully (and I have deployed it on production just fine), but running `npm run start` (which is really `next start`) cannot seem to find the production build. 

I get this error:
```
Error: Could not find a production build in the 'build' directory. 
Try building your app with 'next build' before starting the production server.
https://nextjs.org/docs/messages/production-start-no-build-id
```

This is my `next.config.mjs` file:
```
/** @type {import('next').NextConfig} */
const nextConfig = {
    output: 'export',
    distDir: 'build',
    reactStrictMode: false,
    images: {
        unoptimized: true,
    },
}

export default nextConfig
```

The `.next` folder seems to contain the `BUILD_ID` but the `build` folder, which contains all the static exports, does not have a `BUILD_ID` and I think that is what `npm run start` is looking for based on the URL the error message points to. Any suggestions on how to run the production build with `npm run start`?

I understand my environment info below dictates things are out of date, but my codesandbox above should be using the latest NextJS and it still doesn't work there.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Thu Nov 7 15:41:49 EST 2024
  Available memory (MB): 15736
  Available CPU cores: 4
Binaries:
  Node: 20.5.1
  npm: 9.8.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.16 // An outdated version detected (latest is 15.0.3), upgrade is highly recommended!
  eslint-config-next: 14.2.16
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.3
Next.js Config:
  output: export
 ⚠ An outdated version detected (latest is 15.0.3), upgrade is highly recommended!
```


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

Developer Experience

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

next start (local)

### Additional context

_No response_
Repository: pytorch
Issue: Need to also assert on replacements for unbacked symbols
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

```
            for i0 in new_unbacked_defs:
                ras = self.ras_by_symbol.pop(i0, [])
                # NB: size-like not needed, we won't retrace
                vr = shape_env.var_to_range[i0]
                if not shape_env._default_unspecified_value_range().issubset(vr):
                
                    def is_convertible(s: Expr) -> bool:
                        if s in (int_oo, -int_oo):
                            return False
                        try:
                            int(s)
                            return True
                        except TypeError:
                            return False
        
                    if is_convertible(vr.lower):
                        make_assert(i0 >= vr.lower, f"{i0} >= {vr.lower}")
                    if is_convertible(vr.upper):
                        make_assert(i0 <= vr.upper, f"{i0} <= {vr.upper}")

                for ra in ras: 
                    fvs = free_unbacked_symbols(ra.expr)
                    missing = fvs - self.bound_unbacked_symbols
                    if missing:
                        i1 = min(missing, key=str)
                        self.ras_by_symbol.setdefault(i1, []).append(ra)
                    else:
                        make_assert(ra.expr, f"{ra.expr}")
```

This does value range and deferred runtime asserts, but replacement asserts are missing.

### Versions

main

cc @chauhang @penguinwu @bobrenjc93
Repository: PowerToys
Issue: Make MouseWithoutBorders connections dialog useful
Labels: Needs-Triage

### Description of the new feature / enhancement

Currently the connections dialog is just a few boxes with seemingly random colour borders.

When it doesn't connect, the colours change - that tells me nothing.

Give me an error message that I can do something about.

Make the "Refresh Connections" button actually connect to the other machines.

### Scenario when this would be used?

At least once per day when MWB fails to connect

### Supporting information

Ok, this is a bit tongue in cheek but for real - connection problems never used to be a thing before it was picked up and added to powertoys
The connections screen is no use to end users at all - and making it actually useful would be amazing
Repository: flutter
Issue: RenderParagraph should use an aliased/hard-edge clip rect for overflow removal.
Labels: P2,team-framework,triaged-framework

Context: https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/rendering/paragraph.dart#L899-L909


Even with Impeller, a hard edge clip rect is slightly faster than an anti-aliased clip rect.  fidelity will still be OK for overflow handling via a hard edge clip.

This should change to:

```dart
context.canvas.clipRect(bounds, doAntiAlias: false);
```

Though I'm not sure what qualifies as a test for this.
Repository: TypeScript
Issue: Generic function passed to generic function inferred correctly only with spread
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

generic function spread regression inference

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about generics



### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.8.0-dev.20241121#code/KYDwDg9gTgLgBDAnmYcByEAmqC8cDecAvgNwBQZ2AxgDYCGUwAkAGYCuAdlTAJYQdwWEYSIgAeACoAaOACVgAZzY14oGMA6YFcAIJQodRABkeAa2BjOpjhADuHAHwyAogDceNOGo1a4jOpj8NIhwVjb2ANoAug4AFGRMPBxgbDAAXHDSCVR0NDQARnRUphmxSSnpmTJgjK4Z8koqMgB0rcDuNBluHgCUcDgOcorKMFJkPfXDKhTU9IysnNx8AoV0a2tQkjINI14g6praegbGZhZhdo5xCeWpGVlMOXmFxaW3ldJwNe2TjTB9AyGfzGEyBIxmwFoDFQ7C4vH4cCeBSKpkk1zgGLg73uY0xX1qGQUMCgSQA5tEQYTiWTouQyKBILBBIt4QJQHQALZgGgWCRxbGZPr4Ch4gD0orgAEkOCxgFBtEgUF8GJzgOooGCVIjoIxuMEEkJRMIyslUjIkS9TD1yGKJQA9AD8Isx4rgADE6B4FRAsTK5QhkKgwCqOWr-TstVQdZCYMFfUTgAFfbL5QgABaoKMcIkGJIwBKrdYME0Vc25ZHFa1kW1wR3OjGugBCyDoCgUZOTco0VGAMhgGeZcOWiPLWO0Uf0MermML602nxzNJiJbNI+eKKr04bEulKYVgeVBlD6s18AnutjiC3cFnGxXozXFdRfKrNbrRDIQA

### 💻 Code

```ts
export type Node = { };
declare function fooooooo<T, Result extends ArrayLike<unknown>, Evil extends readonly unknown[]>(
    input: T,
    callback: (input: T, prev: Result, ...evil: Evil) => Result,
): Result

declare function baaaaaar<T, Result extends ArrayLike<unknown>>(
    input: T,
    callback: (input: T, prev: Result) => Result,
): Result

declare function callback<T>(
    input: T,
    prev: string[],
): string[];

export function example<T>(input: T) {
    // Infers type parameter Result correctly
    fooooooo(input, callback);
    // ^? function fooooooo<T, string[], []>(input: T…

    // Fails to infer type parameter Result correctly instead infers the constraint
    baaaaaar(input, callback);
    // ^? function baaaaaar<T, ArrayLike<unknown>>(in…



    // Bypassing inference, the function call is correct
    baaaaaar<T, string[]>(input, callback);

    // Infers type parameter Result correctly
    baaaaaar(input, callback<T>);
    // ^? function baaaaaar<T, string[]>(input: T, ca…
}
```


### 🙁 Actual behavior

`baaaaaar(input, callback)` infers the constraint of `Result = ArrayLike<unknown>`

### 🙂 Expected behavior

`baaaaaar(input, callback)` should infer `Result = string[]` from the return type or parameter of `callback`.

### Additional information about the issue

_No response_
Repository: ollama
Issue: Llama3.2 Safetensors adapter not supported?
Labels: bug

### What is the issue?

Hi Guys,

First thanks for creating such a wonderful tool. I have run into a problem which I believe is a bug but I may be incorrect and I could be asking for a feature request. Basically I have fine-tuned a llama3.2 model on some local data and then saved this in safetensors format. 

Now I create a model file like below and point it to the safe tensor adapter files. Now when I run the command

ollama create myllama3.2 --file myllama3.2.modelfile

I see the below output which I believe tells me it has been a success. 

transferring model data 100% 
converting model

But when I run the Ollama list command my newly created model is not displayed. My modelfile starts like the below providing the directory where the safetensors adapter file is stored:

FROM llama3.2:1b
ADAPTER /home/shuaib/tmp/Llama-3.2-1B/

In the Ollama docs and the modelfile markdown file [https://github.com/ollama/ollama/blob/main/docs/modelfile.md](url) it says:

Currently supported Safetensor adapters:
Llama (including Llama 2, Llama 3, and Llama 3.1)

Is this why my attempt at creating a model from my fine-tuned model is failing? Because the llama3.2 safetensor adapters are not supported yet? Or am I missing something? Also is there a plan to support the llamam3.2 safentensors adapters anytime soon? 

If it is the case because of the lack of support for the llama3.2 safe tensors adapters, should my workaround be to convert my fine-tuned safetensors file into gguf format?

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.1
Repository: deno
Issue: `deno compile --include-code-cache`
Labels: feat,compile

Surfing on the new `deno compile --include`-style flags, it would be great if the compiled binary could have its own [code cache](https://github.com/denoland/deno/pull/26528#issuecomment-2491735952) included.

Code cache right now will only cache in the first execution and then reuse it in subsequent ones.

As I had stated [here](https://github.com/denoland/deno/pull/26528#issuecomment-2455421250), this new flag would make a lot of sense in ephemeral environments like docker containers, where the first execution is also the only execution, rendering code cache a bit useless in this scenario (to be fair, it should be able to work around the issue by running the application once during `docker build`, but running an application isn't always ok to do).

On my tests on some application, the code cache seems very small:

```console
# let's make sure we don't have any prior cache
❯ deno clean
Removed /home/felipecrs/.cache/deno (7569 files, 86.04MB)

❯ ./pkgx-cc --sync

❯ deno clean
Removed /home/felipecrs/.cache/deno (4 files, **76.27KB)**
```

Only 76.27 KB in this example. A negligible size increase considering the whole binary size.

Maybe it should be even made the default?
Repository: deno
Issue: `deno compile --code-cache-path`
Labels: suggestion,compile

With the new [code cache](https://github.com/denoland/deno/pull/26528), compiled programs would end up writing to `~/.cache/deno`. This may not be desirable. The program may have its own cache directory for example. Also, it would end up creating this directory in systems where Deno isn't even installed, which could lead to end-user confusion. End-users may not even know what is Deno.
Repository: vscode
Issue: Unable to interact with Code windows  on Mac Os after window maximization
Labels: info-needed


Does this issue occur when all extensions are disabled?: Yes

I have an intermittent issue that I only see in VS code on Mac, although it may be partially due to electron bugs (I ruled out an open-source  window management utility called Rectangle that I am also using)
I am using multiple displays and using Rectangle to move application windows between or minimize or maximize.
I haven't fully isolated the exact trigger, but  at some point if I try to maximize  one of the VS code windows.VS code windows become unresponsive. I can change the window focus by clicking on the windows and  I can open new windows from the dock, but the menu bar and the application is unresponsive. I have to force quit VS Code and things return to normal

I also can't updated to newer versions of VS code 1.85, since the remote SSH extensions in the later versions have an incompatibility  with  the remote machines I connect to.


Version: 1.85.2 (Universal)
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:32.531Z (10 mos ago)
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.6.0
Sonoma 14.7.1
Steps to Reproduce:

1.  Run VS code opening multiple remote windows
2.  Maximize a window
Repository: PowerToys
Issue: Fail to initialize plugins: OneNote
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.86.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Power Toys Run - Plugin Loading Error Fail to load plugin: OneNote Please report the bug to https://aka.ms/powerToysReportBug. (For third-party plugins, please contact the plugin author.)

### ✔️ Expected Behavior

I should press alt space and have powertoys run work (which it does), but this error is thrown

### ❌ Actual Behavior

I got an error:
Power Toys Run - Plugin Loading Error Fail to load plugin: OneNote Please report the bug to https://aka.ms/powerToysReportBug. (For third-party plugins, please contact the plugin author.)

I do need powertoys run to work for oennote for it to work.

### Other Software

_No response_
Repository: pytorch
Issue: Use expecttest in test_compiled_optimizers.py
Labels: good first issue,module: tests,triaged,enhancement,actionable,oncall: pt2

### 🐛 Describe the bug

@ezyang pointed out that it's kind of annoying to update the kernel counts in https://github.com/pytorch/pytorch/blob/723498aab8803702dfd508be05a1ebe525112ebd/test/inductor/test_compiled_optimizers.py#L4

We should update this to use expecttest like our other tests.

### Versions

N/A

cc @mruberry @ZainRizvi @chauhang @penguinwu
Repository: ui
Issue: [bug]: dialog was not found
Labels: bug

### Describe the bug

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

The component at https://ui.shadcn.com/r/styles/default/dalog.json was not found.      
It may not exist at the registry. Please make sure it is a valid component.

### Affected component/components

Dialog and Alert dialog

### How to reproduce

npx shadcn@latest add dalog 

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: rope perf improvement
Labels: triaged,oncall: pt2,module: inductor

Tracking issue for improving perf of this kernel.

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov
Repository: material-ui
Issue: Select onFocus called way too many times
Labels: performance,component: select,enhancement

### Steps to reproduce

Steps:
1. Open this link to live example: https://codesandbox.io/p/sandbox/q649qz
2. Open console to see logs
3. Click into the select box
4. Click off the select box
5. Click off the select box again


### Current behavior

On the initial focus, onFocus is called 4 times. On initial blur, onFocus is called 2 more times and onBlur is not called. On second blur, onBlur is called.

### Expected behavior

On initial focus, onFocus should be called once and not again until component is blurred and refocused. onBlur should be called when input is initially blurred.

### Context

I have a code associated to with onFocus event that is being called 4 times when I expect it to be called once.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: mui select onfocus multiple times
Repository: vscode
Issue: Terminal suggest: Make sure `cd -` completions play nice in pwsh
Labels: feature-request,terminal-suggest

I see this coming in https://github.com/microsoft/vscode/pull/234363:

```js
			{
				name: '-',
				description: 'Switch to the last used folder',
				hidden: true,
			}
```

In pwsh it's actually - as in -/+ and they navigate a history stack, not just toggle between the last directory (`$OLDPWD` in bash). We could improve the wording for pwsh and add cd + as well (especially if `hidden` does what I think it does and doesn't show it unless typed), similar to the pwsh support from the script:

![Image](https://github.com/user-attachments/assets/c01ec9d1-9dc0-4e05-ab56-abfb08d59cc0)

When I looked into it this history stack is internal so we can't resolve the folder and stick it on the right for pwsh unfortunately, we might be able to do it on shells that use `$OLDPWD`.
Repository: kubernetes
Issue: [FG:InPlacePodVerticalScaling] Revisit ResizeStatus and state transitions
Labels: priority/important-soon,sig/node,kind/feature,triage/accepted

/kind feature

There are several problems with the current approach to pod ResizeStatus, including:

1. Race condition setting the status: the kubelet can overwrite the Proposed status set by the API server (https://github.com/kubernetes/kubernetes/issues/125394)
2. Can technically have 2 parallel resize statuses: a {Proposed/Deferred/Infeasible} resize when desired resources != allocated resources, and an InProgress resize when allocated resources != actual resources. Currently the former just overrides the latter.
3. Separate mechanism for surfacing details related to error states (Deferred, Infeasible, stuck InProgress)
4. No status to capture desired memory limit < actual memory usage, which can lead to a resize stuck in InProgress (maybe this should move to the deferred state?)

Before graduating to Beta, we should revisit the design of ResizeStatus, and take a holistic look at the user experience.

/sig node
/priority important-soon
/milestone v1.33
/triage accepted
/cc @yujuhong
Repository: go
Issue: encoding/binary: Write does not optimise the case of native-format slices
Labels: Performance,NeedsInvestigation

### Go version

go version go1.23.3 linux/amd64

### Output of `go env` in your module/workspace:

```shell
Irrelevant, but happy to provide.
```


### What did you do?

I wrote a (large) number of slices of little-endian IEEE floats using `binary.Write` on a little-endian machine.  I was expecting the library to recognise that I was writing in the native format, and special-case the write.  However, it did not, and the performance was about 3000 slower than expected.

https://go.dev/play/p/wNWegxHXjlG

### What did you see happen?

```
BenchmarkPutFloats-8         	  196766	      5958 ns/op	 671.41 MB/s
BenchmarkPutFloatsUnsafe-8   	465501314	         2.246 ns/op	1781336.18 MB/s
```

### What did you expect to see?

I was expecting the performance of the two implementations to be similar.
Repository: ui
Issue: [bug]: Inconsistent Scrolling Behavior with Dialog and ScrollArea
Labels: bug

### Describe the bug

When using a dialog containing a scroll area component, the expected behavior is that the scroll area should handle scrolling when the dialog is active. However, the following issues occur:  
1. The scroll area within the dialog does not respond to scroll interactions.  
2. In some cases, the background page (outside the dialog) scrolls instead.  
3. This behavior often disrupts the overall scroll functionality of the page, rendering it inconsistent.  

This issue appears to occur specifically when combining `Dialog` and `ScrollArea` components, leading to broken scroll behavior for both the dialog and the page.


### Affected component/components

Dialog, ScrollArea

### How to reproduce

here's a quick v0 code for the same: https://v0.dev/chat/8TUcPpED3by?b=b_XFselDzUnJH 

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Win11, Edge.
(Note: am explicitly using JSX with vite & not TSX)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: Multiple torch.{*}_copy variants are not in generated docs/docs skiplist
Labels: module: docs,triaged

### 🐛 Describe the bug

to track https://github.com/pytorch/pytorch/pull/140045#discussion_r1852591819

`torch.{*}_copy` variants of functions are not in generated docs despite being public

Some examples are `torch.expand_copy`, `torch.diagonal_copy` etc see [here](https://github.com/twaclaw/pytorch/blob/9a30f686fe5496f3562e98b15b7ab15c26b5db11/torch/_torch_docs.py#L13805-L13843)

1. Is not having these in generated docs intentional?
2. I don't see them on the [coverage test skip list](https://github.com/pytorch/pytorch/blob/main/docs/source/conf.py?fbclid=IwZXh0bgNhZW0CMTEAAR0fbujOxNi9AmkYPYVPWNjmN36WcVVPWOk-ULliwfxjohC7ocLyHeYx5eg_aem_SSUJa4GtZyrmoeWPIEdAbA), are our coverage tests working as expected here?

Please close if this was intentional :)

### Versions

main

cc @svekars @brycebortree @sekyondaMeta @AlannaBurke
Repository: go
Issue: crypto/tls: re-enable two TLS tests with fips140tls.Required
Labels: NeedsFix

Two small TODOs that came out of [CR 629736](https://go-review.googlesource.com/c/go/+/629736):

1. In `handshake_server_test.go` the "RSA" and "RSA with ec_point_format" subtests of `TestTLSPointFormats` are skipped when `fips140tls.Requried()` is enabled, otherwise a handshake failure error is observed. This should be debugged (I suspect I'm overlooking someting small) and the subtests re-enabled for FIPS TLS mode.

2. The `TestRenegotiationExtension` test is skipped when `fips140tls.Required()` is enabled due to its use of RC4 ciphersuites and the RSA 1024 test certificate hiearchy. This _should_ be possible to enable in FIPS TLS mode by replacing RC4 with an AES ciphersuite and using RSA 2048 test certs. Doing so was giving a "Server returned short message of length 7" error. This should be debugged and the test re-enabled for FIPS TLS mode.
Repository: node
Issue: Add zlib/promise module
Labels: feature request

### What is the problem this feature will solve?

To work with promise we need to use the `promisify` util to converte the callback function version.


### What is the feature you are proposing to solve the problem?

I would like to add this new module to use promises instead of callbacks, similar to the `fs/promises` module.

### What alternatives have you considered?

_No response_