sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Load transformer models with shared memory 
Labels: Feature request

### System Info

.

### Who can help?

_No response_

### Information

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

### Tasks

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

### Reproduction

.

### Expected behavior

I want to load transformer models with share memory for example when open multi workers I want to load the model once and all workers use it and not load the model for every worker
Repository: next.js
Issue: Using window.history.pushState to add browser history records, clicking the back button does not update the page
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/festive-grothendieck-95zzlh?file=%2Fapp%2Fpage.tsx&embed=1

### To Reproduce

After launching the application, clicking to navigate to Page A triggers the addition of a browser history record using window.history.pushState(null, '', '/c'). However, upon clicking the browser's back button, the view does not update to Page C as expected.
Clicking to navigate to Page B alters the browser history record, yet the page remains unchanged.
Clicking on Page C results in a scenario identical to the first problem described.

### Current vs. Expected behavior

The current behavior is that clicking the browser's back button does not update the page. The expectation is that the page should update correctly, and the browser history should be accurately maintained.




### Provide environment information

```bash
Operating System:           
  Platform: win32           
  Arch: x64                 
  Version: Windows 10 Pro   
Binaries:                   
  Node: 20.9.0              
  npm: N/A                  
  Yarn: N/A                 
  pnpm: N/A                 
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)

App Router

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Other (Deployed)

### Additional context

_No response_
Repository: PowerToys
Issue: Flash of blue background every time I invoke PT run
Labels: Issue-Bug,Product-PowerToys Run,Area-Quality,Area-User Interface,Status-Reproducible

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Invoke PT run using the bound hotkey.

### ✔️ Expected Behavior

PT run shows, nothing else.

### ❌ Actual Behavior

Before PT run shows, a blue background is shown which is rather distracting.

https://github.com/microsoft/PowerToys/assets/30658772/8394d4cc-99d4-4f7e-9d20-c0ecbe33e44d

This seems to be happening every time, not just after fresh application start etc. However, the duration in which this blue background is shown differs rather drastically. Sometimes it's very long, sometimes very short so that it's barely noticeable.

Those short flashes are not captured in the video but they're definitely there.

Also, this blue background appears when the height of the PT run window changes during typing due to changed number of shown results (also shown in the video).


### Other Software

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Do you have no-webui version for this project? Just use params to control inputs and outputs. 
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Do you have no-webui version for this project.The page is lagging when the program launched in server and transfered the result page to my computer.   

### Proposed workflow

1. Go to .... 
2. Press ....
3. ...


### Additional information

_No response_
Repository: next.js
Issue: `Error: Route did not complete loading` causes page reload
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/MistaPidaus/nextjs-routing-issue

### To Reproduce

1. Build the app locally and run production locally
2. Open the Chrome Dev tool and set the network profile to "Slowest 3G" with `250kb` for both download & upload value and `5000` for latency value 
3. On the performance tab, set the CPU performance to `6x slowdown` and make sure the network is the new profile with above setting.
4. Open `http://localhost:3000`
5. Once you see the header section with `Index page` text, spam click it multiple times (it's a button with routing mechanism)
6. Observe the browser console and you'll see `Error: Route did not complete loading` error.

### Current vs. Expected behavior

Current behaviour, as the video attached

https://github.com/vercel/next.js/assets/21690115/ac1fb39a-0317-41a0-81df-4d75ab541c06

Notice when I filled the form and got redirected afterwards due to the logic I've implemented that should run once on the initial visit. 

I'm expecting it won't reload or redirect - in other words, the user should be able to proceed with the flow with no issue.


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 20.6.0: Tue Oct 12 18:33:42 PDT 2021; root:xnu-7195.141.8~1/RELEASE_X86_64
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.6.6
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)

Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

Other (Deployed)

### Additional context

We're migrating our web app to the Next.js framework and slowly redirecting traffic to the new Next.js app. After a few days, we noticed a lot of errors (around 1.7k) in our monitoring service, indicating the `Error: Route did not complete loading` issues/errors. 

