sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: fetches with `cache: no-store` using the `Request` object are still cached on Vercel when using edge runtime and fetchCache is set to `default-cache` 
Labels: bug,Pages Router

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 23.0.0: Tue Jul 18 20:35:19 PDT 2023; root:xnu-10002.0.199.505.1~3/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 8.6.7
    Relevant Packages:
      next: 13.4.14-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Data fetching (gS(S)P, getInitialProps)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/Fredkiss3/fetch-cache-no-store-vercel-bug

### To Reproduce

1. go to the deployed site at : https://fetch-cache-no-store-vercel-bug.vercel.app/
2. reload the page multiple times, only the first fetch (`Fetch (with URL)`) will update while the second will always display the same time 

### Describe the Bug

Using the `Request` object with fetch will still cache the fetch request even if we pass `cache: no-store` to the request init. This bug only happens on edge runtime and if `fetchCache` is set to `default-cache` :

```ts
export const runtime = "edge";
export const fetchCache = "default-cache";
```

This issue also appears only on **vercel**, it works fine locally with a production build.



Other times it works fine



### Expected Behavior

the `cache` field should be respected  even if we pass a `Request` object to fetch wether in edge runtime or not.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

vercel
Repository: kubernetes
Issue: client-go should log with the context
Labels: sig/api-machinery,kind/feature,sig/instrumentation,triage/accepted,wg/structured-logging

### What happened?

we are using the `klog` to do logs, it can be changed by setting the `klog` default logger.

and we have `ctx Context` param in `request`

https://github.com/kubernetes/kubernetes/blob/815b18a46133723b4a08618bb801d2683605a273/staging/src/k8s.io/client-go/rest/request.go#L965

but klog can only print some fixed messages.

### What did you expect to happen?

Context can be used to deliver logger, like controller runtime: 

https://github.com/kubernetes-sigs/controller-runtime/blob/357eb831348772933a2b07b7deeae584538154d0/pkg/log/log.go#L91

if so, we can log more detail in request.


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

trigger requests throttling.

will produce:

