sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [video_player] specify buffer sizes
Labels: c: new feature,p: video_player,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

### Use case

the player has a buffer for what to play. When pausing a live stream, the buffer size also determines whether you will be resuming the stream at the position where you paused (if you are still within buffer size duration) or whether you jump forward in time (the pause exceeded buffer duration).

Is it possible to configure this buffer size?

### Proposal

for example, Exoplayer has different buffer sizes you can specify, here are the defaults:
https://developer.android.com/reference/androidx/media3/exoplayer/DefaultLoadControl

but I assume every player has some kind of buffer configuration. 

I'd like to know, how to pass these buffer sizes on to the player. If not a general option, maybe through a platform specific configuration object.
Repository: flutter
Issue: [camera_web] Using takePicture() always returns XFile with null MimeType
Labels: platform-web,p: camera,package,assigned for triage,P2,team-web,triaged-web

### Steps to reproduce

1. Use https://pub.dev/packages/camera_web according to official example
2. Invoke `final file = await _controller.takePicture()`

### Expected results

- `XFile` with `mimeType` set
- Alternatively, `XFile`  with such format that `lookupMimeType()` from https://pub.dev/packages/mime returns right mimeType
- Bonus: It would be nice to have file's name filled as well

### Actual results

`XFile` contains only path.
I conclude this is because of: https://github.com/flutter/packages/blob/dea6c7306cf6aac942046bbc1ee8b593f296b44c/packages/camera/camera_web/lib/src/camera.dart#L265

### Code sample

It's really just an official example plus:
```dart
final file = await _cameraController.takePicture();
print(file.mimeType);
```

### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.16.5, on macOS 14.2.1 23C71 darwin-arm64, locale en-PL)
    • Flutter version 3.16.5 on channel stable at /Users/michal/Dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 78666c8dc5 (4 weeks ago), 2023-12-19 16:14:14 -0800
    • Engine revision 3f3e560236
    • Dart version 3.2.3
    • DevTools version 2.28.4

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/michal/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 15.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C65
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 14.2.1 23C71 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 120.0.6099.216

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

