sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Add broadcast commands throughout terminals
Labels: feature-request,terminal-input

<!-- ⚠️⚠️ 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. -->
Hi,
If you're familiar with terminator or iTerm, you know that it's possible to type the same prompt to multiple opened terminals.
It would be nice to have the same option in vscode.
Ref: https://terminator-gtk2.readthedocs.io/en/latest/grouping.html
Repository: go
Issue: proxy.golang.org: not found: fetch timed out
Labels: NeedsInvestigation,proxy.golang.org

```
$ go version
go version go1.21.5 linux/amd64
```

<details><summary>`go env`</summary>

```
go env
GO111MODULE='on'
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/azureuser/.cache/go-build'
GOENV='/home/azureuser/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/azureuser/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/azureuser/go'
GOPRIVATE=''
GOPROXY='direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21.5'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='0'
GOMOD='/home/azureuser/ARO-Installer/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3551886818=/tmp/go-build -gno-record-gcc-switches'
```

</details> 

I got the error when I run `go get`.
```
$ go get github.com/openshift/installer-aro@release-4.14-azure
go: downloading github.com/openshift/installer-aro v0.9.0-master.0.20240214010831-fd48bf30c1af
go: github.com/openshift/installer-aro@release-4.14-azure: github.com/openshift/installer-aro@v0.9.0-master.0.20240214010831-fd48bf30c1af: verifying module: github.com/openshift/installer-aro@v0.9.0-master.0.20240214010831-fd48bf30c1af: reading https://sum.golang.org/lookup/github.com/openshift/installer-aro@v0.9.0-master.0.20240214010831-fd48bf30c1af: 404 Not Found
        server response: not found: fetch timed out
```
Several hours have passed since we create that version but it isn't available yet.

#57185 #56174 might be related but not sure.
The question is, is this just a temporary issue or is there something we should do?
Repository: rust
Issue: We have quite different APIs for emitting a lint vs a hard error
Labels: C-cleanup,A-lints,A-diagnostics,T-compiler,A-translation

Switching between a lint and a hard error used to be fairly simple, one basically just swapped out the function that is called to emit the diagnostic. However, with translatable diagnostic, this has become more work:
- the error type needs to be changed from `derive(LintDiagnostic)` to `derive(Diagnostic)`
- a `span` field needs to be added and decorated with `#[primary_span]`
- and only then the diagnostic-emitting code can be adjusted to call `emit_err` instead of `emit_node_span_lint`

It can be hard to find out about this recipe. It is also a (small) roadblock whenever one wants to do  a crater run with a lint turned into a hard error, just to see how much it happens in the ecosystem.

So maybe something could be done to unify these two APIs? I don't know whether "span-in-error-type" vs "separate-span" is the better API. I was told that sometimes having the span in the type is very useful because then extra attributes can be easily applied to it. OTOH, for parts of the compiler (e.g. the interpreter), the logic that determines which error to emit and the logic that determines the span are quite far apart from each other, leading [kind of a mess](https://github.com/rust-lang/rust/issues/112618) with the current error APIs. Maybe there is a way to make both styles possible for both lints and hard errors?

Cc @davidtwco (not sure who else is pushing translatable diagnostics?)
Repository: PowerToys
Issue: Snagit Region Selection captures whole screen
Labels: Issue-Bug,Product-FancyZones,Needs-Triage,Area-App Compat

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

When using Snagit for screen capture of region or window, the selection snaps to FancyZone region and not region or window.

### ✔️ Expected Behavior

Screen capture of region or window.

### ❌ Actual Behavior

Screen capture of FancyZone region.

### Other Software

TechSmith Snagit 2024.0.1 (Build 555) - 13.10.2023
Repository: terminal
Issue: Occasional extra characters in terminal output 
Labels: Issue-Bug,Needs-Triage,Needs-Attention

### Windows Terminal version

1.18.10301.0

### Windows build number

10.0.19045

### Other Software

_No response_

### Steps to reproduce

No repro, these extra symbols occur in the output from time to time like: **]8;;**.
Please see the msbuild ticket with other details
https://github.com/dotnet/msbuild/issues/9715

### Expected Behavior

_No response_

### Actual Behavior

Rarely, extra characters will appear at the end of the line for some of the build artifacts.

```
....dll]8;;
....dll\
```
Repository: pytorch
Issue: ModularIndexing does not have well-defined semantics
Labels: triaged,module: inductor

### 🐛 Describe the bug

We currently sometimes use it to mean floordiv + floordiv-based %, e.g. in its documentation
https://github.com/pytorch/pytorch/blob/87c6cd2f0069bb8ef990098266b916f3e6984e3f/torch/utils/_sympy/functions.py#L98
or in wrapper code
https://github.com/pytorch/pytorch/blob/87c6cd2f0069bb8ef990098266b916f3e6984e3f/torch/_inductor/codegen/common.py#L374-L382

But then sometimes it means truncation div + truncation-based %, like in kernel codegen:
https://github.com/pytorch/pytorch/blob/87c6cd2f0069bb8ef990098266b916f3e6984e3f/torch/_inductor/codegen/cpp.py#L358
or triton (which uses the Python syntax to dispatch to C operations lol)

### Versions

master

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler
Repository: vscode
Issue: Provide Notebook Cell Progress Bar Control in Extension API
Labels: feature-request,notebook-api

<!-- ⚠️⚠️ 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. -->
Currently the cell progress bar in the notebook can only be shown in an infinite fashion, though the progress bar component itself actually supports showing progress. Could we expose progressbar API to extension developers, so they can have a VSCode-styled progress bar out-of-box to illustrate the progress of their cell execution? Thanks!
Repository: next.js
Issue: Custom error.tsx page is not rendered for dynamic routes using generateStaticParams / ISR in app router. Pages router 500.tsx is rendered instead
Labels: bug

### Link to the code that reproduces this issue

https://github.com/bkrajewski94/next-isr-error-page-bug

### To Reproduce

1. Install dependencies with `npm install`
2. Build the application with `npm run build`
3. Start the application `npm start`
4. Navigate to `localhost:3000/test` 

### Current vs. Expected behavior

If you use `generateStaticParams` inside a dynamic route like `[slug]/page.tsx`, none of the custom `error.tsx/global-error.tsx` pages will be displayed in case of an error. What you'll see instead is the NextJS inbuilt error page
<img width="276" alt="image" src="https://github.com/vercel/next.js/assets/43791606/19b081f3-432e-45c5-b587-53707cd44dfb">

In the below example I used generateStaticParams to implement ISR (on request static generation):

```
// src/app/[slug]/page.tsx

async function getData() {
  const res = await fetch("https://api.example.com/...");

  if (!res.ok) {
    // This will activate the closest `error.js` Error Boundary
    throw new Error("Failed to fetch data");
  }

  return res.json();
}

export default async function Page({ slug }: any) {
  const data = await getData();

  return (
    <main>
      <div>{slug}</div>
      <div>{JSON.stringify(data)}</div>
    </main>
  );
}

// error.tsx is not rendered when:
export function generateStaticParams() {
  return [];
}

// error.tsx is rendered correctly when instead of generateStaticParams I use:
// export const dynamic = "force-dynamic";
```

It only breaks if you build your application (works fine on devserver).
As you can imagine it can be a big problem when you'd like to e.g. render a custom error page, or log error to an external system inside the error boundary.


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: 7.1.0
Relevant Packages:
  next: 14.1.1-canary.52 // Latest available version is detected (14.1.1-canary.52).
  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 build (local), next start (local), Other (Deployed)

### Additional context

_No response_
Repository: flutter
Issue: Record a animation widget at 60fps and extract a video 
Labels: c: new feature,framework,engine,P3,team-framework,triaged-framework

### Use case

I would like to record a flutter widget

Existing Flutter Feature :
-> RepaintBoundary allows us to take a screenshot of a particular widget


New Feature Request:
-> A widget like Repaint boundary but can record a widget like Screen recorder and can be used to extract a video,

Exiting plugin Issues for the Feature Request:
-> There are some flutter plugins but they crash after certain time due to memory issues, Native apps has the capacity to render a video by taking screenshot 

Current Approach : 
I tried to fix this feature using Repaint Boundary from Flutter and then passing the bytedata to swift AV Foundation but has a lot of inconsistencies. 


Since, Flutter Engine has access to low level render tree, A new feature to tract the frames and bind it together ti extract a video can be implemented.



Use Cases:
-> Video Editor Apps completely based on flutter can offer video render features,
-> Games can be recorded in real time that are made in flutter



### Proposal

Some package offering the feature conpect but has drawbacks 

https://pub.dev/packages/screen_recorder
->  This can only extract a gif and has low quality and frame rate and can only be used for very few seconds,

https://pub.dev/packages/ed_screen_recorder
-> This is a solution for screen recorder but can't record the individual widget instead records the entire screen and asks for permission,