```
│{"level":"info","ts":"2023-08-08T10:00:22+08:00","logger":"klog","msg":"Waited for 11.366890166s due to client-side throttling, not priority and fairness, request: GET:/apis/policy.krui│se.io/v1alpha1?timeout=10s\n"}
```

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
1.27
```

</details>


### Cloud provider

<details>
N/A
</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: [Feature Request]: xyz plot prompt weighting, something like prompt s/r to replace weights instead of text
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 ?

after waiting for long and now searching the web again i cant believe there is still no proper feature of xyz plot to test weights since this seems the most obvious and would probably be one of the most used features of xyz plot since finding the right weights is one of the most important parts of prompt engineering. thought somebody must have requested this already but since after months still nothing happened and i didnt find anything i thought i might have to request it myself.
if i didnt miss anything the only solution for that right now is to manually type in the prompt s/r value field: dog, dog:0.1, dog:0.2, dog:0.3, ... to have prompt s/r replace the whole word dog with a weighted dog without being able to automate that by specifying a range and increments with its existing syntax.
 
so what id want would be either a syntax for prompt s/r or another kind of prompt s/r to replace something attached to a word prompt s/r is looking for including the ability to use a range and increment for numerical values, for weighting it could be something like dog :0-1 (+0.1) where the space in front of the : would trigger weighting with the already existing range and increment syntax instead of replacing the whole word itself, something like that.

that way it could also be used for lora, lyco, hypernetwork, embedding or whatever weights without the need for something like addnet extension to chose a lora like addnet weight does (or without running in trouble with lycos for that matter since addnet still doesnt support selecting lycos so i guess i cant properly test lyco weights the same way as lora weights atm and have to manually type lyco weights like in my dog example...).

of course it would also be cool to have xyz plot get a general overhaul with an upgraded ui for more possible fields or sliders to not run into that problem like we have here where we just dont have enough fields to separate a search word and a numerical value or range with increments so we have to solve it with syntax to do everything within that same old single value field, and maybe even eventually get some features like plot saving/loading and the multitool from extended xy plot extension to add syntax for multiple tested parameters on the same axis, ive been patiently waiting for that since forever now since i thought those are so obvious they would have to come to this script soon. 
but well, adding/changing syntax to be able to test weights at least should be the fast and easy temporary solution till one day we might actually get that stuff id guess.

### Proposed workflow

use syntax in prompt s/r like something like dog :0-1 (+0.1) for example to replace the weight instead of the word to get an output grid of a range of weights on an axis.

### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: Outputting someone's username with the prompt in command line
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 ?

I am not sure if this is already available, so I am requesting this as a feature. 

It would just be a batch file argument or command line argument enabling this if you have --gradio-auth for usernames like accounts and stuff. I want the username of whoever makes a certain prompt to be shown when you enable console prompts so I can easily moderate who is making what and be able to easily remove whoever I see not using the AI appropriately.

### Proposed workflow

1. Go to the webui-user.bat
2. Add the --enable-console-prompts argument to the batch file
3. Shows the username in the prompts.


### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: centos安装,pip版本始终不对，访问不到https
Labels: asking-for-help-with-local-system-issues

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

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/29546184/b08348e4-c049-4de8-b90e-a4f607589cb3)
但插看版本是23.2.1
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/29546184/f3fc0d92-74b6-45fb-95cb-9e0648e284b5)
还有老报https连不上。


### Proposed workflow

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/29546184/b08348e4-c049-4de8-b90e-a4f607589cb3)
但插看版本是23.2.1
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/29546184/f3fc0d92-74b6-45fb-95cb-9e0648e284b5)
还有老报https连不上。



### Additional information

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/29546184/b08348e4-c049-4de8-b90e-a4f607589cb3)
但插看版本是23.2.1
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/29546184/f3fc0d92-74b6-45fb-95cb-9e0648e284b5)
还有老报https连不上。
Repository: next.js
Issue: Window object  in a particular component causing the enitire page to get client side rendered instead of throwing an error ( while using use client)
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Development
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/epic-shadow-69d2jy?file=%2Fapp%2Fpage.tsx%3A4%2C1

### To Reproduce

In the sand box I ahve added two componets  **CompA** and **CompB** , while adding window object in CompB , CompA also gets Client side rendered 

### Describe the Bug

In the sand box I ahve added two componets  **CompA** and **CompB** , while adding window object in CompB , CompA also gets Client side rendered 
It should either throw an error thatw indow is not found or SSr the page with CompA only right ?

### Expected Behavior

It should either throw an error that indow is not found or SSr the page with CompA only right ?

### Which browser are you using? (if relevant)

Chrome

### How are you deploying your application? (if relevant)

_No response_
Repository: material-ui
Issue: [TextField][material-next] Add v7 TextField component
Labels: umbrella,on hold,component: text field,design: material you

This is an umbrella issue for tracking the work on adding `TextField` to `@mui/material-next` as part of the Material You effort (https://github.com/mui/material-ui/issues/29345)

Material Design 3 TextField specs: https://m3.material.io/components/text-fields/specs

### Prerequisites

As TextField is composed from several components, we have issues tracking work for the constituent parts:

- [x] https://github.com/mui/material-ui/issues/38372
- [x] https://github.com/mui/material-ui/issues/38411
- [x] https://github.com/mui/material-ui/issues/39052
- [x] https://github.com/mui/material-ui/issues/39512
- [ ] https://github.com/mui/material-ui/issues/39628 (internally it also depends on `Typography`)
- [x] https://github.com/mui/material-ui/issues/39513
- [ ] https://github.com/mui/material-ui/issues/39695
- [ ] https://github.com/mui/material-ui/issues/39696

These look related but are not: `FormControlLabel`, `FormGroup`

### New Features/Breaking Changes

#### TextField

- [ ] Drop the built-in `Select` [#21782](https://github.com/mui/material-ui/issues/21782)
- [ ] Drop Standard variant, we were still supporting it even though it was dropped from Material Design 2 ([source](https://medium.com/google-design/the-evolution-of-material-designs-text-fields-603688b3fe03))
- [ ] Rename `inputComponent` to `component` https://github.com/mui/material-ui/pull/39032#issuecomment-1737563093
- [ ] Integrate better with `<input type="reset">` https://github.com/mui/material-ui/issues/39302

#### FormControl

- [ ] Pass `disabled` attribute if the underlying element is a `fieldset` https://github.com/mui/material-ui/issues/38932
- [ ] Refactor the context and hook so that it extends Base UI's FormControl to provide Material UI features (discussed in https://github.com/mui/material-ui/issues/38411)
- [ ] Allow rendering a `Fragment` https://github.com/mui/material-ui/issues/38094



#### InputAdornment

- [ ] https://github.com/mui/material-ui/issues/13898
Repository: pytorch
Issue: [Feature request] Add new API Tensor.device_as 
Labels: triage review,oncall: jit,feature,module: python frontend

### 🚀 The feature, motivation and pitch

This new Api can be like Tensor.type_as.
```python
a1 = torch.zeros(5, device='cuda')
a2 = torch.zeros(5, device='cpu')
a3 = a1.device_as(a2)
assert a3.device == a1.device
```
Mainly used in the jit.trace model.
Because Tensor.to only record constant parameter. 
This can cause exceptions when moving the model to other devices.

I am currently using this method to transfer tensor from A device to B device in the trace model.
```python
@torch.jit.script
def device_as(self, other):
    return self.to(device=other.device)