```

</details>
Repository: rust
Issue: complicated build stages
Labels: T-bootstrap

Current approach on bootstrap stages adds too much complexity on the bootstrap codebase; the complexity continues to grow with the additional changes made on bootstrap and it's not even functioning correctly (like writing incorrect stages to stdout on certain commands).

One possible solution could be to handle stage behaviours as part of the `Step` trait individually on `Step` implementation.

Some references to why current implementation of step calculations is making things so difficult/complicated:

https://github.com/rust-lang/rust/blob/ef324565d071c6d7e2477a195648549e33d6a465/src/bootstrap/src/core/build_steps/compile.rs#L839-L847

https://github.com/rust-lang/rust/blob/ef324565d071c6d7e2477a195648549e33d6a465/src/bootstrap/src/core/build_steps/compile.rs#L905-L926

Particularly, the behaviors of the force_use_stage function are not really useful for all use cases (for instance, see https://github.com/rust-lang/rust/issues/118233 and https://github.com/rust-lang/rust/issues/118918)

https://github.com/rust-lang/rust/blob/ef324565d071c6d7e2477a195648549e33d6a465/src/bootstrap/src/lib.rs#L1403-L1417

@rustbot label +T-bootstrap
Repository: godot
Issue: The 2D scene doesn't update the particles when using a mesh as the texture of a GPUParticles2D node.
Labels: bug,topic:rendering,topic:2d,topic:particles

### Tested versions

- Reproducible in : 4.2 stable and in 4.1 stable.

### System information

Godot v4.2.stable - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; 31.0.15.3623) - Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (12 Threads)

### Issue description

When using a GPUParticles2D node, and assigning a MeshTexture to it's texture (no matter the texture used, I will use a QuadMesh), any change made to the mesh (for example its image size) will not be present in the scene.
However, modifying several property (any trail properties, some visibility properties...) update the scene.
This is the same for the editor's scene and in game when doing "hot reload".
Note: When launching the project it work fine.

### Steps to reproduce

- Create a GPUParticles2D node
- Assign a ParticleProcessMaterial to its process material to see particles.
- Assign a MeshTexture to its texture.
- Assign a QuadMesh to the Mesh of the MeshTexture.
- Change the image size of the QuadMesh to be 5x5
Now the particle node should pop out some particles, but none appear.
- Now for example change the trail_lifetime properties (without even activating the trail)
Now particles do pop out.

### Minimal reproduction project (MRP)

[TestBug.zip](https://github.com/godotengine/godot/files/13929738/TestBug.zip)
Repository: pytorch
Issue: Deprecate and remove usage of from __future__ import annotations in codebase
Labels: module: typing,triaged

### 🐛 Describe the bug

https://peps.python.org/pep-0563/ which introduced `from __future__ import annotations` has been superseded by https://peps.python.org/pep-0649/ , which was accepted last year. Among other things, the new PEP deprecates the old one, which means we should NOT use the early adoption future pragma in our codebase.

At time of writing, there are 150 occurrences of this pragma in the PyTorch codebase.

cc @malfet @xuzhao9 @gramster @Skylion007 

### Versions

main
Repository: TypeScript
Issue: Document and/or deprecate Node's getFullStart() vs. pos?
Labels: Help Wanted,Infrastructure

### Acknowledgement

- [X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

Coming over from https://github.com/typescript-eslint/typescript-eslint/issues/8227 -> https://discord.com/channels/508357248330760243/640177429775777792/1194002057858916483: it looks like `ts.Node` objects have both a `pos: number` property and a `getFullStart(): number` method that directly returns `this.pos`:

https://github.com/microsoft/TypeScript/blob/02f9ddf55d27716c0306ec6561baf80d42744fed/src/services/services.ts#L564-L566

Doing some quick _Find all references_ from the interfaces' definitions in VS Code:

* `Node`'s `getFullStart()` has 25 results
* `ReadonlyTextRange`s `readonly pos` has 407 results

I looked through the GitHub repo and code history but couldn't find anything justifying why both exist. My hunch is maybe that #9529 which added `getFullStart()` predates TS 2.0's `readonly` ([TS 2.0 release notes > readonly](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-0.html#read-only-properties-and-index-signatures))?

Given that `getFullStart()` incurs an extra function call, is there any reason beyond backwards compatibility to keep it around? If not, would the team be open to marking it as `@deprecated` in JSDoc to reduce ambiguity?
Repository: vscode
Issue: macOS: Keybindings: cmd+h cannot hide app while in "Hex Editor" tab. There aren't any relevant keyboard binding entry.
Labels: bug,keybindings,webview

<!-- ⚠️⚠️ 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?: No

<!-- 🪓 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. -->
```
Version: 1.85.1
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:48:16.874Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 22.6.0
```

Steps to Reproduce:

1. Install VSCode
2. install official extension "hex editor"
3. open a file in hex editor, keep in this tab
4. press cmd+h
5. vscode app does not hide. keyboard binding debug info below.

```
2024-01-14 10:48:08.773 [info] [KeybindingService]: / Received  keydown event - modifiers: [meta], code: MetaRight, keyCode: 93, key: Meta
2024-01-14 10:48:08.774 [info] [KeybindingService]: | Converted keydown event - modifiers: [meta], code: MetaRight, keyCode: 57 ('Meta')
2024-01-14 10:48:08.774 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-01-14 10:48:09.027 [info] [KeybindingService]: / Received  keydown event - modifiers: [meta], code: KeyH, keyCode: 72, key: h
2024-01-14 10:48:09.028 [info] [KeybindingService]: | Converted keydown event - modifiers: [meta], code: KeyH, keyCode: 38 ('H')
2024-01-14 10:48:09.028 [info] [KeybindingService]: | Resolving meta+[KeyH]
2024-01-14 10:48:09.028 [info] [KeybindingService]: \ No keybinding entries.
2024-01-14 10:48:09.421 [info] [KeybindingService]: + Storing single modifier for possible chord meta.
2024-01-14 10:48:09.727 [info] [KeybindingService]: + Clearing single modifier due to 300ms elapsed.
```
Repository: storybook
Issue: React: RSCs don't render correctly in Docs
Labels: bug,documentation,react,has workaround,addon: docs,nextjs,sev:S2,rsc

### Describe the bug

When I enable RSCs in Next.js they render fine as individual stories. However, on the docs page they show up blank:

<img width="1252" alt="image" src="https://github.com/storybookjs/storybook/assets/488689/d97c0806-af4d-43b6-a60b-fc27e04e6e51">

In the console is the typical error message:
 
> Warning: async/await is not yet supported in Client Components, only Server Components. This error is often caused by accidentally adding `'use client'` to a module that was originally written for the server.

Also, navigating away from the page locks up the browser.


### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: rust
Issue: Tracking Issue for Bevy special-casing of implied bounds and `-Zno-implied-bounds-compat`
Labels: P-high,C-tracking-issue,T-types

In #118553 we're adding special casing for functions containing a type using `ParamSet` from Bevy to not emit an error or warning for incorrect implied bounds (see #109628). This special casing can be disabled via the unstable `-Zno-implied-bounds-compat` flag.

The expectation is that we may be adding additional implied bounds that (with some modifications to Bevy) allows Bevy's dependents to continue compiling without errors or warnings. When those changes are made, we want to remove this special casing. Alternatively, if we find out we *can't* add additional implied bounds in a way that allows dependents to continue compiling, we still want to remove the special casing.
Repository: godot
Issue: MultiMesh3D throws errors and can corrupt scenes, Condition "instance_count > 0" is true.
Labels: bug,topic:editor,topic:3d

### Tested versions

4.2.1 bot standard and mono

### System information

Windows 11 - Vulkan - Nvidia RTX 4070 - intel i5 13600KF

### Issue description

For some reason MultiMesh3D now throws an error like this:

![image](https://github.com/godotengine/godot/assets/33526847/650e5dc4-5ed4-4b87-8a80-96f1e5a3b582)
(screenshot is from mono version but same error happens in the standard godot version)

and it can also lead to scene corruption - I don't know the conditions for that, sometimes my scenes just get corrupted when I add the multimesh, I have no idea why, it's not any particular mesh itself I tried built-in ones too.

### Steps to reproduce

With MRP:
Open the project if you don't see the error on the first try (no .godot folder yet so it doesn't show) then close the project and open it again, you should see it now or after opening the scene with the MultiMesh3D (called planet.tscn) - you might need to have both scenes open when you close the project so they reopen.
(sometimes under no idea what circumstances you can get a corrupted scene error and the scene will no longer open though I have no idea why or how to reproduce this)

Without MRP:
1. Make a scene with MultiMesh3D and populate a surface with some MeshInstance3D (for testing I used the Cylinder mesh) and save it as a scene.
2. Instantiate that scene into your main scene.
3. Run your project.
4. Close the project and open it again
5. You should see the error now or after opening the scene with the MultiMesh3D.

### Minimal reproduction project (MRP)

[MultiMeshMRP.zip](https://github.com/godotengine/godot/files/13930789/MultiMeshMRP.zip)
Repository: go
Issue: x/tools/gopls: rename doesn't propagate to the implementors
Labels: NeedsInvestigation,gopls,Tools,Refactoring

### Go version

devel go1.22-1d45a7ef56 darwin/arm64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/denpeshkov/Library/Caches/go-build'
GOENV='/Users/denpeshkov/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/denpeshkov/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/denpeshkov/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/denpeshkov/src/go.googlesource.com/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/denpeshkov/src/go.googlesource.com/go/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='devel go1.22-1d45a7ef56 Wed Jan 10 03:29:50 2024 +0000'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/Users/denpeshkov/src/github.com/denpeshkov/greenlight/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 -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/nw/fts0xshx033fq3q8rn4rhjhc0000gn/T/go-build755587796=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

==> ./foo/foo.go <==
```go
package foo