https://pub.dev/packages/render
-> Low frame rate and can only be used to record for few seconds
Repository: next.js
Issue: Suspense fallback not being displayed when updating query params and having multiple suspenses in a single page
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/jolly-grass-5t82t8

### To Reproduce

1. Start the application
2. Click the "Update Query Params" button
3. No loading will be shown
4. Remove the"FirstAsyncComponent" from the page
5. Click the "Update Query Params" button
 - Now the loading is displayed properly as soon as we click the button


### Current vs. Expected behavior

Current behaviour
 - With multiple Suspense components with different keys no fall back is shown when clicking the button and the query param only updates in the url after the loading, but in the code if we console.log the searchParams it is updated instantly

Expected behaviour
 - When pressing the button independently of the number of Suspenses, the one using the query param as a key should display the fallback

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000
Binaries:
  Node: 20.4.0
  npm: 9.7.2
  Yarn: 1.22.18
  pnpm: 8.6.2
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.0.4
  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), Vercel (Deployed), Other (Deployed)

### Additional context

_No response_
Repository: material-ui
Issue: [material-ui][Text Field] Weird exit border transition on the filled variant
Labels: design: material,component: text field,package: material-ui,enhancement

### Steps to reproduce

Link to live example: (required)

Steps:
1. visit this [material-ui/react-text-field](https://mui.com/material-ui/react-text-field/)
2. click on the `TextField` input with either `variant="standard"` or variant="filled".
3. Watch the border-bottom when it is transitioning out.

https://github.com/mui/material-ui/assets/28821368/f967b01a-6c41-40d5-851c-fb654451308f



### Current behavior

The transition out is quite weird. 

### Expected behavior

The transition should resemble the `TextField ` with `variant="outlined"`.

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: TextField
Repository: frp
Issue: Display FRP client Public IP in the FRP Dashboard
Labels: enhancement

### Describe the feature request

Currrently in the FRP Dashboard no IP address of the connected machines are shown it would be really helpful if this feature is added.

![image](https://github.com/fatedier/frp/assets/83474708/9be048d0-ca16-42d1-843d-5252cd3601e0)


### Describe alternatives you've considered

_No response_

### Affected area

- [ ] Docs
- [ ] Installation
- [ ] Performance and Scalability
- [ ] Security
- [X] User Experience
- [ ] Test and Release
- [ ] Developer Infrastructure
- [ ] Client Plugin
- [ ] Server Plugin
- [ ] Extensions
- [ ] Others
Repository: vscode
Issue: Adding support for the uniqueKeys vocabulary in settings.json validation
Labels: feature-request,settings-editor

Hello,

I would like vscode json validator to be compatible with the uniqueKeys vocabulary when validating an array of object [see UniqueKey Documentation](https://docs.json-everything.net/schema/vocabs/array-ext)

My use case if for an extension that I develop I need to add a configuration contribution consisting of an array of object, and would like that when users are filling their settings.json they get to know that a properties in my object must have unique value in the array.

I see that uniqueItems has been corrected in the last vscode release and I need a little bit more  flexibility.

Thank you
Repository: pytorch
Issue: dynamo remap collective improvement
Labels: oncall: distributed

We should update the warning message "Can't remap async version of inplace op to functional collective" to point out that users can rewrite their own code to use the functional collective.  (possibly point them to a doc with more helpful examples).  

Also, we might want to open a placeholder issue for adding dynamo support to trace work objects, and point users there to have a place to ask for help.

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @yf225
Repository: ant-design
Issue: Missing feature to modify styling of containers of the different Ant Tour Step containers
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

We want the possibility to customize the background color of the cover section on a step. We want that section to be white, while the rest of the content is blue (set by using type="primary" on the Tour component). However, the only way to modify styling on a step now is either to globally override the styling (which we do not want), or to use the style-property on the TourStepProps type. The problem with this is that the style-property doesn't target the html element for the cover object. It doesn't even target the html element that actually sets the background color (class="ant-tour-inner"), it targets the top level element (class="ant-tour"). This creates the effect you can see in this example: [https://codesandbox.io/p/sandbox/gracious-thunder-forked-h5hrrz](https://codesandbox.io/p/sandbox/gracious-thunder-forked-h5hrrz).

As you can see in the example, we have also tried to use @emotion/styled to set the styling on the actual Ant Tour React component, but with no luck. We cannot set the background on the react node that is applied to the cover property, as there are padding set on the container for the cover element.

### What does the proposed API look like?

If there are no non-hacky solution for this problem today, my suggestion would be to do something similar to how styling on Card is implemented: [https://ant.design/components/card](https://ant.design/components/card). Add a styles-property that opens up the possibility to target the different elements inside a TourStep.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: tensorflow
Issue: Cannot find Tensorflow API document (html)
Labels: comp:apis,type:docs-feature

### Issue type

Documentation Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

I try Tensorflow/Tensorflow and Tensorflow/docs, but I cannot find the document about API usage. It says Tensorflow's API document (HTML files) are generated based on source code docstring. If so, where can I find the script of it?

### Standalone code to reproduce the issue

```shell
N/A
```


### Relevant log output

_No response_
Repository: neovim
Issue: Cannot specify -1 for end_col in `nvim_buf_set_extmark()`
Labels: enhancement,api,complexity:low

### Problem

As the title says, In `nvim_buf_add_highlight()`, since -1 can be specified as `{col}` (or `{col_end}` in `nvim_buf_add_highlight()`), it is lack coherence to not be able to use -1 in `{opts}.end_col`.
It should be fixed by tweaking this area.

https://github.com/neovim/neovim/blob/a376d979bda103fa9998d05c3cc4ba56d3c3cece/src/nvim/api/extmark.c#L556

### Steps to reproduce

```
nvim --clean
:call setline(1, 'foo')
:call nvim_buf_set_extmark(0, nvim_create_namespace('foo'), 0, 0, #{ end_row: 0, end_col: -1, hl_group: 'Error' })
```

### Expected behavior

Add highlight to the first line.

### Neovim version (nvim -v)

NVIM v0.10.0-dev-a376d97

### Vim (not Nvim) behaves the same?

No

### Operating system/version

Ubuntu 20.04.5 LTS (WSL2)

### Terminal name/version

Windows terminal

### $TERM environment variable

tmux-256color

### Installation

build from repo
Repository: rust
Issue: Bad error message for infinite type recursion
Labels: A-diagnostics,A-trait-system,T-compiler,A-const-eval,D-confusing,D-terse,fixed-by-next-solver

### Code

```Rust
#![recursion_limit = "5"]
#![allow(unconditional_recursion)]

fn quicksort<It, I>(i: I) -> Vec<i32>
where
    It: Iterator<Item = i32>,
    I: IntoIterator<IntoIter = It>,
{
    quicksort(i.into_iter().filter(|_| true))
}

pub fn bar(xs: Vec<i32>) -> Vec<i32> {
    quicksort(xs)
}

```


### Current output
relevant error:
```Shell
error[E0275]: overflow evaluating the requirement `Filter<Filter<Filter<Filter<Filter<std::vec::IntoIter<i32>, ...>, ...>, ...>, ...>, ...>: Iterator`
  |
  = help: consider increasing the recursion limit by adding a `#![recursion_limit = "10"]` attribute to your crate (`qsort`)
  = note: required for `Filter<Filter<Filter<Filter<Filter<std::vec::IntoIter<i32>, {closure@src/lib.rs:8:36: 8:39}>, {closure@src/lib.rs:8:36: 8:39}>, {closure@src/lib.rs:8:36: 8:39}>, {closure@src/lib.rs:8:36: 8:39}>, {closure@src/lib.rs:8:36: 8:39}>` to implement `IntoIterator`
```


### Desired output

```Shell
something-something infinite recursion
```


### Rationale and extra context

Suggestion to increase recursion limit is wrong

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-unknown-linux-gnu
release: 1.76.0
LLVM version: 17.0.6
```


### Anything else?

_No response_
Repository: rust
Issue: Running "x.py build library --target XYZ" breaks previously built targets
Labels: T-bootstrap

After building an x86_64-unknown-linux-gnu toolchain, I wanted to add libstd for `i586-unknown-linux-gnu` by running `./x.py build library --target i586-unknown-linux-gnu`.

However, doing this apparently removes libstd for x86_64-unknown-linux-gnu.

What is the correct way to build multiple libstds without touching config.toml?
Repository: godot
Issue: GPUParticle2D not working on Android 14
Labels: bug,needs testing,topic:2d,topic:particles

### Tested versions

4.2.1

### System information

Android 14 - Pixel Fold - Compatibility

### Issue description

Creating an new project with a single GPUParticles2D emitter does not show anything on Android 14 on my Pixel Fold. It does work on an older Galaxy Tab 4 on Android 10.

### Steps to reproduce

* Create a new Project
* Place an GPUParticle2D node and give it a default process material
* Run on Android 14 device(?)

### Minimal reproduction project (MRP)

[particletest.zip](https://github.com/godotengine/godot/files/14283639/particletest.zip)