```

### Alternatives

_No response_

### Additional context

_No response_

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @albanD
Repository: godot
Issue: Godot Steam version is broken
Labels: bug,needs testing,crash

### Godot version

4.1.1.stable

### System information

Godot v4.1.1.stable - Windows 11 22H2 - Vulkan (Forward+) - MSI GT 1030 - AMD Ryzen 3 1300x @ 3.50GHz (4 Threads)

### Issue description

At a random time godot freezes and crashes. When it crashes, steam thinks it's still running and when you try to close it, it won't close and just stucks. I've had it 10 times.

### Steps to reproduce

I opened godot
At random crashed

### Minimal reproduction project

N/A
Repository: next.js
Issue: `generateStaticParams` not Passing Parent Params to Child in Nested Dynamic Routes
Labels: bug,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64
    Binaries:
      Node: 18.12.1
      npm: 9.7.1
      Yarn: 1.22.19
      pnpm: 8.6.6
    Relevant Packages:
      next: 13.4.14-canary.0
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/nikolailehbrink/generateStaticParams-Bug

### To Reproduce

- Clone the [GitHub repository](https://github.com/nikolailehbrink/generateStaticParams-Bug) that contains the bug.
- Install the necessary dependencies with npm install or yarn install.
- Start the development server with npm run dev or yarn dev.
- Navigate to a nested route such as http://localhost:3000/12314/iasd in your browser.
- Observe that the child page is accessible and the slug parameter is not available in the child's generateStaticParams.

### Describe the Bug

I encountered a bug when using the generateStaticParams function with nested dynamic routes in Next.js. The parent's parameters are not being passed to the child's generateStaticParams, causing unexpected behavior in the generated static pages. According to the [your documentation](https://nextjs.org/docs/app/api-reference/functions/generate-static-params#generate-params-from-the-top-down), the expected behavior is to "Generate the parent segments first and use the result to generate the child segments." However, in the provided example, the behavior is not consistent with this documentation, and the slug parameter from the parent route does not get passed to the child.

### Expected Behavior

Expected Behavior:
The slug parameter generated in the parent's generateStaticParams should be available in the child's generateStaticParams.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

<sub>[NEXT-1509](https://linear.app/vercel/issue/NEXT-1509/generatestaticparams-not-passing-parent-params-to-child-in-nested)</sub>
Repository: angular
Issue: Add an option to `FormControl.enable()` to skip enabling children.  
Labels: area: forms

### Which @angular/* package(s) are the source of the bug?

forms

### Description

I stumbled across the following behavior of enabling a formControl with the flag onlySelf and I assume it's a bug:

Steps to reproduce:
1) Open the stackblitz example
2) Click on the button `Set disabled` to disable the formControls `section`, `shortAnswer` and `longAnswer`
3) Click on the button `Set enabled` that uses the flag `onlySelf`  to only update the current formControl `section` without the children.
4) The command `.enable({ onlySelf: true });` also sets now the formControls `shortAnswer` and `longAnswer` to enabled.   I would expect that the formControls `shortAnswer` and `longAnswer` are still disabled.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-dvdhca?file=src%2Fmain.ts,package.json

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 16.0.1
```