![Screenshot 2024-02-29 at 6 20 52 PM](https://github.com/vercel/next.js/assets/21690115/64416527-7ebe-4c31-a7bb-947125e8bcd3)

We suspect the user is having a slow network connection and we managed to reproduce the error. The worst thing is the issue causing the page to reload (refer the video attached) so if the user has to fill in their details, they have to restart again. We have a multiple-step form within our flow. So if the user manages to get far and fill most of the form and hit this error, they have to redo it again. We saw a lot of traffic drop-off after getting this error.
Repository: ant-design
Issue: 希望能控制 Cascader 多选时下拉展开的选项
Labels: help wanted,Inactive,👷🏻‍♂️ Someone working on it

### What problem does this feature solve?

优化用户修改多选 Cascader 选项的体验，快速定位到已选的选项

例如 用户想从选中的 a-b-c-1 选项，改为 a-b-c-2 ，目前有两种办法：
1. 一层层手动展开 a-b-c
2. 输入搜索 a-b-c-2

如果选项展开的值能受控，就比较方便做到  点击已选中的选项，自动展开层级

想实现的效果如下：

![image](https://github.com/ant-design/ant-design/assets/9395932/e63d8d0a-85dc-468a-8b2d-cf47a27a85cc)

Related issue: https://github.com/ant-design/ant-design/issues/37588

### What does the proposed API look like?

```tsx
const [activeValue, setActiveValue] = useState<string[]>([])

<Cascader
  activeValue={activeValue}
  onActive={setActiveValue}
/>
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: tauri
Issue: [docs] Correct shell.open api example
Labels: type: documentation

In docs,the demo of shell.open is below:

```javascript
import { open } from '@tauri-apps/api/shell';
// opens the given URL on the default browser:
await open('https://github.com/tauri-apps/tauri');
// opens the given URL using `firefox`:
await open('https://github.com/tauri-apps/tauri', 'firefox');
// opens a file using the default program:
await open('/path/to/file');
```

However,the last `opens a file` is not supported since the default pattern is `^((mailto:\w+)\|(tel:\w+)\|(https?://\w+)).+`
Repository: PowerToys
Issue: MWB device layout not maintained when switching from non-elevated > elevated instance of Powertoys
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.78.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

- Open non-elevated PowerToys;
- Setup MWB with multiple Devices;
- On left bar, select 'General' (Settings cog icon);
- Select 'Restart PowerToys as Administrator';
- Check MWB.

### ✔️ Expected Behavior

Monitor to retain position from non-elevated to elevated privilages.

### ❌ Actual Behavior

Restarting as admin causes positions set to revert:
![1](https://github.com/microsoft/PowerToys/assets/36490238/86dd815e-f03f-4198-9182-1055bf0e5f84)
![2](https://github.com/microsoft/PowerToys/assets/36490238/ec4789f1-c94e-4252-bbd3-d9d81085c2b6)
![3](https://github.com/microsoft/PowerToys/assets/36490238/5fe0aeb3-1311-47cd-af5c-d875ab3ccd7c)
![4](https://github.com/microsoft/PowerToys/assets/36490238/bdef660d-4964-4a54-bc5c-f232a8a7a8a8)

### Other Software

N/A
Repository: PowerToys
Issue: When I start Powertoys, the search box in Task Manager becomes unusable.
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Repro,Needs-Triage,Area-App Compat

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

[PowerToysReport_2024-02-29-21-56-01.zip](https://github.com/microsoft/PowerToys/files/14448259/PowerToysReport_2024-02-29-21-56-01.zip)

1. Start Powertoys.
2. Immediately the search box in Task Manager becomes unavailable.
3. 100% reproducibility, mission accomplished.

### ✔️ Expected Behavior

Task Manager's search box becomes available.

### ❌ Actual Behavior

When I click the search box in Task Manager, it doesn't respond, so I can't use the keyboard.
You can input by moving the focus with Tab.
When you end a Powertoys task from Task Manager, the search box becomes available immediately.

### Other Software

Please refer to the attached PowerToysReport.
Repository: go
Issue: os: expand support for Windows Deduplication Reparse Points to Include SIS (NTFS)
Labels: OS-Windows,NeedsInvestigation

I ran into an issue using [restic](https://github.com/restic/restic/) where Windows [SIS](https://en.wikipedia.org/wiki/Single-instance_storage) [reparse points](https://en.wikipedia.org/wiki/NTFS_reparse_point#Data_deduplication) on an NTFS file system were failing to back up. After some discussion, it was pointed out that the new Windows NTFS deduplication [is supported nicely in Go](https://github.com/restic/restic/issues/4704#issuecomment-1970061128).

Here is where I was shown support for the new Windows NTFS deduplication scheme: [(https://tip.golang.org/src/os/types_windows.go#L201](https://tip.golang.org/src/os/types_windows.go#L201). I'm not 100% sure, but I think the old-style SIS deduplication could be handled the same way, just with a different reparse tag.
Repository: go
Issue: go/printer: build constraints are moved above block comments
Labels: NeedsInvestigation

### Go version

go version go1.22.0 darwin/arm64

### Output of `go env` in your module/workspace:

```shell
Not relative
```


### What did you do?

1. <https://go.dev/play/p/XfUekq-wb8i>
2. Click the `format` button or run `go fmt`

```go
/* Ok, the LICENSE is...
 * UNLICENSED
 */

// some test comments here

//go:build !ignore

// some package description
package main
```

### What did you see happen?

```go
//go:build !ignore

/* Ok, the LICENSE is...
 * UNLICENSED
 */

// some test comments here

// some package description
package main
```

### What did you expect to see?

Nothing should happen, so

```go
/* Ok, the LICENSE is...
 * UNLICENSED
 */

// some test comments here

//go:build !ignore

// some package description
package main
```
Repository: godot
Issue: VehicleWheel3D spring length is being calculated incorrectly
Labels: bug,topic:physics,topic:3d

### Tested versions

4.3

### System information

nixos-unstable

### Issue description

There have been bug reports revolving weird spring behaviors before. For some users, the wheels appear to clip into the floor, when [their suspension strength is simply set too low](https://github.com/godotengine/godot/issues/45339#issuecomment-1050273752_)

Initially I thought this was caused by the wheels not being transformed at all, however I now discovered they are simply not transformed correctly.

### Steps to reproduce

1. Set up a VehicleBody3D with wheels
2. Attatch a visual instance to the wheels
3. Run the game

You will likely see the suspension not being able to hold up the vehicle. You will also likely see the wheels clipping trough the floor.

### Minimal reproduction project (MRP)

[minimal_vehicle_bug.zip](https://github.com/godotengine/godot/files/14448808/minimal_vehicle_bug.zip)
Repository: angular
Issue: RouterTestingHarness: Provide an option to configure  the root component
Labels: feature,action: discuss,area: router

### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

In some integration tests you'd like more control over the boostrapped root component.

Guards on lazy routes, for instance, are initialized before any of the parent components are instantiated. This causes issues when trying to (integration) test (automatic) login scenarios.

### Proposed solution

Ideally you'd pass in a higher order component which is composed with the original root component; but since functional components are not a thing that seems like a long shot at best. So you'd probably have to implement your own `RouterTestingHarnessRootComponent`:
```
const routerHarness = await RouterTestingHarness.create({
  initialUrl?: string;
  root?: RouterTestingHarnessRootComponent;
);
```

### Alternatives considered

You can manually create a test root component first:
```
TestBed.createComponent(RootComponent);
routerHarness = await RouterTestingHarness.create();
```
This works if you re-use this component in your provided routes but it's only a workaround since the component is created twice.
Repository: TypeScript
Issue: Show deprecated strikethrough for JSX properties when union type
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

"strikethrough deprecated prop jsx", "strikethrough deprecated prop react", "strikethrough deprecated property jsx", "strikethrough deprecated property react", "deprecated property react", "deprecated property jsx"

### ✅ 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

I came across #50079 and the fix #50084 which works nicely when the whole property is deprecated. However it's also possible to create a type like the following:

```
{
  myProp: 'a' | 'b' | 'c'
} | { 
  /** @deprecated use 'a' | 'b' | 'c' */
  myProp: 1 | 2 | 3
}
```

This still correctly shows the deprecated message when hovered over the property in JSX when the value of the property is 1, 2, or 3, and not when the value is 'a', 'b' or 'c'. However the property is never shown with a strikethrough. It would be fantastic if the strikethrough on the property could match the deprecated message behaviour in the hover pop over.  

### 📃 Motivating Example

TypeScript has now extended deprecation checking in JSX to visually add a strikethrough to a property when the property is still valid, but a deprecated value for the property is used (see example in the suggestion above).

### 💻 Use Cases

1. What do you want to use this for?
When transitioning a React component's property to a new set of values it would be useful to maintain the old values for backwards compatibility but deprecate them to visually indicate to a user that they should no longer be using them. My specific use case is when the original values were less explicit: 
```
size: 'classname-small' | 'classname-medium' | 'classname-large'
```
and I'm transitioning the new type to be:
```
size: 's' | 'm' | 'l'
```
and would like to support both types in the interim, but notify uses explicitly to use the new values.
2. What shortcomings exist with current approaches?
There is no visual indication that the value is deprecated without hovering over the property
3. What workarounds are you using in the meantime?
It's not possible to workaround. Just have to deal with it only being in the pop up
Repository: PowerToys
Issue: Screen Ruler - Display ratio
Labels: Idea-Enhancement,Product-Screen Ruler

### Description of the new feature / enhancement

Add an option to display the ratio (x/y) of the bounds (or spacing) measure tool.
![image](https://github.com/microsoft/PowerToys/assets/51906791/087c0658-1582-4788-94ac-8d1d0fbbb3a3)


### Scenario when this would be used?

I very often use the spacing or bounds measure only to check that the ratio of an image displayed is what I expect and it is not being transformed from 16/9 to 16/10 for example. It would save me some time not to have to put these numbers in a calculator everytime.

### Supporting information

_No response_
Repository: kubernetes
Issue: Eviction manager: When stats calls failed, we evict the pod that we couldn't get stats for.
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

### What happened?

As I was investigating the eviction tests, I discovered an interesting problem. We are seeing a wide range of flakes where the one pod that should not be evicted gets evicted in the eviction test.  

Eviction tests work by assigning one pod that it should never be evicted and then it ranks these pods and evicts the other pods. If there is a stats API failure, we evict the pod that we couldn't get stats for.

This seems to be by design (cc @derekwaynecarr)

### What did you expect to happen?

We should maybe consider a more deterministic approach if stats fails.

### How can we reproduce it (as minimally and precisely as possible)?

Try running the eviction tests on the PR.

### Anything else we need to know?

Code that causes this is here:

https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/eviction/helpers.go#L747



### Kubernetes version

all supported

### Cloud provider

na

### OS version

na

### Install tools

na

### Container runtime (CRI) and version (if applicable)

crio and containerd

### Related plugins (CNI, CSI, ...) and versions (if applicable)

_No response_
Repository: godot
Issue: text cursor is invisible when renaming nodes on BSPWM
Labels: bug,platform:linuxbsd,topic:porting,topic:gui

### Tested versions

reproducible in 4.2.1.stable.mono and 4.1 iirc

### System information

Godot v4.2.1.stable.mono - Arch Linux #1 SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:31:48 +0000 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3060 Ti (nvidia; 550.54.14) - AMD Ryzen 5 7600X 6-Core Processor (12 Threads)

### Issue description

the I-shaped cursor that appears when writing text is invisible when renaming nodes on BSPWM, as far as i can tell this is the only place where it happens as otherwise, on node properties or filesystem, its fine

### Steps to reproduce

rename any node on BSPWM

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: Canvas.saveLayer emits tracing is flaky
Labels: P2,team-engine,triaged-engine

https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20Production%20Engine%20Drone/618153/overview

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8754755997407041505/+/u/test:_test:_Host_Tests_for_host_debug_unopt/stdout

build host_debug_unopt and run:

```
out/host_debug_unopt/exe.unstripped/flutter_tester --force-multithreading --enable-impeller --use-test-fonts --icu-data-file-path=out/host_debug_unopt/icudtl.dat --flutter-assets-dir=out/host_debug_unopt/gen/flutter/lib/ui/assets --disable-asset-fonts 
 out/host_debug_unopt/gen/tracing_test.dart.dill
```
Repository: storybook
Issue: [Bug]: v8 `automigrate` creates `package.json` at project root
Labels: bug,nx,monorepos,sev:S2

### Describe the bug

I ran `npx storybook@next upgrade --config-dir apps/my-app/.storybook` on a Nx monorepo. Everything worked smoothly (apart from `viteConfigFile` but [I created another issue](https://github.com/storybookjs/storybook/issues/26260) for it).

However, even though it did find the workspace root `package.json` (since it updated the Storybook dependencies, and removed the packages that needed to be removed, like `@storybook/testing-library`, `@storybook/jest` etc), it ended up created another `package.json` inside the nested project's directory (eg. `apps/my-app`).

### To Reproduce

Here is my reproduction repository: https://github.com/mandarini/storybook-upgrade-latest-nx

You can see the [storybook upgrade commit](https://github.com/mandarini/storybook-upgrade-latest-nx/commit/0801be45f943d691cea8d482f8715459bc730c3c#diff-566f888b55d24f1c40ef9594242233f489ffc2d5a1408912c01611976986a367) which created the new `package.json`.

### System

```bash
npx storybook@next info

Storybook Environment Info:

  System:
    OS: macOS 13.5
    CPU: (12) arm64 Apple M2 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm <----- active
    pnpm: 8.6.11 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 122.0.6261.69
    Safari: 16.6
  npmPackages:
    @storybook/addon-essentials: ^8.0.0-rc.0 => 8.0.0-rc.0
    @storybook/addon-interactions: ^8.0.0-rc.0 => 8.0.0-rc.0
    @storybook/core-server: ^8.0.0-rc.0 => 8.0.0-rc.0
    @storybook/react-vite: ^8.0.0-rc.0 => 8.0.0-rc.0
    @storybook/test: ^8.0.0-rc.0 => 8.0.0-rc.0
    @storybook/test-runner: ^0.13.0 => 0.13.0
    storybook: ^8.0.0-rc.0 => 8.0.0-rc.0

```
```


### Additional context

_No response_
Repository: pytorch
Issue: Symbolic shape tests don't actually test that arguments aren't specialized
Labels: module: tests,triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

For example, this means that https://github.com/pytorch/pytorch/pull/120776 didn't cause an xfail to be removed. This is suboptimal.

The difficulty here is that we need to actually annotate which inputs are expected to be specialized and which are not.

Prior to us switching to automatically specializing, we could sort of get some coverage info because if someone called `.size()` this would hard error, but now it doesn't anymore.

### Versions

main

cc @mruberry @ZainRizvi @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang