sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Feature request: Text to speech Power Toy - similar to MacOS' "option + esc"
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Unless there is already a way in windows, I often find myself longing for a way to have native and easily accessible text-to-speech capabilities for reading on-screen highlighted text with a button shortcut. On a mac, this is achieved with 'option + escape' and it will immediately read highlighted text aloud with a pop-up menu for controlling the reading pace, and play/pause. Windows has 'Narrator', but the scope that it narrates is too wide (often reading aloud changes in volume levels, mouse clicks). The scope I am proposing is just reading aloud the highlighted text. The specification/requirements of the feature should match MacOS's text-to-speech in ease of activation and control, and be on par with "speech-ability"/ being able to understand what is being spoken. PowerToys seems to me like a great place to implement this feature on Windows. 

### Scenario when this would be used?

- If a user cannot read well, but is better at understanding spoken language. The task of understanding what is written on the screen would be made easier for these users.
- If a user would like to multitask: for example cook while Windows/PowerToys reads a paper aloud.

### Supporting information

Look at the feature already included in MacOS if you are unfamiliar: https://support.apple.com/guide/mac-help/have-your-mac-speak-text-thats-on-the-screen-mh27448/mac
Repository: vscode
Issue: Activation event for diagnostics
Labels: feature-request,languages-basic,languages-diagnostics

<!-- ⚠️⚠️ 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. -->

We have activation events for any extension-contributed views, but it would be helpful to have something similar for built-in views--particularly those that may not always be showing, for example the Problems view.

We're playing with a prototype that would contribute `CodeAction`s to `Diagnostic`s in the Problems view. Whereas commands can be added in context menus nearly everywhere else _without_ needing the extension to be activated, these `CodeAction`s must be provided by code, not defined in `package.json`. Right now, we can use `onStartupFinished` to activate, but I would prefer if we could defer activation until the Problems view becomes visible. I could imagine use cases for other built-in views like Output, Terminal, etc.
Repository: storybook
Issue: [Bug]: Error: No `docs.container` set, did you run `addon-docs/preset`?
Labels: bug,addon: docs

### Describe the bug

Getting this error in the console when try and look at generated docs:

```
renderDocs.js:36 Uncaught (in promise) Error: No `docs.container` set, did you run `addon-docs/preset`?
    at _callee$ (renderDocs.js:36:1)
    at tryCatch (runtime.js:63:1)
    at Generator.invoke [as _invoke] (runtime.js:293:1)
    at Generator.next (runtime.js:118:1)
    at asyncGeneratorStep (renderDocs.js:5:1)
    at _next (renderDocs.js:7:1)
    at renderDocs.js:7:1
    at new Promise (<anonymous>)
    at renderDocs.js:7:1
    at renderDocsAsync (renderDocs.js:17:1)
```

### To Reproduce

```
git clone https://github.com/acl-services/paprika.git .
yarn
yarn storybook
```

Storybook will open. Click any component's "Docs" tab and watch the console, e.g. look at the "Avatar" component under the "Display" section, expand "Avatar" and click "Docs".  Look at the console.


### System

```shell
System:
    OS: macOS 13.2.1
    CPU: (10) x64 Apple M1 Pro
  Binaries:
    Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v14.19.1/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.0/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Firefox: 106.0.5
    Safari: 16.3
  npmPackages:
    @storybook/addon-a11y: ^6.5.16 => 6.5.16
    @storybook/addon-actions: ^6.5.16 => 6.5.16
    @storybook/addon-cssresources: ^6.2.9 => 6.2.9
    @storybook/addon-docs: ^6.5.16 => 6.5.16
    @storybook/addon-knobs: ^6.4.0 => 6.4.0
    @storybook/addon-links: ^6.5.16 => 6.5.16
    @storybook/addons: ^6.5.16 => 6.5.16
    @storybook/react: ^6.5.16 => 6.5.16
```


### Additional context

You can find the "Avatar" story under `packages/Avatar/stories/Avatar.stories.mdx`. In this file I tried both of these with no luck:
```
// import { Meta, Description } from "@storybook/addon-docs/blocks";
import { Meta, Description } from "@storybook/addon-docs";
```

In `.storybook/main.js` I tried both of these with no luck:

```
module.exports = {
  addons: [
//  "@storybook/addon-docs/preset",
    "@storybook/addon-docs",
  ],
```

Thank you.
Repository: vscode
Issue: Allow opening startup CPU profiles in VS Code or explorer 
Labels: feature-request,perf

<!-- ⚠️⚠️ 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. -->

After using `code-insiders --prof-startup`, I get this dialog:
<img width="814" alt="image" src="https://user-images.githubusercontent.com/30305945/224375145-e090fdbe-e8a0-403e-872d-65fce3be2edf.png">

If I try to copy the filepaths out, this gets written to my clipboard: `## Header`

Since the path and filename are randomly generated I would much prefer actions to `Open Profile in VS Code` (which we can do through the JS debug extension) or `Reveal in File Explorer`.
Repository: rust
Issue: Diagnostic message for std trait implementation includes unstable std type
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics

### Background

Within std I'm attempting to add an unstable type to a trait (see [here for the impl](https://github.com/rust-lang/rust/pull/108981/files#diff-212737b68c4541123dae6916cdde516551e1fafcb343467bfe08a3d7ce72c517)). However, after compiling the new std, the unstable type is shown in error messages even without the feature enabled.

### Code

```rust
struct Biscuits;
fn main() {
    std::fs::metadata(&Biscuits).unwrap();
}
```

### Current Output

```plain
error[E0277]: the trait bound `Biscuits: AsRef<Path>` is not satisfied
    --> temp.rs:3:21
     |
3    |     std::fs::metadata(&Biscuits).unwrap();
     |     -----------------  ^^^^^^^^ the trait `AsRef<Path>` is not implemented for `Biscuits`
     |     |
     |     required by a bound introduced by this call
     |
     = help: the trait `AsPath` is implemented for `&NativePath`
     = note: required for `&Biscuits` to implement `AsRef<Path>`
     = note: required for `&Biscuits` to implement `AsPath`
note: required by a bound in `std::fs::metadata`
    --> R:\rust\library\std\src\fs.rs:1848:20
     |
1848 | pub fn metadata<P: AsPath>(path: P) -> io::Result<Metadata> {
     |                    ^^^^^^ required by this bound in `metadata`
```

### Desired Output

Remove the first `help: ` message.

```plain
error[E0277]: the trait bound `Biscuits: AsRef<Path>` is not satisfied
    --> temp.rs:3:21
     |
3    |     std::fs::metadata(&Biscuits).unwrap();
     |     -----------------  ^^^^^^^^ the trait `AsRef<Path>` is not implemented for `Biscuits`
     |     |
     |     required by a bound introduced by this call
     |
     = note: required for `&Biscuits` to implement `AsRef<Path>`
     = note: required for `&Biscuits` to implement `AsPath`
note: required by a bound in `std::fs::metadata`
    --> R:\rust\library\std\src\fs.rs:1848:20
     |
1848 | pub fn metadata<P: AsPath>(path: P) -> io::Result<Metadata> {
     |                    ^^^^^^ required by this bound in `metadata`
```
Repository: rust
Issue: Inconsistent behavior of auto_traits+negative_impls across crates.
Labels: A-trait-system,T-compiler,C-bug,F-negative_impls,F-auto_traits,A-auto-traits

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
// Crate a

#![feature(auto_traits)]
#![feature(negative_impls)]

pub auto trait NotVoid {}
impl !NotVoid for () {}

pub trait A<I, O> {}

impl<T, I: NotVoid> A<I, ()> for T {}
impl<T, O: NotVoid> A<(), O> for T {} // OK

use b::ExternNotVoid;

pub trait B<I, O> {}

impl<T, I: ExternNotVoid> B<I, ()> for T {}
impl<T, O: ExternNotVoid> B<(), O> for T {} // Error
```
```rust
// Crate b

#![feature(auto_traits)]
#![feature(negative_impls)]

pub auto trait ExternNotVoid {}
impl !ExternNotVoid for () {}
```

I expected to see this happen:
Identical behavior when `NotVoid` is declared in an external crate.

Instead, this happened:
```rust
error[E0119]: conflicting implementations of trait `B<(), ()>`
  --> a.rs:19:1
   |
18 | impl<T, I: ExternNotVoid> B<I, ()> for T {} // Error
   | ---------------------------------------- first implementation here
19 | impl<T, O: ExternNotVoid> B<(), O> for T {} // Error
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation

error: aborting due to previous error

For more information about this error, try `rustc --explain E0119`.
```
An error is produced when `NotVoid` is declared in an external crate (`ExternNotVoid`).

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.70.0-nightly (e3dfeeaa4 2023-03-07)
binary: rustc
commit-hash: e3dfeeaa45f117281b19773d67f3f253de65cee1
commit-date: 2023-03-07
host: x86_64-unknown-linux-gnu
release: 1.70.0-nightly
LLVM version: 15.0.7
```
Repository: stable-diffusion-webui
Issue: [Feature Request]: Turn off 'scripts.AlwaysVisible' for each extensions.
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 ?