### Anything else?

_No response_
Repository: next.js
Issue: Dynamic Routes in App Router are considered Server Functions
Labels: bug,Pages Router

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
    Binaries:
      Node: 20.5.0
      npm: 9.8.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.12
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Data fetching (gS(S)P, getInitialProps)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/nextjs-dynamic-route-bug-report-scwrgr

### To Reproduce

Step 1: Start with an empty app directory Next project. 
Step 2: Add `/app/test/[slug]/page.tsx`:

```tsx
const Test = ({ params: { slug } }: { params: { slug: string } }) => {
  return <div>Slug: {slug}</div>;
};

export default Test;
```
Step 3: Run `next build`

Observe that the Route is considered a Server route:
```
Route (app)                                Size     First Load JS
┌ ○ /                                      145 B          78.4 kB
└ λ /test/[slug]                           145 B          78.4 kB

λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)
```


### Describe the Bug

The route `/test/[slug]` is considered a Server route despite the fact that it uses no dynamic functions. It does not seem to be cached via the Full Route Cache and causes a function execution on every load.


### Expected Behavior

I expected the route `/test/[slug]` to be a Static route and be cached (ISR / Full Route Cache)


You can work around this issue by setting the following flags, which causes NextJS to consider the route Static:
```ts
export const dynamic = "error";
export const dynamicParams = true;
```

I expected the default behavior to be Static and not Server.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Vercel
Repository: stable-diffusion-webui
Issue: stable diffusion webui extension shows two identical plugins, can you help with the problem? 
Labels: asking-for-help-with-local-system-issues

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

stable diffusion webui extension shows two identical plugins, can you help with the problem? 
<img width="507" alt="Screenshot - 2023-08-08 18 30 32" src="https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/15052053/fb7cbd55-71e0-48ca-9091-6e31371e20c7">


### Proposed workflow

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


### Additional information

_No response_
Repository: next.js
Issue: I18n configuration in next.config.js breaks app directory
Labels: bug,Navigation,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64
    Binaries:
      Node: 20.5.0
      npm: 9.8.0
      Yarn: 3.5.0
      pnpm: 8.6.12
    Relevant Packages:
      next: 13.4.14-canary.0
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Internationalization (i18n), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/fabio-nettis/next-i18n-error

### To Reproduce

This issue is directly related to my previous issue #53665 You can find more about the discovery process of this bug in [this discussion](https://github.com/vercel/next.js/discussions/53667). 

1. Clone the repository 
2. Try to navigate to any of the defined pages
3. You will encounter a not found error for each of the defined routes. 

Once you have seen the error you can then do the following steps to revert the broken app folder:

1. Remove `i18n` key from next config
2. Try to navigate to any of the defined pages
3. See the defined page

### Describe the Bug

Since version 13.4.13-canary.0 an application previously working fine on version 13.4.12 returns a 404 status code for every page in the app folder when the `i18n` setting is set in the next config file.

### Expected Behavior

Setting the `i18n` in the next config file should not break the whole application' routing.

### Which browser are you using? (if relevant)

Chrome 114.0.5735.106 (Official Build) (x86_64)

### How are you deploying your application? (if relevant)

next dev

<sub>[NEXT-1512](https://linear.app/vercel/issue/NEXT-1512/i18n-configuration-in-nextconfigjs-breaks-app-directory)</sub>