sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/pkgsite: pages require horizontal scrolling at width of 320 css pixels
Labels: help wanted,pkgsite

<!--
Please answer these questions before submitting your issue. Thanks!

If you would like to have your package removed, please file an issue at https://golang.org/s/pkgsite-package-removal.
-->
 
### What is the URL of the page with the issue?
 
Throughout. Screenshot uses stdlib `math` documentation as an example - https://pkg.go.dev/math
 
### What is your user agent?

`Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36`
 
<!-- 
You can find your user agent here:
https://www.whatismybrowser.com/detect/what-is-my-user-agent
-->
 
### Screenshot

(taken w/ width 1280, zoom 4x, i.e. 320 css pixels)
 
<!--
Please paste a screenshot of the page.
-->
 
<img width="1271" alt="image" src="https://github.com/golang/go/assets/16788495/f1b54602-278e-47ef-a353-efaabcdef6f9">

### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
 
Navigate to any page and achieve a viewport width of 320 pixels by any means (slide the window, zoom, etc.)
 
### What did you expect to see?
 
Page content is visible without horizontal scroll at 320 CSS pixels per [WCAG SC 1.4.10 guidelines on reflow](https://www.w3.org/WAI/WCAG21/Understanding/reflow.html).
 
### What did you see instead?

Page content blows out of the viewport and requires horizontal scrolling to view.
Repository: next.js
Issue: Trailing slash appended to home page links when i18 and skipTrailingSlashRedirect - true
Labels: bug,Internationalization (i18n)

### Link to the code that reproduces this issue

https://github.com/marcorcau/next-i18n-routing

### To Reproduce

Test URL: https://next-i18n-routing-lac.vercel.app

1. Start the application in development (pnpm run dev) in default language `http://localhost:3000`.
2. Hover on the "Locale switcher" links, notice urls **end in a slash** as in `http://localhost:3000/fr/`
3. Hover on the other links, notice they **don't end in a slash**, as in `http://localhost:3000/gsp/first`
4. Click on any of the "To XXXXX page" link except "To Index page").
5. Hover on any of the "Locale switcher" links, notice urls **do not end in a slash**.
6. Visit french home page at `http://localhost:3000/fr`. Notice link to english do not contain trailing slash, but german does. 

### Current vs. Expected behavior

In steps 2 and 6, I would expect the "Locale switcher" links to not end in a slash, as any other link in the page or its sub-pages.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11)
  Available memory (MB): 15691
  Available CPU cores: 16
Binaries:
  Node: 18.20.2
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 8.15.7
Relevant Packages:
  next: 14.2.2 // Latest available version is detected (14.2.2).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Internationalization (i18n)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

The code in the repo is exactly the same as the `next-i18n` example, just adding this line to `nextConfig`:

```
  skipTrailingSlashRedirect: true,
```

Any link to the home page in a language other than default gets a slash appended. This behaviour does not happen when linking to other pages.

In addition to this, when adding a `rewrites` section to `nextConfig` or adding an empty `middleware` and visiting the translated home page at `http://localhost:3000/fr`, a slash is also appended to the URL. It's not a redirect, its just appended after the page load.

The "empty-middleware" and "rewrites" branches in the same repo reflect this issue, which is also triggered by adding `  skipTrailingSlashRedirect: true,` to nextConfig
Repository: vscode
Issue: Issue Reporter: overall styling tune-up
Labels: feature-request,issue-reporter

Testing #210874

The issue reporter works well but feels a bit webview-y given what look like halfway-styled input and text elements. Things I think we should/could do:

- Use the text inputs, checkboxes and dropdowns that we use in the settings UI
- Use our default markdown styling
- Finally, a quick CSS polish (I can help with this)