extensions that are being made recently are 'script.AlwaysVisible' is being overspent.
Although it is an extension that is not used continuously, it is displayed on the screen, and the use of the UI is becoming increasingly uncomfortable.
( Maybe because of the problem of having only one choice in 'scripts' dropdown. extension developers have started using scripts.AlwaysVisible. )

It would be nice to have a feature that can turn off 'AlwaysVisible' of each extensions.

Please consider it..

### Proposed workflow

1. Go to 'extensions' > 'installed'
2. Turn off 'Always visible' of each extension.



### Additional information

_No response_
Repository: kubernetes
Issue: Kubelet stops rotating service account tokens when pod is terminating, breaking preStop hooks
Labels: kind/bug,sig/storage,sig/node,sig/auth,priority/important-longterm,triage/accepted

### What happened?

We have pods that use the kube API during their preStop hooks and we use 12h service account token expirations. Today we had a pod where the token was approaching expiration at the time the pod was deleted. 4h into the preStop hook, the token expired and the preStop hook started failing.

### What did you expect to happen?

Service account token rotation should continue working until pods have fully terminated.

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

Run a pod with a 10-minute service account token expiration and long terminationGracePeriodSeconds and a preStop hook that does `sleep infinity`. Exec into the pod after 10 minutes have elapsed and check the token, it will be expired.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.16", GitCommit:"60e5135f758b6e43d0523b3277e8d34b4ab3801f", GitTreeState:"clean", BuildDate:"2023-01-18T16:01:10Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.16", GitCommit:"60e5135f758b6e43d0523b3277e8d34b4ab3801f", GitTreeState:"archive", BuildDate:"2023-03-01T14:28:40Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>
AWS, but N/A for this issue
</details>


### OS version

<details>
CentOS 8 stream, but N/A for this issue

</details>


### Install tools

N/A

### Container runtime (CRI) and version (if applicable)

Occurs with both cri-o and cri-dockerd

### Related plugins (CNI, CSI, ...) and versions (if applicable)

N/A
Repository: go
Issue: x/build: missing host-openbsd-mips64-joelsing host
Labels: Builders,NeedsFix

Currently at https://farmer.golang.org/#pools:
```
host-openbsd-mips64-joelsing: 0/0 (1 missing)
```
CC @golang/release
Repository: godot
Issue: override.cfg not working on web export
Labels: bug,platform:web,topic:porting

### Godot version

3.5.2

### System information

Windows 10

### Issue description

When I create an override.cfg in the same directory as index.html, game does not use this config

### Steps to reproduce

add a single line to debug projectSettings (example: print(ProjectSettings.get_setting("application/config/name"))
Export project to HTML5
Place override.cfg in the same directory as index.html with the following content:

[application]
config/name="Web version"

run page, and console you can see the default setting instead of override


### Minimal reproduction project

N/A
Repository: next.js
Issue: [NEXT-1127] "Error: Cannot convert a Symbol value to a string" when using lazy in RSC
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: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.14.2
      npm: 8.5.0
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 13.2.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


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

App directory (appDir: true)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/lucid-elion-93ccmf?file=%2Fapp%2Fstuff.tsx

### To Reproduce

Assuming `stuff.js` is a Client component:

```js
import { lazy } from "react";
const Stuff = lazy(() => import("./stuff"));

export default function Home() {
  return <Stuff />;
}

```

### Describe the Bug

The error on `canary` is a bit better:

>Error: Attempted to call Symbol(Symbol.toPrimitive)() from the server but Symbol(Symbol.toPrimitive) is on the client. It's not possible to invoke a client function from the server, it can only be rendered as a Component or passed to props of a Client Component.

But this is still kinda confusing.

### Expected Behavior

Are we intentionally not supporting `lazy`? Then the error could be better (e.g. tell me to remove `lazy`). I get that maybe it doesn't make sense in the RSC environment directly.

Or if there's a way for that to work, maybe it could be made to work.

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

_No response_

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

_No response_

<sub>[NEXT-1127](https://linear.app/vercel/issue/NEXT-1127/error-cannot-convert-a-symbol-value-to-a-string-when-using-lazy-in-rsc)</sub>
Repository: next.js
Issue: `res.revalidate()` only working on Vercel deployment
Labels: bug

### 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 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.14.0
      npm: 9.3.1
      Yarn: 1.22.19
      pnpm: 7.1.7
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.1.6
      react: 18.2.0
      react-dom: 18.2.0
```

### Link to the code that reproduces this issue

https://www.digitalocean.com/community/questions/next-js-on-demand-revalidation-not-working-on-digitalocean-app-platform

### To Reproduce

- Create an endpoint do manually revalidate the generate static. Here's my code:
```typescript
import { NextApiRequest, NextApiResponse } from 'next';

export default async function handler(req: NextApiRequest, res: NextApiResponse) {
  // Checking for available method
  if (req.method !== 'POST') {
    return res.status(404).json({ error: `Invalid method ${req.method}` });
  }

  // Checking body
  if (!req.body.subdomain) {
    return res.status(401).send({ error: 'Missing subdomain on body' });
  }

  // Revalidating route
  try {
    await res.revalidate(`/${req.body.subdomain}`); // Next.js method to recreate static pages

    res.status(200).json({ ok: true, subdomain: req.body.subdomain, headers: req.headers });
  } catch (error) {
    res.status(500).json({ error, headers: req.headers });
  }
}

```
- Create a page [subdomain] that will be static generated;
- Deploy the application to a DigitalOcean App Platform;
- Call the endpoint using `Postman` or equivalent. Send the `subdomain` on the body;
- Check for the update on the generated static;

### Describe the Bug

When deployed the same version on Vercel, or using it locally, is working normally, but deploying it to the DigitalOcean makes the `revalidate` do nothing, and don't even throw an error.
Adding the `unstable_onlyGenerated` as true on the options, makes it throw an empty error on DigitalOcean, but not on Vercel.

I returned the headers to check if there's something I can do, but I don't think so.

### Expected Behavior

Checking the source code on `node_modules/next/dist/esm/server/api-utils/node.js`, the revalidate checks for the host header and handles it differently if trusted or not.

The expected behavior is to work on both deployments, and not only on Vercel.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

DigitalOcean
Repository: godot
Issue: web editor not importing preloaded project
Labels: bug,platform:web,topic:editor,confirmed

### Godot version

4.0.stable

### System information

windows 10

### Issue description

When you add a project into the preload section of the web editor [(link)](https://editor.godotengine.org/releases/4.0.stable/godot.editor.html)
![image](https://user-images.githubusercontent.com/114032547/224430662-bf814be6-877b-404c-bbf4-d1dea112891c.png)
it accepts the file but wont load it or realize it has been loaded
[(link to video)](https://drive.google.com/file/d/1eVbse4GxRxz23phFQoDciwHvVuXWrVdw/view?usp=sharing)

### Steps to reproduce

try import a project into the preload of the web editor

### Minimal reproduction project

[demo.zip](https://github.com/godotengine/godot/files/10946226/demo.zip)
Repository: flutter
Issue: Support PlatformViews where the size is determined by the platform and not Flutter
Labels: c: new feature,framework,engine,a: platform-views,team-ecosystem,P3,triaged-ecosystem

Currently, the width and height of a platform view is controlled by the Flutter widget tree. However, in some instances a plugin/app may want the width and height to be determined by the underlying native view. 

[FluidAds](https://developers.google.com/android/reference/com/google/android/gms/ads/AdSize#FLUID) for `google_mobile_ads` is one example of a use case. This plugin currently has a workaround that places the Dart platform view in a `Container` that changes it's width and height when it receives a method call from the underlying native view to set the size.
Repository: godot
Issue: Inspector: Visual shader resource menu collapses when toggling flags
Labels: bug,topic:editor,usability,topic:shaders

### Godot version

4.0.stable

### System information

Windows 11, Forward+, Nvidia 3060 (laptop)

### Issue description

Don't know how to describe it better than the title. See screen capture:

![Godot_4_latest_EcJtEkTylY](https://user-images.githubusercontent.com/26832680/224433518-3cdd5ad5-a2ff-457c-b918-efc987607274.gif)


### Steps to reproduce

1. Click on surface material override
2. shader > new shader > create a visual shader
3. Expand flags menu
4. Click on any flag

### Minimal reproduction project

[ShaderMenuCollapse.zip](https://github.com/godotengine/godot/files/10946403/ShaderMenuCollapse.zip)
Repository: pytorch
Issue: early stopping
Labels: feature,triaged,needs design

### 🚀 The feature, motivation and pitch

It would be nice and easy to have the early stopping function/feature in Pytorch so that neural network training can stop before overfitting based on some criteria for instance algorithm stops after 3 consequent epochs with very small changes in validation loss. At the moment this is possible in the training loop by adding a condition but if this is done by a separate specific function, it would be much easier for users to utilize it.

### Alternatives

_No response_

### Additional context

_No response_