sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Fast refresh is broken by a lib using inline `await`
Labels: bug,Module Resolution

### Link to the code that reproduces this issue

https://github.com/flo-dao/repro-fast-refresh

### To Reproduce

1. Start the app in dev
2. Make a change in `index.tsx`
3. You get a full page reload, with a message in the console indicating that fast refresh didn't work

### Current vs. Expected behavior

Fast refresh should work

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:51 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6030
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.21
  pnpm: 8.14.0
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Not sure, Module resolution (CJS / ESM, module resolving)

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

next dev (local)

### Additional context

I pinpointed the code causing the issue in the `bson` lib, here is the [link](https://github.com/mongodb/js-bson/blob/44bec1900b53bac9938c3f0b9dcf0f75eadcd95e/src/utils/node_byte_utils.ts#L46).

The final code looks like this in  `bson.mjs`:
```
const nodejsRandomBytes = await (async () => {
    try {
        return (await import('crypto')).randomBytes;
    }
    catch {
        return nodejsMathRandomBytes;
    }
})();
```
If I turn this into a promise without async await, the fast refresh works as expected.
Repository: flutter
Issue: Text Overflow.fade for multiline text
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Use case

I am trying to achieve the effect of fading out the block text. I am writing this code:
``` dart 
Text(
      'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. ',
      maxLines: 2,
      style: TextStyle(
        overflow: TextOverflow.fade,
     ),
),
```
And I get it:
<img width="301" alt="Screenshot 2024-01-31 at 16 21 35" src="https://github.com/flutter/flutter/assets/63193897/baf9accc-4db4-40c5-9d01-7484b5abfde2">

But that's not what I need. I want the text to fade out only on the right side of the last line. That is, the last line should look like this:
<img width="301" alt="Screenshot 2024-01-31 at 16 28 36" src="https://github.com/flutter/flutter/assets/63193897/ac98db21-e774-4531-b271-69704d4f3080">


### Proposal

 I want the text to fade out only on the right side of the last line. That is, the last line should look like this:
<img width="301" alt="Screenshot 2024-01-31 at 16 28 36" src="https://github.com/flutter/flutter/assets/63193897/ac98db21-e774-4531-b271-69704d4f3080">

Maybe something can be corrected inside Flutter to achieve this behavior?
Repository: storybook
Issue: [Bug]: Init fails when using appTemplate or routes config w/ @storybook/sveltekit
Labels: bug,svelte,sveltekit,sev:S2

### Describe the bug

When using `appTemplate` and `routes` in `storybook.config.js`, `@storybook/sveltekit` cannot find files from the storybook directory.

![image](https://github.com/storybookjs/storybook/assets/1218446/3c200778-6c32-4ad2-8f01-5e7dde12f9b6)

However, when using the standard config, everything works as expected.

![image](https://github.com/storybookjs/storybook/assets/1218446/f2baed27-f3c3-4925-8f39-60a25874fa49)

Storybook **MUST** pick up the route and template configs from story `storybook.config.js` to be viable for production codebases.

Production code for large organizations tends to have more deeply nested directories and use non-standard configurations to provide separation between server code, web code, service integrations, and so on.

### To Reproduce

1. Create a SvelteKit project with the following config for Svelte and Vite:

    ```javascript
    // svelte.config.js
    const config = {
        kit: {
            files: {
                routes: './web/routes',
                appTemplate: './web/app.html'
            }
        }
    };

    export default config;
    ```

    ```javascript
	import { sveltekit } from '@sveltejs/kit/vite';
	import { defineConfig, searchForWorkspaceRoot } from 'vite';

	export default defineConfig({
		plugins: [sveltekit()],

		server: {
			fs: {
				allow: [searchForWorkspaceRoot(process.cwd())]
			}
		}
	});
    ```
  

2. Run `npx sb init`

    You will then see a message like:
    
    > The request url "/home/user/my-repo/stories/Configure.mdx" is outside of Vite serving allow list.
    
    ![image](https://github.com/storybookjs/storybook/assets/1218446/3c200778-6c32-4ad2-8f01-5e7dde12f9b6)

### System

```bash
System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1270P
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 21.2.0 - ~/.nvm/versions/node/v21.2.0/bin/node
    npm: 10.2.3 - ~/.nvm/versions/node/v21.2.0/bin/npm <----- active
  npmPackages:
    @storybook/addon-essentials: ^7.6.11 => 7.6.11
    @storybook/addon-interactions: ^7.6.11 => 7.6.11
    @storybook/addon-links: ^7.6.11 => 7.6.11
    @storybook/blocks: ^7.6.11 => 7.6.11
    @storybook/svelte: ^7.6.11 => 7.6.11
    @storybook/sveltekit: ^7.6.11 => 7.6.11
    @storybook/test: ^7.6.11 => 7.6.11
    storybook: ^7.6.11 => 7.6.11
```


### Additional context

_No response_
Repository: vscode
Issue: Should dispose code actions after auto-running AI action?
Labels: editor-code-actions,under-discussion

cc @aeschli 

this code autoruns a code action if there's a single AI action:

https://github.com/microsoft/vscode/blob/7a56623b8276d75a77e3093d89568cfa772362df/src/vs/editor/contrib/codeAction/browser/codeActionController.ts#L115

does it need to dispose the CodeActionSet? this similar code that autoruns a single action does:

https://github.com/microsoft/vscode/blob/7a56623b8276d75a77e3093d89568cfa772362df/src/vs/editor/contrib/codeAction/browser/codeActionController.ts#L188-L193
Repository: deno
Issue: Worker-Threads not running in parallel
Labels: perf,needs investigation

Version: Deno 1.40.2

I'm currently doing a benchmark of Node.js, Deno and Bun when using Worker Threads. 
I have a very simple implementation, which creates a certain number of worker threads which calculate the fibonacci number. 

This is the code i use for Deno
``` js
/* main.js */
const numThreads = Deno.args[0] || 1;

console.log(`Starting ${numThreads} Threads in Deno!`);
for (let i = 0; i < numThreads; i++)
    new Worker(new URL('./worker.js', import.meta.url).href, {
        type: 'module',
    });
```

```js
/* worker.js */
fibonacci(1000);

function fibonacci(n, memo = {}) {
    if (n <= 1) return n;
    if (memo[n]) return memo[n];

    memo[n] = fibonacci(n - 1, memo) + fibonacci(n - 2, memo);
    return memo[n];
}
self.close();
```

I did my benchmark with
`/usr/bin/time -v deno run --allow-read main.js <num-threads>`
and plotted it to a graph:
y: real time x: number of threads
![Screenshot_20240131_153205](https://github.com/denoland/deno/assets/68951860/22e3ce2e-1e8a-4a8c-b20c-72a5573d7f39)
y: user + sys time x: number of threads
![Screenshot_20240131_153404](https://github.com/denoland/deno/assets/68951860/a95acac3-1d90-40ea-b248-06795372496e)
y: Maximum resident size (memory) x: number of threads
![Screenshot_20240131_153439](https://github.com/denoland/deno/assets/68951860/9ccdb3b5-6c0f-41d1-bbe7-c801115376d2)

So the real time and user+sys time is increasing linearly and the memory usage is just staying the same. This behavior seems weird to me. I would expect an increase in the memory usage and a similar graph to Node.js and Bun for real and user+sys time. 

This led me to believe that there is some kind of bug in the worker threads API of Deno. However maybe the bug is in my code.
If you have any clue, please let me know. 

Thanks!
Repository: pytorch
Issue: decorate_context results in uninformative backtraces
Labels: module: logging,triaged,oncall: pt2

### 🐛 Describe the bug

When I use `decorate_context` to convert a context manager into a decorator, I only ever see the generic decorate_context in stack traces. This sucks, because different context managers can be quite different, and I would quite like to know what the actual context manager I was running was.

Example uninformative stack:

```
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]     optimizer.step()
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]   File "/packages/training_platform/worker-inplace#link-tree/torch/optim/optimizer.py", line 391, in wrapper
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]     out = func(*args, **kwargs)
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]   File "/packages/training_platform/worker-inplace#link-tree/torch/utils/_contextlib.py", line 115, in decorate_context
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]     return func(*args, **kwargs)
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]   File "<torch_package_0>.caffe2/torch/fb/optim/shampoo_v1/distributed_shampoo.py", line 1334, in step
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]     self._split_foreach_weightdecay_kernel(
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]   File "/packages/training_platform/worker-inplace#link-tree/torch/utils/_contextlib.py", line 115, in decorate_context
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]     return func(*args, **kwargs)
[rank7]:[2024-01-25 11:27:03,298] [3/1] torch._dynamo.symbolic_convert: [INFO]   File "/packages/training_platform/worker-inplace#link-tree/torch/_dynamo/eval_frame.py", line 417, in _fn
```

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @zou3519
Repository: go
Issue: cmd/compile: DIE with empty locations generated with optimizations disabled
Labels: NeedsInvestigation,compiler/runtime

### Go version

go version devel go1.23-ae457e811d Tue Jan 30 23:37:12 2024 +0000 linux/amd64

### What did you do?

I was investigating https://github.com/go-delve/delve/issues/3640 which is about DIE for variables being generated with an empty location attribute when compiling with `-N -l` in go1.21.

It turns out that most of the bug seems to have been solved (accidentally?) by https://go.dev/cl/509856, however very few of those persist.

An example is net.sendFile which for its return parameters ends up having two entries for its output parameters:

 <2><10dbe2>: Abbrev Number: 17 (DW_TAG_formal_parameter)
    <10dbe3>   DW_AT_name        : handled
    <10dbeb>   DW_AT_variable_parameter: 1
    <10dbec>   DW_AT_decl_line   : 20
    <10dbed>   DW_AT_type        : <0x5cdb9>
    <10dbf1>   DW_AT_location    : 0 byte block:        ()
 <2><10dbf2>: Abbrev Number: 12 (DW_TAG_variable)
    <10dbf3>   DW_AT_name        : &handled
    <10dbfc>   DW_AT_decl_line   : 20
    <10dbfd>   DW_AT_type        : <0x5cdca>
    <10dc01>   DW_AT_location    : 2 byte block: 91 68  (DW_OP_fbreg: -24)

I investigated the problem a bit and the first one, the one without location, is added by $GOROOT/src/cmd/compile/internal/dwarfgen/dwarf.go:241. In the same function I noticed that there is some weird looking code there that looks related:

	if n.Esc() == ir.EscHeap {
		// The variable in question has been promoted to the heap.
		// Its address is in n.Heapaddr.
		// TODO(thanm): generate a better location expression
	}

Is this really meant to be like this? An empty if statement?

cc @thanm
Repository: vscode
Issue: Webview View won't get focussed properly
Labels: bug,webview-views

Does this issue occur when all extensions are disabled?: No (because it is extension-related)

- VS Code Version: 1.85.2 (Universal)
- OS Version: 14.3 (23D56)

Steps to Reproduce:

1. Download, open, compile and run (start debugging) **webview-view-sample** from  [vscode-extension-samples](https://github.com/microsoft/vscode-extension-samples)
2. In the _extension development_ instance open Explorer Side Bar
3. Go to command palette and execute "Explorer: Focus on Outline View"
4. Observe that the Outline area gets focussed with indication:
    ![focussed](https://github.com/microsoft/vscode/assets/33084159/b97949c3-7ce1-4b22-b52d-c15daa78da29)
6. Go to command palette and execute "Explorer: Focus on Calico Colors"
7. Observe that no focus indication appears:
![no-focus](https://github.com/microsoft/vscode/assets/33084159/b162d4c8-bf13-40d5-a1a5-8573b44bcc08)
Also, no focus/status update event to propagate to the underlaying webview is generated.

Notes:
- If the panel was collapsed it will get expanded correctly
- If different sidebar panel is active, the correct (Explorer) panel is shown

This leads to confusing user experience for Webview View panels.

#### Full version info
```
Version: 1.85.2 (Universal)
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:32.531Z
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.3.0
```
Repository: vscode
Issue: Wrong Webview View tab order / keyboard navigation order
Labels: bug,accessibility,webview

Does this issue occur when all extensions are disabled?: No (because it is extension-related)

- VS Code Version: 1.85.2 (Universal)
- OS Version: 14.3 (23D56)

Steps to Reproduce:

1. Download, open, compile and run (start debugging) **webview-view-sample** from  [vscode-extension-samples](https://github.com/microsoft/vscode-extension-samples)
2. In the _extension development_ instance open Explorer Side Bar
3. Bring focus to "Calico Colors" header (click), but keep it expanded (click may be needed)
4. Press "tab" to move the focus to the next element ("Clear colors" button is focussed)
5. Press "tab" again to move the focus to the webview view panel
6. Observe that focus has moved to somewhere else (typically the document tab)
   Note: The Webview panel is accessible, but somewhere else in the tab order as the hosting iframe is located  somewhere else in the page hierarchy; This is confusing and not accessible

#### Full version info
```
Version: 1.85.2 (Universal)
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:32.531Z
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.3.0
```
Repository: ollama
Issue: Request official flatpak or SNAP
Labels: feature request

I'd like to request a flatpak. It's easier to install, easy to sandbox, safer than piping a script into bash and cross platform! You can then submit the flatpak to flathub, get the verified icon and things would be awesome! ;)

thanks!

Edit: It's been pointed out (and I forgot) that flatpaks really aren't designed for server software or command line tools and that snaps are more appropriate. Although I am not a huge fan of snaps, this may be a better way to go.
Repository: node
Issue: --watch should monitor replaced files
Labels: feature request,watch-mode

### What is the problem this feature will solve?

Currently, `--watch` watches an [inode](https://nodejs.org/docs/latest/api/fs.html#inodes) and not necessarily what the user might consider a "file". This can cause confusion on systems that write to disk by deleting the old file and then creating a new one.

For example, when using Docker Compose's [`watch`](https://docs.docker.com/compose/file-watch/) mode, the watched file is first deleted and when a new file is created. Node currently fails to restart on file changes, as  node is still watching the inode of the deleted file, and doesn't react to the new file being created.

### What is the feature you are proposing to solve the problem?

While this behavior makes sense for the lower-level and more "raw" `fs.watch()`, perhaps the more general `--watch` behavior can be expanded to be smarter about detecting replaced files. Alternatively, a new flag can be introduced with this behavior.

### What alternatives have you considered?

Other alternatives require using one of the different file watcher libs. That seems like a step down from the otherwise awesome native `watch` feature.


Docker Compose Issue: [[BUG] Compose Watch With “node –watch” Only Reloads First Time](https://github.com/docker/compose/issues/11090)
Docker Issue: [node --watch doesn't work well within a container](https://github.com/moby/moby/issues/47061)
Repository: pytorch
Issue: Selectively disable dynamic shapes in an inner compile region
Labels: feature,triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

Consider

```
import torch

@torch.compile(dynamic=False)
def g(x):
    return x * x

@torch.compile(dynamic=True)
def f(x, y):
    return g(x), y * y

f(torch.randn(10), torch.randn(20))
```

Intuitively, you would expect g to be compiled with static shapes. However, the outer configuration overrides everything else:

```
[2024-01-31 09:35:05,282] [0/0] torch.fx.experimental.symbolic_shapes: [INFO] create_env
[2024-01-31 09:35:05,495] [0/0] torch.fx.experimental.symbolic_shapes: [INFO] create_symbol s0 = 10 for L['x'].size()[0] [2, 9223372036854775806] at a.py:9 in f (_dynamo/variables/builder.py:1797 in <lambda>)
[2024-01-31 09:35:05,506] [0/0] torch.fx.experimental.symbolic_shapes: [INFO] create_symbol s1 = 20 for L['y'].size()[0] [2, 9223372036854775806] at a.py:9 in f (_dynamo/variables/builder.py:1797 in <lambda>)
[2024-01-31 09:35:15,113] [0/0] torch.fx.experimental.symbolic_shapes: [INFO] produce_guards
```

For many configuration values, it is not meaningful to change their meaning mid-stream, but dynamic=False is feasible to do in this way and we should have some support for it.

This came up when helping Shuai Yang debug why automatic dynamic shapes was not being disabled for Shampoo optimizer when they marked it as dynamic=False. This may not necessarily be the root cause, but it could be one of the potential causes of the problem.

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @zou3519
Repository: rust
Issue: `rustc` warns when finding an unknown jobserver style
Labels: A-diagnostics,C-bug,D-terse

`rustc` warns when finding an unknown jobserver style, but the Make manual seems to suggest to ignore it (since new kinds may be introduced in the future), or at least that is one possible interpretation:

> If your tool does not recognize the format of the `--jobserver-auth` string, it should assume the jobserver is using a different style and it cannot connect.

One could also read that as "... and then warn about it", like it asks to do for the simple pipe case. But if that is the case, I am not sure why it would say "it cannot connect" since obviously one would not be able to do so, i.e. I take it to mean "ignore it".

Thus, should `CannotParse` from `jobserver` be taken as an OK case, or should we keep the current behavior?

```console
$ echo 'fn main() {}' | MAKEFLAGS=--jobserver-auth=new rustc -
warning: failed to connect to jobserver from environment variable `MAKEFLAGS="--jobserver-auth=new"`: cannot parse jobserver environment variable value: expected `fifo:PATH` or `R,W`, found `new`
  |
  = note: the build environment is likely misconfigured
```

From https://github.com/rust-lang/rust/issues/120515.
Repository: PowerToys
Issue: Always on top border gets duplicated after minimizing and restoring all windows
Labels: Issue-Bug,Product-Always On Top,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Always on Top

### Steps to reproduce

1. Activate always on top for a window
2. Minimize all windows --> Win + M
3. Restore the minimized windows --> Win + Shift + M
4. Drag the top most window to another position

![BorderDuplicated](https://github.com/microsoft/PowerToys/assets/29866610/2b7b9db0-393a-48ac-ba75-4b956b089261)

I've found no way to get rid of these border anymore without disabling the the feature in PowerToys.

### ✔️ Expected Behavior

Always on top border stays correct after minimizing and restoring all windows

### ❌ Actual Behavior

Always on top border gets duplicated after minimizing and restoring all windows

### Other Software

_No response_
Repository: flutter
Issue: engine_v2 tests are incorrectly run on dart-internal bots when they should run on prod
Labels: P2,team-release,triaged-release

### Type of Request

bug

### Infrastructure Environment

LUCI - engine_v2 recipe

### What is happening?

https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Linux%20engine_release_builder/815/overview failed due to linux_fuchsia not having any kvm bots in dart-internal to run on. The expectation is that tests should run on prod to save dart-internal capacity.

This seems to be occurring on linux_web_engine as well https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Linux%20Production%20Engine%20Drone/31109/overview.

For the short term, we added some kvm bots to unblock the releases, but we should fix engine_v2 to trigger the tests outside dart-internal.

### Steps to reproduce

_No response_

### Expected results

Possible solutions
1. Fix the JSON configs to do the correct thing
2. Add a feature to the engine_v2 recipe so tests are spawned on bots from a different pool
Repository: next.js
Issue: eslint-config-next: `satisfies` in HTML attribute produces error
Labels: bug

### Link to the code that reproduces this issue

https://github.com/ysulyma/eslint-config-next-repro

### To Reproduce

1. Clone the repository
2. Run the following
```sh
npm install

# works
eslint --config default.json index.tsx

# doesn't work
eslint --config next.json index.tsx
# The prop value with an expression type of TSSatisfiesExpression could not be resolved. Please file an issue ( https://github.com/jsx-eslint/jsx-ast-utils/issues/new ) to get this fixed immediately.
```
The error only happens when using `next/core-web-vitals`, not when using the default TypeScript lint settings.

### Current vs. Expected behavior

I expected `index.tsx` to lint without issue, but with the Next plugin I'm receiving the error
```
The prop value with an expression type of TSSatisfiesExpression could not be resolved. Please file an issue ( https://github.com/jsx-eslint/jsx-ast-utils/issues/new ) to get this fixed immediately.
```

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.3.0: Thu Jan  5 20:50:21 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T8112
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 7.5.2
Relevant Packages:
  next: 14.1.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A
```


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

ESLint (eslint-config-next)

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

next build (local)

### Additional context

_No response_
Repository: flutter
Issue: Windows doesn't implement full Display API
Labels: engine,platform-windows,P2,a: multi window,team-windows,triaged-windows

Not implemented (always returning 0):

https://main-api.flutter.dev/flutter/dart-ui/Display/size.html
https://main-api.flutter.dev/flutter/dart-ui/Display/devicePixelRatio.html
Repository: flutter
Issue: ☂️ Windowing API
Labels: framework,engine,P2,a: multi window,team-framework,triaged-framework

* Display API:
  - [ ] https://github.com/flutter/flutter/issues/142630
  - [x] https://github.com/flutter/flutter/issues/142629