sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Unchanged files recompiled for each page navigation in dev build
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101
    Binaries:
      Node: 16.15.0
      npm: 8.5.5
      Yarn: N/A
      pnpm: 7.25.1
    Relevant packages:
      next: 12.3.0
      eslint-config-next: N/A
      react: 18.1.0
      react-dom: 18.1.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-yppvvt?file=pages/_app.tsx

### To Reproduce

Create a shared backend file which generates a random number at import-time, and returns that from a function. Import this file from several different routes. Observe that as you navigate to each new route, the number changes. Once you go back, the number is consistently the new number.

### Describe the Bug

Unchanged modules are recompiled upon navigation to another page which also uses it, leading to slower development, and issues around connection re-use and reinitializing of services (which can be mitigated via "hacks" like storing in global variables, but not ideal).

This is especially painful with common files such as "DatabaseHelper", which encapsulates database connections. In my application, we have a shared "getInitialProps" across all routes, which imports into our entire backend. Every page change in development (until each route is compiled) has to rebuild that one import, which leads to 3000 dependent modules recompiling. This is made even more painful by the fact that after several route loads, the original route needs to be recompiled upon navigation to it (perhaps due to memory constraints).

Additionally this seems to lead to high memory usage, and eventual OOMs (potentially due to files which expect to be singletons not cleaning themselves up — but if the framework didn't force many instances to be created, or gave a way to cleanup when the module is reloaded, it would be easier)

### Expected Behavior

Once a module is imported, it should be cached until it changes and needs hot reloading (or at a minimum, until some file changes, requiring a full rebuild).

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Other platform
Repository: pytorch
Issue: [LibTorch] pickle_save output cannot be reloaded using pickle_load in Windows
Labels: oncall: jit

### 🐛 Describe the bug

For the following code, it works in Mac but crashed in Windows for the last step

```
#include <torch/script.h>

torch::jit::IValue tensor(torch::randn({1, 64}));
std::vector<char> input = torch::jit::pickle_save(tensor);
tensor = torch::jit::pickle_load(input);
```
Error messages:
`Microsoft C++ exception: c10::Error at memory location 0x0000000C8155E460`

### Versions

LibTorch version is latest stable 1.13.1.

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: stable-diffusion-webui
Issue: [Bug]: Launching the webui never got further "Loading weights [dcd690123c]"
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

Hello. I have a Radeon VII graphic card and freshly installed EndeavourOS to try out this amazing software. My problem is the program never going further than this line:
`Loading weights [dcd690123c] from /home/palinko/Desktop/stable-diffusion-webui/models/Stable-diffusion/v2-1_768-ema-pruned.safetensors
`

I've tried to load 4 different models both ckpt and safetensors, nothing worked and nothing loaded unfortunatelly. Even if I'm waiting a lot of time, processor remainst at 4% python, and ram is around 5-6GB but nothing happening. I got no error message so hard to figure out what went wrong. I tried to edit the webui-user and play with the arguments but not solved problem.

### Steps to reproduce the problem

1. source venv/bin/activate
2. TORCH_COMMAND='pip install torch torchvision --extra-index-url https://download.pytorch.org/whl/rocm5.1.1' python launch.py --precision full --no-half

or

1. ./webui.sh


### What should have happened?

Should not stall.

### Commit where the problem happens

5c1cb9263f980641007088a37360fcab01761d37

### What platforms do you use to access UI ?

Linux

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

```Shell
export COMMANDLINE_ARGS="--no-half --precision full --opt-split-attention --opt-sub-quad-attention --api"

export TORCH_COMMAND='pip install torch torchvision --extra-index-url https://download.pytorch.org/whl/rocm5.1.1' python launch.py --precision full --no-half
```


### Additional information, context and logs

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Symmetrical Outpainting
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 ?

A checkbox that allows the outpainted area to be symmetrical.

### Proposed workflow

* User can select the `symmetrical` check box
* If checked, expanded area matches on both sides
** Might require Left/Right or Up/Down only

Currently, I'd have to photoshop one side onto another. It would be better if, instead copying the image after all the steps, each step can be copied over and continue to be rendered on the other side. 

Flow for expanding an image left and right:
* 256px of space added to the left side of the canvas
* X steps happen
** suggested 2-4 steps
* Copy the 256x512 image
* Add 256px to the right of the canvas
* Flip and paste in the copied image
* X Steps
* Repeat until done
* Optionally allow X steps at the end to remain on respective side
** Allows for unique features to appear



### Additional information

Images of the problem I'm running into: 
https://www.reddit.com/r/StableDiffusion/comments/10jprya/how_do_i_get_symmetrical_outpainting/
Repository: flutter
Issue: Flutter align text to the bottom and on the same textBaseline doesn't work
Labels: framework,a: layout,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-framework,triaged-framework

TextBaseline not working...
- `crossAxisAlignment: CrossAxisAlignment.baseline` can't use with `InstrisicHeight`
- without `InstrisicHeight`, `Vericaldivider` will not render (height = 0)

## Steps to Reproduce

<!-- Please include full steps to reproduce so that we can reproduce the problem. -->

1. Execute `flutter run -d chrome on the code sample

**Expected results:** <!-- what did you want to see? -->
- "ASDASDASDASDASDAS" should align the text baseline with "very long long... text"

**Actual results:** <!-- what did you see? -->
![image](https://user-images.githubusercontent.com/80244566/214207976-766adfe9-879c-47f5-bacf-11aee36a8a56.png)


<details>
<summary>Code sample</summary>

```
class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Column(
        crossAxisAlignment: CrossAxisAlignment.start,
        children: [
          Text(
            "titleeeeeeee",
            style: const TextStyle(
              fontFamily: "WorkSans",
              fontStyle: FontStyle.normal,
              fontWeight: FontWeight.w900,
              fontSize: 14,
              letterSpacing: 1,
            ),
          ),
          IntrinsicHeight(
            child: Row(
              crossAxisAlignment: CrossAxisAlignment.end,
              textBaseline: TextBaseline.alphabetic,
              children: [
                Expanded(
                  child: Text(
                    "very long long long long long long long long long long long long long long long long long long long long... text",
                    style: const TextStyle(
                      fontSize: 34,
                      letterSpacing: 1,
                    ),
                  ),
                ),
                VerticalDivider(
                  thickness: 1,
                  color: Colors.black,
                ),
                Expanded(
                  child: Text(
                    "ASDASDASDASDASDAS",
                    style: const TextStyle(
                      fontSize: 17,
                      fontStyle: FontStyle.italic,
                      fontWeight: FontWeight.w900,
                      letterSpacing: 1,
                    ),
                  ),
                ),
              ],
            ),
          )
        ],
      ),
    );
  }
}
```

</details>
Repository: vscode
Issue: Document Content Providers are being passed URI-unescaped paths when invoked through the DAP
Labels: bug,debug

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.74.3
- OS Version: Win11 22H2 22621.1105

Steps to Reproduce:

1. We have an implementation of the DAP for our language server, and in response to the `stacktrace` call, we return `stackframes` which contain URI-escaped filenames as the `Path` property of  `Source`. Something like this:
![image](https://user-images.githubusercontent.com/39045749/214208719-38389e89-8023-4a65-bb9c-5737163208b2.png)

2.  When VSCode handles this response and calls our document content provider, it has un-escaped the URI. This generates an invalid filename.
![image](https://user-images.githubusercontent.com/39045749/214208811-1a1c5c75-91f0-42b8-a042-d913a0e9141a.png)

We'd expect that the `Path` sent to the document content provider is the same as the `Path` we sent as part of the `stacktrace` call.
Repository: kubernetes
Issue: Volume populators should use resource instead of kind
Labels: kind/bug,priority/important-soon,sig/storage,lifecycle/rotten,needs-triage

### What happened?

While discussing the ReferenceGrant kep, I learned that there is a distinction between "resource" and "kind". The biggest takeaway is that "group + kind" is not uniquely identifiable for arbitrary resources (for in-tree apis we can enforce).

refs:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#kind-vs-resource
https://github.com/kubernetes/enhancements/pull/3767/files#r1084662831


### What did you expect to happen?

The implications are that we should be using `resource` instead of `kind` in `PVC.dataSourceRef` and `VolumePopulator.sourceKind`.

We need to resolve this before volume populators goes GA.

cc @bswartz @jsafrane @xing-yang 

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

n/a

### 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: stable-diffusion-webui
Issue: [Bug]: Ubuntu 22.04.1 | RX 6800XT | "Torch is not able to use GPU; add --skip-torch-cuda-test..."
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

- Attempted to install the UI using both the automated install and the one located on the wiki for AMD GPUs. 
- Previously I had installed the drivers for ROCm 5.4.2 so I started fresh on a new Ubuntu install and had the same results.
- Output is the same whether run through the automated script or follow the wiki, shown below.
![image](https://user-images.githubusercontent.com/83607645/214222070-fec2bc14-f7db-4e79-81bd-73c1e9655500.png)


- As an addendum I was running Arch before then swapped to Ubuntu and the automated script install went fine on there. At least it seemed to. Didn't generate any images with it but opened the Web UI. I can try it out later tomorrow on Arch again and see what happens.



### Steps to reproduce the problem

1. Be running on Ubuntu 22.04.1.
2. Have a 6800XT
3. Attempt to run automated install / install mentioned in Wiki for AMD GPUs
4. Receive error.

### What should have happened?

- Automated install should work on Ubuntu 22.04

### Commit where the problem happens

5c1cb9263f980641007088a37360fcab01761d37

### What platforms do you use to access UI ?

Linux

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

_No response_

### Additional information, context and logs

- I did see that the issue seems to have been addressed in a manner in this [pull request](https://github.com/AUTOMATIC1111/stable-diffusion-webui/pull/6709) though I'm not sure if this would address my exact problem but it might. Might be specific to 22.04 if the rocm version being used is 5.1.1 as 22.04 isn't support according to [here](https://docs.amd.com/bundle/ROCm-Installation-Guide-v5.1/page/Introduction_to_ROCm_Installation_Guide_for_Linux.html)
Repository: storybook
Issue: [Bug]: TypeError when not specifying stories in v7
Labels: bug,needs triage

### Describe the bug

If you comment out, the stories option in the following config,
```
module.exports = {
  stories: ['../components/*.stories.ts'],
  core: {
    disableTelemetry: true,
  },
  framework: {
    name: '@storybook/vue3-vite',
    options: {},
  },
}
```
then storiesbooks fails with
```
info => Starting manager..
D:\Programming\JabRefOnline\node_modules\@storybook\core-common\dist\index.js:807
    normalizeStories = (entries, options) => entries.map(entry => normalizeStoriesEntry(entry, options));       
                                                     ^