type I interface {
	F()
}
```

==> ./bar/bar.go <==
```go
package bar

type S struct{}

func (s S) F() {}
```

==> ./qux/qux.go <==
```go
package qux

import (
	"github.com/denpeshkov/doodles/bar"
	"github.com/denpeshkov/doodles/foo"
)

var _ foo.I = bar.S{}
```

The renaming of the function `foo/I.F()` to `foo/I.FF()` doesn't propagate to `bar/S.F()`

Checked with both `gopls@v0.15.0-pre.1` in VSCode and `gorename`

### What did you see happen?

`bar/S.F()` renamed to `bar/S.FF()`

### What did you expect to see?

`bar/s.F()` is not renamed
Repository: tauri
Issue: Support local async executors for I/O bound applications?
Labels: type: feature request

### Describe the problem

Does tauri have the ability to use a local async executor instead of a multithreaded one? I noticed that the [manage method](https://docs.rs/tauri/latest/tauri/struct.Builder.html#method.manage) requires the state to be `Send + Sync + 'static`, which is not what I expected for tauri commands, as I thought they would probably be more I/O bound (a concurrency problem) rather than CPU bound (a multithreading problem). This makes it unfortunately annoying to write a backend since it requires me to use `Arc<Mutex<T>>` for a mutable global state, when it only needs to do so concurrently (eg. `Rc<Cell<T>>`).

### Describe the solution you'd like