![CleanShot 2024-04-23 at 10 13 23@2x](https://github.com/microsoft/vscode/assets/25163139/4213f4e9-6aa8-4e97-b747-0bd1ba1580ed)
Repository: vscode
Issue: Add the ability to reopen chat stream after successful response
Labels: feature-request,api,chat

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
I have been working with @isidorn on a chat extension and I'm finding that I need to re-open the chat stream so I can update the user on the results of their message.

For instance: the user asks Copilot for help on a topic. I'm augmenting the prompt and sending. When I receive the reply, I'm extracting code that I then execute, but only after the user clicks a button that I output to the chat window, which explicitly says "Run This". I want to report back the results of execution, but currently the only way I can do that is via popups, which is out of the flow of the chat.

Ideally, I could re-open the chat stream so I can send the results and also add a `stream.progress` when the execution goes off (or show an error if there was one). The follow up provider doesn't quite fit the scenario as the process is a bit more interactive.
Repository: stable-diffusion-webui
Issue: [Bug]: Can't create venv at the first launch
Labels: asking-for-help-with-local-system-issues

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [X] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [X] The issue has been reported before but has not been fixed yet

### What happened?

WebUi can't create venv at the first launch. The system cannot find the specified path.

### Steps to reproduce the problem

1. Install webui
2. Open webui-user.bat

### What should have happened?

Starting stable-diffusion

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

_No response_

### Sysinfo

Windows 10

### Console logs

```Shell
Creating venv in directory C:\Stable Diffusion\stable-diffusion-web ui\event using python "C:\Users\°ыхъерэфЕ\AppData\Local\Programs\Python\Python312\python.exe "
Unable to create event in directory "C:\Stable Diffusion\stable-diffusion-webui\venv"

exit code: 3

stderr:
The system cannot find the specified path.

Launch unsuccessful. Exiting.
To continue, press any key . . .
```


### Additional information

_No response_
Repository: react-native
Issue: android onScrollEndDrag throttled by scrollEventThrottle
Labels: Issue: Author Provided Repro,Platform: Android,Needs: Triage :mag:,Newer Patch Available

### Description

on android, onScrollEndDrag can be prevented by a non-zero scrollEventThrottle value.



### Steps to reproduce

- using below code, scroll/fling with any kind of velocity and notice the `onScrollEndDrag` message is not logged.
- repeat without flinging/no velocity (hold same scroll position for >250ms before releasing), notice the `onScrollEndDrag` message is logged.
```tsx
<FlatList
  data={[1,2,3,4]}
  onScrollEndDrag={() => console.log('onScrollEndDrag')}
  renderItem={() => <View style={{height: 400}} />}
  scrollEventThrottle={250}
/>
```

### React Native Version

0.73.6

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
info Fetching system and libraries information...
System:
  OS: macOS 14.4.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 264.94 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.20.1
    path: ~/.nvm/versions/node/v18.20.1/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.yarn/bin/yarn
  npm:
    version: 7.24.2
    path: ~/code/react-native-sydney-components/node_modules/.bin/npm
  Watchman:
    version: 2024.04.15.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/AG63864/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.4
      - iOS 17.4
      - macOS 14.4
      - tvOS 17.4
      - visionOS 1.1
      - watchOS 10.4
  Android SDK:
    API Levels:
      - "33"
      - "34"
    Build Tools:
      - 33.0.1
      - 34.0.0
    System Images:
      - android-34 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2023.2 AI-232.10300.40.2321.11567975
  Xcode:
    version: 15.3/15E204a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.11
    path: /Users/AG63864/.jenv/shims/javac
  Ruby:
    version: 3.1.1
    path: /Users/AG63864/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.6
    wanted: 0.73.6
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: false
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

info React Native v0.74.0 is now available (your project is running on v0.73.6).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.74.0
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.74.0
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos".
```


### Stacktrace or Logs

```text
n/a
```


### Reproducer

https://github.com/scrungrth/android-scroll-throttle-reproducer

### Screenshots and Videos

_No response_
Repository: pytorch
Issue: TestAOTAutograd.test_mem_leak_from_save_for_bw fails locally but not on CI when run with dynamo
Labels: module: ci,triaged,oncall: pt2,module: dynamo

I was trying to repro the recent flaky tests that CI was reported, when CI runs AOTAutograd tets on the dynamo shard.

However I noticed that this test would reliably fail in isolation for me locally:
```
PYTORCH_TEST_WITH_DYNAMO=1 python test/functorch/test_aotdispatch.py TestAOTAutograd.test_mem_leak_from_save_for_bw
```

@zou3519 pointed out that due to the fact that dynamo.reset doesn't reset **all** global state, it is technically possible that this test might not be failing in CI when run with the rest of the test suite.

cc @seemethere @malfet @pytorch/pytorch-dev-infra @ezyang @msaroufim @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng
Repository: vscode
Issue: `HoverContext` should have non-optional readonly members
Labels: api,polish,editor-hover

Testing #210904

Because it is VS Code passing a `HoverContext` instance we should mark its properties `readonly` and unless I am mistaken there is no reason the declare them as optional. AFAIK when having a context (which is optional) all properties are defined
Repository: pytorch
Issue: Improve Dynamo (and other) flaky tests
Labels: module: tests,triaged,oncall: pt2,module: dynamo,dynamo-triage-june2024

Tests in the Dynamo shard are marked as flaky. Most of the time the flakiness is deterministic in that one can reliably repro the tests by running them in a specific order.

We propose two test infra changes to reduce flakiness:
- We should run tests in the same order in CI (I don't think this is true today due to TD cc @mruberry @ZainRizvi @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @rec @msaroufim @bdhirsh @anijain2305 @clee2000).
- It is useful to fuzz the order of test suite runs to catch bugs. We should add some test runs (maybe in periodic?) that are fuzzing the order of tests. This needs some way to run the tests in reliable order as they do in CI (may need pytest plugin -- @aorenste may have some prior art).
Repository: vscode
Issue: `HoverContext` should pass back the specific type of hover I provided
Labels: engineering,editor-hover,on-hold

Testing #210904

I suggest that we change the provider to:

```
interface  HoverProvider<T extends Hover = Hover> {... }
```

And then make `HoverContext` use the specific type of hover our provider returned (`T`). This lets us avoid an extra cast
Repository: vscode
Issue: Use different templates for issue reporting vs performance vs features
Labels: feature-request,issue-reporter

Testing #210874
Repository: vscode
Issue: Show progress while resolving next level hover
Labels: under-discussion,editor-hover

Testing #210904

When a hover provider takes a few seconds to resolve the next level hover, there is not currently any feedback that next hover is being resolved. I suggest we show a spinner and also prevent the user from clicking the `+/-` buttons in these cases
Repository: vscode
Issue: Github Querry limit exceeded when tying the issue title
Labels: bug,issue-reporter

Testing #210874

![image](https://github.com/microsoft/vscode/assets/3840081/020a6a04-c5a4-4f8f-b1e6-6506d265a163)
Repository: vscode
Issue: I misunderstood yieldTo
Labels: bug,api

Testing #210985

### Steps

I returned an array of two pasteEdits [A, B]
I let A yield to text.plain, but I did not set yieldTo for B.
I thought the completion order would be [B, text.plain, A] because "A yielded but B didn't", but instead it was [text.plain, A, B], which implies that the order of the elements in the returned array matters.

### Suggestions

Could the behaviour above be clarified in the docstring for provideDocumentPasteEdits (such as by saying a list is returned instead of a set) or in the yieldTo field?
Repository: vscode
Issue: Expanding a verbose hover can end up with a non expandable hover
Labels: under-discussion,editor-hover

Testing #210904

1. Create a verbose hover provider that returns a hover that can be expanded
2. In the expansion, return a new hover that is not expandable

**Bug**
The user expands the hover and then can't unexpand it. This feels strange

Could VS code instead preserve the previous hover?
Repository: next.js
Issue: Update to `HotReload` triggers ‘bad `setState()`’ warning when server/client disagree on the initial value of `useSyncExternalStore()` and application throws
Labels: bug

### Link to the code that reproduces this issue

https://github.com/steveluscher/hot-reload-bug-repro

### To Reproduce

1. Create a hook `useFoo` that uses `useSyncExternalStore()` where the initial value of the server and the client rendering mismatch (ie. `getSnapshot` and `getServerSnapshot` disagree).
    ```ts
    import { useSyncExternalStore } from "react";

    function getSnapshot() {
      return 1;
    }

    function getServerSnapshot() {
      return 0;
    }

    function subscribe() {
      return () => {};
    }

    export default function useExternalStoreWhereTheServerAndTheClientDisagreeOnFirstRender() {
      return useSyncExternalStore(subscribe, getSnapshot, getServerSnapshot);
    }
    ```
2. In a component `ComponentThatThrows`, call `useFoo` and throw when the return value is the value returned on the client (ie. the value returned by `getSnapshot()`).
    ```ts
    import { ReactNode } from "react";
    import useExternalStoreWhereTheServerAndTheClientDisagreeOnFirstRender from "./useExternalStoreWhereTheServerAndTheClientDisagreeOnFirstRender";

    export default function ComponentThatThrows(): ReactNode {
      const num = useExternalStoreWhereTheServerAndTheClientDisagreeOnFirstRender();
      if (num === 1) {
        throw new Error("1 is the loneliest number");
      }
      return <span>Nothing is everything</span>;
    }
    ```
3. Wrap the whole thing in an ErrorBoundary and supply a fallback rendering.
    ```ts
    <ErrorBoundary fallback={<>Something bad happened</>}>
      <ComponentThatThrows />
    </ErrorBoundary>
    ```

### Current vs. Expected behavior

I would expect the server rendering to appear, followed by the error boundary's fallback once the app has a chance to re-render on the client.

I do see that, but in addition to that the following warning appears on the console:

> Warning: Cannot update a component (HotReload) while rendering a different component (ComponentThatThrows). To locate the bad setState() call inside ComponentThatThrows, follow the stack trace as described in https://reactjs.org/link/setstate-in-render



### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: Ubuntu 20.04.0 LTS Tue Apr 23 2024 11:17:57 GMT-0700 (Pacific Daylight Time)
Binaries:
  Node: 18.18.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.15.3
Relevant Packages:
  next: 13.5.1
  eslint-config-next: 13.5.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: kubernetes
Issue: Wishlist of CEL libraries
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

This is just my wishlist. We need all of them, so no specific priority.

- [ ] Regexes for object names, label keys, values, container names, etc. I think this one is already in the works?
- [ ] validate the type metav1.Conditions
- [ ] simple functions to check if conditions are true/false.
- [ ] taints and tolerations
- [ ] labelSelectors (we don't need this one, but it will probably be useful for some projects)
- [ ] The ultimate validation: Pod templates, but worth starting with just containers :) Very useful for job CRDs.
- [ ] ... (waiting for feedback)

### Why is this needed?

As we were working on transitioning Kueue validation webhooks to CEL, we ended up with a lot of repeated validation lines. In some cases, validating something is so involved that we decided to keep most of the webhooks, otherwise readability would be significantly impacted.
Repository: pytorch
Issue: Release artifacts for rc releases
Labels: oncall: releng,triaged

### 🚀 The feature, motivation and pitch

Hello, it would be nice if you could release the source artifacts like you do on real releases, but for release candidates too. For example, on releases, we have access to a `pytorch-<>version>.tar.gz` that includes all the git submodules and everything necessary to build pytorch. These are not available for release candidates.

We (Anaconda) start building rc releases early to prepare for the official releases and would like to be able to simply download the source instead of having to clone the tag + all submodules, etc. Cloning is significantly slower than just downloading a `.tar.gz` file.

Do you think that would be possible to do or be a good idea?

### Alternatives

_No response_

### Additional context

_No response_
Repository: next.js
Issue: The Error balloon/toast overlay is broken in 14.2
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/error-test-zx47mf

### To Reproduce

1. Create a blank next app with `npx create-next-app`
2. Create error.tsx in /app with `'use client'; export default function Error() { return 'test'; }`
3. Throw an error in page.tsx `throw new Error('test error');`
4. In 14.1, you get a balloon in the corner of the screen:
<img width="1672" alt="Screenshot 2024-04-19 at 6 34 00 PM" src="https://github.com/vercel/next.js/assets/3037705/d1a8e59d-0366-4af3-84bf-62bce71b5cdd">
5. In 14.2 this balloon/toast is broken. It never appears. 

### Current vs. Expected behavior

After the upgrade of next to 14.2 the toast/balloon never appears. I tried the canary as well `14.3.0-canary.19` and the issue persists.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Wed Feb 21 21:44:43 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6000
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: N/A
  pnpm: 7.30.3
Relevant Packages:
  next: 14.1.4
  eslint-config-next: 14.2.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Not sure

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

next dev (local)

### Additional context

_No response_
Repository: PowerToys
Issue: PowerToys is started as used after upgrading with winget and scope set to machine despite "Always run as administrator" option enabled
Labels: Issue-Bug,Area-Runner,Needs-Triage

### Microsoft PowerToys version

0.80.0

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

1) `winget install --id=Microsoft.PowerToys -v "0.80.0" -e --scope=machine -h`
2) Enable "Always run as administrator" and restart as admin.
3) `winget upgrade --scope=machine -h Microsoft.PowerToys`
4) PowerToys started as user instead of as admin.

### ✔️ Expected Behavior

PowerToys should be started as admin after upgrade when "Always run as administrator" option enabled.

### ❌ Actual Behavior

PowerToys is started as non-admin after upgrade when "Always run as administrator" option enabled.

### Other Software

_No response_
Repository: ollama
Issue: Why Ollama is so terribly slow when I set format="json"
Labels: bug,performance,api

### What is the issue?

This is a duplicate of #3154, which was closed, I'm assuming, by mistake. 
The performance of the `format="json"` param is 10x slower than regular inference when additional context is included

A prompt like this takes ~24s to return on an NVIDIA T4 with CUDA enabled and ` format="json"`. The same exact prompt without format json takes ~2s to return. This has got to be a bug right?
```
Use the following pieces of context to answer the question at the end. If you don't know the answer, just say that you don't know, don't try to make up an answer.

${context}

Please respond in the following JSON schema
{
   "${schema.fieldName}": {
      "type": ${schema.type},
      "description": ${schema.description}
     }
}

Question: ${schema.description}
Helpful Answer:
```


### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.1.32