TypeError: Cannot read properties of undefined (reading 'map')
    at normalizeStories (D:\Programming\JabRefOnline\node_modules\@storybook\core-common\dist\index.js:807:54)  
    at getStoryIndexGenerator (D:\Programming\JabRefOnline\node_modules\@storybook\core-server\dist\index.js:20:640)
```

### To Reproduce

```shell
https://github.com/JabRef/JabRefOnline/pull/1726
```


### System

```shell
Environment Info:

  System:
    OS: Windows 10 10.0.22621
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-1280P
  Binaries:
    Node: 19.4.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 3.3.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 9.2.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1105.0), Chromium (109.0.1518.61)
  npmPackages:
    @storybook/core-server: ^7.0.0-beta.32 => 7.0.0-beta.32
    @storybook/vue3: ^7.0.0-beta.32 => 7.0.0-beta.32
    @storybook/vue3-vite: 7.0.0-beta.32 => 7.0.0-beta.32
```


### Additional context

_No response_
Repository: PowerToys
Issue: No .tga support for Power Resize
Labels: Idea-Enhancement,Help Wanted,Product-Image Resizer

### Description of the new feature / enhancement

It would be nice for .tga files to be supported by the image resizer tool.

### Scenario when this would be used?

Game development, 3d modelling, and other applications that utilize tga files.

### Supporting information

_No response_
Repository: PowerToys
Issue: [PowerToys Run] Jump to virtual desktop.
Labels: Idea-Enhancement,Product-Virtual Desktop,Run-Plugin

### Description of the new feature / enhancement

# Feature request: [PowerToys Run] Jump to desktop.

## Expected behaviour:

### Use case: jump by number.
1. User presses 'Alt+Space' to open PowerToys Run.
1. User types '*activation-command* 4' and presses Enter.
2. PowerToys Run takes the user to desktop 4.

### Use case: jump by label.
1. User presses 'Alt+Space' to open PowerToys Run.
1. User types '*activation-command* work' and presses Enter.
2. PowerToys Run takes the user to desktop with the label 'work'.

### Scenario when this would be used?

I organize my workflow by desktops. There is a desktop dedicated to 'work', 'chat', etc., and while I can simply jump to a window on that desktop (which is what I've been doing so far), it would be more convenient to simply jump to the desktop.

### Supporting information

_No response_
Repository: rust
Issue: Separate clauses and goals from the Predicate type
Labels: C-cleanup

Split up the `PredicateKind` type into `Goal` and `Clauses` similar (or exactly :D) like what chalk does. The TLDR is that ParamEnv only contains a small set of `PrecicateKind` variants and we want to encode this in the type system by only returning `Clause`s from it.

This projection has been accepted as an MCP: https://github.com/rust-lang/compiler-team/issues/531

## Implementation steps

* [x] [SP] Split out `Trait`, `TypeOutlives`, `RegionOutlives` and `Projection` into `Clause` enum: [#104846](https://github.com/rust-lang/rust/pull/104846)
* [x] [SP] [#104911](https://github.com/rust-lang/rust/pull/104911) `inferred_outlives_crate` returns predicates, but they are always only TypeOutlives or RegionOutlives
    * may kill perf, so let's see if it works to just return ty::Clause where it now returns `ty::Predicate` and build the predicates at the caller site of `inferred_outlives_of`
* [x] doing the same thing for `explicit_predicates_of` is gonna be a bit more involved
* [ ] Improve perf of [#104846](https://github.com/rust-lang/rust/pull/104846)
* [x] start with `gather_explicit_predicates_of` and convert at the caller sites
* [x] `Bounds::predicates` should return an iterator over Clauses (#112734)

Follow-up work after #112938:
* [ ] Investigate making `TypeFoldable<TyCtxt<'tcx>> for ty::Clause<'tcx>` implementation less weird: https://github.com/rust-lang/rust/blob/2efe09170530fa18e42ff05b8d9dd23f00b5c430/compiler/rustc_middle/src/ty/structural_impls.rs#L672
* [ ] Clean up the elaborator since it should only be emitting child clauses, not predicates
* [ ] Rename identifiers like `pred` and `predicates` to `clause` if they're actually clauses around the codebase
* [ ] Validate that all of the `ToPredicate` impls are acutally still needed, or prune them if they're not

leave a comment when you start working on one of these steps so that no one else duplicates work.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: stable-diffusion-webui
Issue: [Bug]: training embeddings with textual inversion is not possible on CPU
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

I have a 4GB graphic card, so there's no way to use it for training. I've tried to train on CPU, but got error from GradSclaer `assert outputs.is_cuda or outputs.device.type == 'xla'`.
Probably should be replaced with `ShardedGradScaler`, I'm not very good at Python so wasn't able to implement it properly and ended up with replacing `scaler` lines with the ones, that were used before scaler was added. This way training works fine, as far as I can see.

### Steps to reproduce the problem

1. Go to webui-user.sh and set COMMANDLINE_ARGS="--use-cpu all --no-half";
2. Start web UI;
3. Start training embedding;
4. Get error from GradScaler.


### What should have happened?

Training on CPU works without errors.

### Commit where the problem happens

e33cace2c2074ef342d027c1f31ffc4b3c3e877e

### What platforms do you use to access UI ?

Linux

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

```Shell
--use-cpu all --no-half
```


### Additional information, context and logs

_No response_
Repository: kubernetes
Issue: APF: Understand the failures of 5k scalability tests with client-side rate-limitting disabled
Labels: sig/scalability,sig/api-machinery,triage/accepted

The results can be found in:
https://github.com/kubernetes/kubernetes/pull/109614

Facts:
- latency metrics include waiting time in APF
- so basically, long waiting time (saturated PLs) would result in exactly this

Hypothesis:
- some PLs are saturated and thus latency metrics are exceeding the threshold

But we need to confirm this and figure out how to improve it.

[The next step would be to see how we can speed up this test even further and see what will happen later, but I think we're currently mostly blocked on scheduler throughput.]

/assign @MikeSpreitzer 
/cc @tkashem
Repository: three.js
Issue: SVGLoader: Shape generation breaks with large stroke width.
Labels: Bug,Loaders

### Description

The original issue was reported at the forum: https://discourse.threejs.org/t/glitches-with-svg-loader/46803

SVGs that exceed a certain `stroke-width` are not rendered correctly. As visible in the below screenshot, the resulting shape is rendered with additional triangles on its back side. When decreasing the stroke width (in the below SVG try 200), the issue goes away.

 I suspect there is a problem in [SVGLoader.pointsToStrokeWithBuffers()](https://github.com/mrdoob/three.js/blob/4a6cf23c5f69ecde00e79171be7235deb39dff79/examples/jsm/loaders/SVGLoader.js#L2412) which generates triangles based on the stroke definition from the SVG.

### Reproduction steps

1. Load the following SVG with the loader to reproduce the glitch.
```
<?xml version="1.0"?>
<svg viewBox="0 0 600 792" width="600" height="792">
  <path stroke="#64C36E" fill="none" id="link_2_21_ok" d="M30,463.61904761904765C150,463.61904761904765,150,571.0476190476189,270,571.0476190476189" stroke-width="290" stroke-opacity="0.6"/>
</svg>
```

### Code

- See fiddles.

### Live example

* [jsfiddle-latest-release](https://jsfiddle.net/f5veyqst/2/)
* [jsfiddle-dev](https://jsfiddle.net/f5veyqst/)


### Screenshots

![image](https://user-images.githubusercontent.com/12612165/214255601-3691a33b-891f-4698-9f9b-891afc86264f.png)


### Version

r148

### Device

Desktop, Mobile, Headset

### Browser

Chrome, Firefox, Safari, Edge

### OS

Windows, MacOS, Linux, Android, iOS