An option to use a local async executor, perhaps by default, would be a huge QoL improvement, as it lets us avoid implementing `Send + Sync + 'static` unnecessarily.

### Alternatives considered

For now, I will likely use `Arc<Mutex<T>>` and wait on the mutex to emulate a concurrent behavior of invocations of tauri commands. However, this has both a high developer cost (requiring me to rewrite my existing code to use multithreading primitives), and a performance cost (acquiring mutexes).

### Additional context

_No response_
Repository: next.js
Issue: When npm run dev, -4094 syscall: 'open' occurs intermittently.
Labels: bug

### Link to the code that reproduces this issue

```
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 20.11.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 14.0.5-canary.56
      react: ^18
      react-dom:  ^18
      typescript: ^5
```
https://github.com/eeennsu/nextjs-post2

### To Reproduce

1. npm run dev
2. Develope my project
3. error occur

### Current vs. Expected behavior

```
[Error: UNKNOWN: unknown error, open 'D:\myCoding\GitHub\nextjs-post2\.next\static\chunks\app\layout.js'] {
  errno: -4094,
  code: 'UNKNOWN',
  syscall: 'open',
  path: 'D:\\myCoding\\GitHub\\nextjs-post2\\.next\\static\\chunks\\app\\layout.js'
}
```

While developing with npm run dev, the -4094 UNKOWN error occasionally occurs. I don't know the timing and conditions under which it occurs, and after Googling, it seems that the same error has already occurred before and it still hasn't been fixed.

** What I did to fix this bug **

1. remove .next
2. npm cache clean --force
3. npm cache verify
4. remove node_modules
5. restart vscode
6. computer format and reinstall all programs


I tried all the solutions but couldn't solve it. I hope this bug is resolved as soon as possible.

This error does not occur only in a specific project, but occurs simultaneously in all of my projects. So I think it is next.js's own error.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
{
  "dependencies": {
    "@grafbase/sdk": "^0.14.0",
    "@headlessui/react": "^1.7.18",
    "@radix-ui/react-slot": "^1.0.2",
    "@types/jsonwebtoken": "^9.0.5",
    "class-variance-authority": "^0.7.0",
    "cloudinary": "^1.41.2",
    "clsx": "^2.1.0",
    "framer-motion": "^10.18.0",
    "graphql-request": "^6.1.0",
    "lucide-react": "^0.309.0",
    "mongoose": "^8.0.4",
    "next": "^14.0.4",
    "next-auth": "^4.24.5",
    "react": "^18",
    "react-dom": "^18",
    "react-hot-toast": "^2.4.1",
    "tailwind-merge": "^2.2.0",
    "tailwindcss-animate": "^1.0.7",
    "zustand": "^4.4.7"
  },
  "devDependencies": {
    "@grafbase/sdk": "~0.14.0",
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "autoprefixer": "^10.0.1",
    "postcss": "^8",
    "tailwindcss": "^3.3.0",
    "typescript": "^5"
  },
  "name": "nextjs-post2-project",
  "private": true,
  "scripts": {
    "build": "next build",
    "dev": "next dev",
    "lint": "next lint",
    "start": "next start"
  },
  "version": "0.1.0"
}
```


### 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: FancyZones not working for FRE:AC (Free Audio Converter)
Labels: Issue-Bug,Product-FancyZones,Needs-Triage,Area-App Compat

### Microsoft PowerToys version

0.77.0

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Windows from other programs works well, it just does not work with FRE:AC (Free Audio Converter).


### ✔️ Expected Behavior

Working

### ❌ Actual Behavior

Not working

### Other Software

FRE:AC (Free Audio Converter): https://www.freac.org/
Repository: vscode
Issue: Inside of multiline math expressions in markdown files is not recognized as math/latex context.
Labels: bug,help wanted,markdown,grammar

<!-- ⚠️⚠️ 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.85.1
- OS Version: Windows 11

In markdown file, multiline math expressions like the following are valid and supported by the official markdown preview feature.
But the inside of the dollar signs is not recognized as math/latex context unless the beginning dollar sign is at the start of the line.
I checked the context by "Inspect Editor Tokens and Scopes".
```
aaa $\begin{pmatrix}
1 & 2 \\
3 & 4 \\
\end{pmatrix}$ bbb
```
I have a lot of latex snippets for writing math expressions in markdown, but they are not suggested in such expressions for this issue.

btw, I have a setting "markdown.preview.breaks": true.
When this is true, I think the only way to write an inline multiline math expression is like this.