sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: TypeError: invalid boundary key and TypeError: cursor out of bounds
Labels: ext/kv,triage required 👀

```
for await (const match of db.list({
  start:[ "__oindex__", "", "Laloux", "" ] ,
  end:[ "__oindex__", -Infinity, "Laloux", -Infinity ]})) { ... }
```
throws error: Uncaught (in promise) TypeError: invalid boundary key
However, it throws this AFTER it iterates through all values.

Also note, I use -Infinity for the upper bound instead of -NaN because when -NaN renders using the console.log function it drops the - sign and I am unsure if -NaN really sorts properly.

I will also occasionally get a cursor out of bounds error, although the inner code does nothing with the cursor; in fact, it has no access to it.

I have added this hack to my code to get around these issues:

```
 let matchCount = 0;
        try {
            for await (const match of db.list({start,end})) {
               ...
           }
        } catch(err) {
            if(err.message!=="cursor out of bounds" && !(matchCount>0 && err.message==="invalid boundary key")) {
                throw err;
            }
        };
```
Repository: go
Issue: cmd/run: error hint for "no required module provides package" is not helpful
Labels: help wanted,NeedsFix,GoCommand

In a directory that contains a `go.mod`, use go run to run a package that is not in the dependency graph with no version specified. Currently we tell you to `go get tool`. This probably isn't what you want (it will temporarily add the tool to your module, but it will be removed on the next `go mod tidy`). We should consider removing this hint.

```
$ go run golang.org/x/tools/cmd/stringer
no required module provides package golang.org/x/tools/cmd/stringer; to add it:
	go get golang.org/x/tools/cmd/stringer
```

I created this issue to track the work mentioned on this comment from @rsc on https://github.com/golang/go/issues/48429#issuecomment-1601062050
> @ConradIrwin, I think that error message change is not correct. If people are using "go run" then we shouldn't tell them to do something that is meant to be used with "go tool" but accidentally also makes "go run" work. Honestly I think the "to add it" note should probably be removed entirely. There are two possible ways to fix that error. The other is to add @version to the command line. Often that's what you want instead. We should stop presuming one solution.
Repository: stable-diffusion-webui
Issue: A new button to copy a metadata image prompt in gallery directly in textbox (txt2img, img2img)
Labels: enhancement

In models gallery for lora, embbedings, hypernetwork we already have a button to show the model metadata. 

### Proposed workflow

Another interesting feature is when an image with a prompt metadata has been added for the model is to add another button to send the image prompt metadata directly to the textbox. 

And eventually to complete this idea also add an arrow left/right if the model has more than one image to show others images.
Repository: flutter
Issue: SemanticsProperties.hintOverries documentation is outdated
Labels: framework,a: accessibility,d: api docs,P2,team-framework,triaged-framework

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

https://api.flutter.dev/flutter/semantics/SemanticsProperties/hintOverrides.html

The doc mentions the `hint overrides` will affect how `hint` is used in Android, but it doesn't. They are two different things that work independently.

### Proposal

We should update the doc
Repository: excalidraw
Issue: Arrowheads are too big and cant be changed of size
Labels: arrow-redesign

I'm trying to put an arrow but it doesn't fit well
![image](https://github.com/excalidraw/excalidraw/assets/39559632/e8e51375-4ec6-4762-af2a-68d312a8322d)
Repository: storybook
Issue: [Bug]: `storybook dev` crash by `file-system-cache`
Labels: bug,core

### Describe the bug

This is a rare error in the storybook cli and cannot be reproduced. It can be cured by deleting `node_modules/.cache/storybook/dev-server`.The error log is below.

```
> storybook dev -p 6006

@storybook/cli v7.0.22

info => Serving static files from ././public at /
info => Starting manager..
╭───────────────────────────────────────────────────╮
│                                                   │
│   Storybook 7.0.22 for react-vite started         │
│   191 ms for manager and 2.49 s for preview       │
│                                                   │
│    Local:            http://localhost:6006/       │
│    On your network:  http://192.168.11.7:6006/    │
│                                                   │
╰───────────────────────────────────────────────────╯
/home/re-taro/projects/github.com/suzuka-kosen-festa/2023-hp/node_modules/.pnpm/file-system-cache@2.3.0/node_modules/file-system-cache/lib/common/Util.js:74
            throw new Error(`Failed to read cache value at: ${path}. ${error.message}`);
                  ^

Error: Failed to read cache value at: /home/re-taro/projects/github.com/suzuka-kosen-festa/2023-hp/node_modules/.cache/storybook/dev-server/a5a8bf6e622aef57065c6498611f40c911543d7d-f086b87885981c04ce7a583ff90a49313de83de7. /home/re-taro/projects/github.com/suzuka-kosen-festa/2023-hp/node_modules/.cache/storybook/dev-server/a5a8bf6e622aef57065c6498611f40c911543d7d-f086b87885981c04ce7a583ff90a49313de83de7: Unexpected end of JSON input
    at Object.<anonymous> (/home/re-taro/projects/github.com/suzuka-kosen-festa/2023-hp/node_modules/.pnpm/file-system-cache@2.3.0/node_modules/file-system-cache/lib/common/Util.js:74:19)
    at Generator.throw (<anonymous>)
    at rejected (/home/re-taro/projects/github.com/suzuka-kosen-festa/2023-hp/node_modules/.pnpm/file-system-cache@2.3.0/node_modules/file-system-cache/lib/common/Util.js:6:65)

Node.js v20.3.0
 ELIFECYCLE  Command failed with exit code 1.
```

### To Reproduce

_No response_

### System

```shell
System:
    OS: Linux 6.3 Arch Linux
    CPU: (12) x64 AMD Ryzen 5 5600U with Radeon Graphics
  Binaries:
    Node: 20.3.0 - ~/.asdf/installs/nodejs/20.3.0/bin/node
    npm: 9.6.7 - ~/.asdf/plugins/nodejs/shims/npm
  npmPackages:
    @storybook/addon-a11y: 7.0.22 => 7.0.22 
    @storybook/addon-essentials: 7.0.22 => 7.0.22 
    @storybook/addon-interactions: 7.0.22 => 7.0.22 
    @storybook/addon-links: 7.0.22 => 7.0.22 
    @storybook/blocks: 7.0.22 => 7.0.22 
    @storybook/react: 7.0.22 => 7.0.22 
    @storybook/react-vite: 7.0.22 => 7.0.22 
    @storybook/testing-library: 0.2.0 => 0.2.0
```


### Additional context

_No response_
Repository: pytorch
Issue: Tracking issue for optimizer graph not being an inference graph
Labels: triaged,tracker,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

### 🐛 Describe the bug

The optimizer is incorrectly classified as a training graph in aot. The main reason this occurs is that some parameters have `requires_grad=True` *and* torchdynamo calls set_grad_enabled(True|False) while simultaneously putting a call_function node in the graph which performs the global state change. 

As a result, when dynamo traces a no_grad context manager, it will trace the *exit* of the context manager *before* calling the user compiler. As a result, by the time we reach aot, grad is enabled, and the graph is treated as a training graph.

Why this matters:
Functionalization appends an epilogue which aggregates all mutation updates of tensors into a single code block consisting of a bunch of copies. In inference mode, these copies are visible to inductor while in training mode, these copies are not visible to inductor. If the copies are not visible to inductor, inductor will allocate tensors for every single parameter in the graph in order for them to get sent to the epilogue, which is atrocious for perf. 

Solutions:
1. graph break before grad is re-enabled
2. in functionalization make the epilogue visible in training mode
3. with compiled backwards, the entire graph is an inference graph by default

1 is two lines of code, so that approach is the easiest. 
3 is getting implemented currently, so once it's ready we can remove the graph breaks.


### Error logs

N/A

### Minified repro

_No response_

### Versions

N/a

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519
Repository: flutter
Issue: [video_player] live stream Update duration to allow seek back
Labels: c: new feature,platform-android,p: video_player,package,c: proposal,P3,team-android,triaged-android

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I would like to request an enhancement for the video_player package to include a seek back feature for live streaming. Currently, the package supports playing live streams but lacks the capability to seek back within the live window. This limits the ability to review or replay previously streamed content, https://github.com/flutter/packages/pull/3983 is a pr where i did include the duration updates



### Proposal

its a feature request in video_player package

The ExoPlayer library (https://exoplayer.dev/live-streaming.html) provides a similar functionality where a live window is created, enabling users to seek back within the stream's duration. It would be beneficial to implement a comparable mechanism within the video_player package.

for ios i dont know if its viable or not
Repository: vscode
Issue: feature request: structured logging console
Labels: feature-request,debug

<!-- ⚠️⚠️ 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. -->

Specifically, I'm thinking of the Debug Console, but probably applies to Output as well, and maybe others.

Currently, the Debug Console supports a basic filtering syntax with include/exclude, presumably on a per-line basis. ([It curiously is lacking Find.](https://github.com/microsoft/vscode/issues/4338)) A structured logging console would instead interpret program output as having some kind of structure, and be able to query that more richly.

We probably cannot proscribe a format, and we probably cannot support every format, but supporting a few common ones would be nice. At the very least, we could support lines prefixed with timestamp so I could stop having 20% of the width of the console consumed by noise :)
Repository: pytorch
Issue: DISABLED test_graph_concurrent_replay (__main__.TestCuda)
Labels: module: rocm,module: tests,triaged,skipped

Platforms: rocm

Disabling this unit test since it showed up in CI testing for ROCm5.5 CI upgrade PR: https://github.com/pytorch/pytorch/pull/103092: https://github.com/pytorch/pytorch/actions/runs/5338693121/jobs/9682282685?pr=103092

cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @mruberry @BLOrange-AMD
Repository: vscode
Issue: Add `extensionVersion` to activation error
Labels: feature-request,telemetry

External ask from the C# Dev kit team.

Current `monacoworkbench/extensionactivationerror` only has extensionId and not the version of the extension.
Repository: next.js
Issue: App Router showing 404 page when using inbuilt routing but the page is working when visited directly
Labels: Parallel & Intercepting Routes

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home Single Language
    Binaries:
      Node: 18.15.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.8-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/thisiskartik/nextjs-routing-bug-reproduction

### To Reproduce

I've three routes `/`, `/signup`, `/verify` and `/onboarding`. I want `/signup` and `/verify` to be shown as modal in `/` route. I created the following routing directory:
```
app
    (auth)
        onboarding
            page.tsx
        signup
            page.tsx
        verify
            page.tsx
        layout.tsx
    (landing)
        @getStarted
            (.)signup
                page.tsx
            (.)verify
                page.tsx
            default.ts
            layout.tsx
        layout.tsx
        page.tsx
    layout.tsx
```

Now if I try to visit the route from `/` -> `/signup` -> `/verify` -> `/onboarding` it works fine. I see the modal for both `signup` and `verify` and got redirected to `onboarding` page.

But if I try to visit the route from `/signup` -> `/verify` it shows 404 for `/verfiy` and then if I refresh the page then the `verify` page works and from `/verify` I can visit `/onboarding`

![ezgif-2-e785483dc4](https://github.com/vercel/next.js/assets/25222549/0740da83-8da6-4820-9e1f-3acabb4dad8b)

### Describe the Bug

While using parallel and Intercepting routes in App Router it's showing 404 page with inbuilt routing using `Link` tag to `redirect` function, but the same page is working when visited directly from the browser url bar.

### Expected Behavior

When I go from `/signup` to `/verify` it shouldn't show the `verify` page instead of 404 page.

### Which browser are you using? (if relevant)

Chrome 114.0.5735.134

### How are you deploying your application? (if relevant)

_No response_
Repository: go
Issue: x/tools/cmd/go-contrib-init: deprecate and remove it
Labels: NeedsFix,Tools

This tool wasn't updated for a while (so, it still assumes GOPATH-based workspace setup).
The 4-step setup described in https://go.dev/doc/contribute is not too hard to follow and needs to be done only once. 
Let's deprecate this tool, and focus on keeping the official contribution guide concise and accurate.

- [ ] update https://go.dev/doc/contribute
- [ ] delete the tool
Repository: godot
Issue: [TRACKER] XWayland-related issues
Labels: platform:linuxbsd,topic:porting,tracker

### Godot version

Various, mostly 4.x

### System information

Linux/BSD - Wayland

### Issue description

Lately lots of Linux distributions (such as [Fedora 34](https://fedoramagazine.org/announcing-fedora-34/), [Debian 10 "buster"](https://www.debian.org/News/2019/20190706) and [Ubuntu 21.04](https://canonical.com/blog/ubuntu-21-04-is-here)) have been switching to Wayland compositors as their default windowing solution and many people don't even know that they're actually running one.

Luckily, people can still use Godot through a compatibility mechanism that most compositors have, called [XWayland](https://wayland.freedesktop.org/xserver.html), which allows them to run X11 unmodified applications seamlessly.

It works fine most of the time but sadly it looks like that Godot, for whatever reason, doesn't work that well with it, manifesting issues that can't be replicated on common X11 window managers.

The above and the fact that most people aren't seemingly aware of XWayland are causing confusion in multiple bug reports lately.

The purpose of this tracker is to have all the currently known XWayland issues in one place to aid future bug reports.

#### 4.x issues

```[tasklist]
- [ ] #57288
- [ ] #74168
- [ ] #75140
- [ ] #75752
- [ ] #77333
- [ ] #78487
- [ ] #75515
- [ ] #74723
- [ ] #78818
- [ ] #79102
- [ ] #79677
- [ ] #79820
- [ ] #80008
- [ ] #81732
- [ ] #82205
- [ ] https://github.com/godotengine/godot/issues/85342
- [ ] https://github.com/godotengine/godot/issues/93892
- [ ] https://github.com/godotengine/godot/issues/96137
- [ ] https://github.com/godotengine/godot/issues/99343
- [ ] https://github.com/godotengine/godot/issues/100611
```
(for #77333, unsure, some people report it also with native X11)

#### 3.x issues

```[tasklist]
- [ ] #44741
```

#### Workaround

Most of those are windowing related (4.x) and can be worked around by running Godot with **single window mode**. To enable it, either go in the editor settings or run Godot with the `--single-window` CLI argument.

### Steps to reproduce

Run Godot on a Wayland compositor through XWayland.

### Minimal reproduction project

N/A

**_Production team edit:_** _to make the lists use the `[tasklist]` format_
Repository: node
Issue: `cpplint` does not accept literals that require namespace
Labels: c++

Literals such as `std::string_view::string_view_literals` or `std::literals::string_view_literals` is required to be used through a namespace. The following code is the only way of achieving that:

```cpp
using namespace std::string_view::string_view_literals
```

Currently, cpplint does not accept this example, and forces us to add a ignore statement, and `using-declarations` are not available for string_view_literals.

```
src/node_options.cc:20:  Do not use namespace using-directives.  Use using-declarations instead.  [build/namespaces_literals] [5]
```

One way of achieving this through: 

`using std::string_view_literals::operator""sv;`.

cc @nodejs/cpp-reviewers
Repository: storybook
Issue: [Bug]: storybookStoreV6 does not work with Suspense
Labels: bug,help wanted,react

### Describe the bug

When using a "suspense decorator" with a v6 storybook store, I recieve this error in the story:

```
TypeError: can't convert symbol to string
    Dv index.js:497
    io index.js:659
    y5 index.js:670
    nu index.js:709
    g6 config.mjs:19
    React 3
    g6 config.mjs:19
    jv config.mjs:20
    hookified runtime.js:7
    decorateStory runtime.js:34
    bindWithContext runtime.js:34
    wrapper chunk-DXNAW7Q2.mjs:7
    decorator runtime.js:104
    makeDecorator runtime.js:104
    hookified runtime.js:7
    decorateStory runtime.js:34
    bindWithContext runtime.js:34
    AB preview.mjs:19
    hookified runtime.js:7
    decorateStory runtime.js:34
    bindWithContext runtime.js:34
    EB preview.mjs:9
    hookified runtime.js:7
    decorateStory runtime.js:34
    bindWithContext runtime.js:34
    KB preview.mjs:6
    hookified runtime.js:7
    decorateStory runtime.js:34
    bindWithContext runtime.js:34
    i8 preview.mjs:401
    hookified runtime.js:7
    decorateStory runtime.js:34
    defaultDecorateStory runtime.js:34
    applyHooks runtime.js:7
    unboundStoryFn runtime.js:34
    React 7
    g scheduler.production.min.js:13
    Y scheduler.production.min.js:14
    EventHandlerNonNull* scheduler.production.min.js:14
    <anonymous> scheduler.production.min.js:19
react-dom.production.min.js:189:29
```

Which I have finally narrowed down to using a storybook store of v6.

### To Reproduce

https://stackblitz.com/edit/github-xgijrv-d6etea?file=.storybook%2Fmain.ts

### System

```shell
normally on macOS, but my repro works in stackblitz:


❯ npx storybook info

Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
  npmPackages:
    @storybook/addon-essentials: ^7.1.0-alpha.38 => 7.1.0-alpha.38 
    @storybook/addon-interactions: ^7.1.0-alpha.38 => 7.1.0-alpha.38 
    @storybook/addon-links: ^7.1.0-alpha.38 => 7.1.0-alpha.38 
    @storybook/blocks: ^7.1.0-alpha.38 => 7.1.0-alpha.38 
    @storybook/react: ^7.1.0-alpha.38 => 7.1.0-alpha.38 
    @storybook/react-vite: ^7.1.0-alpha.38 => 7.1.0-alpha.38 
    @storybook/testing-library: ^0.2.0 => 0.2.0 

```



### Additional context

The only reason we still use storybook store v6 is I think because Chromatic didn't support v7 at one point? I wonder if they've updated their support...

Looks like yes: 
![image](https://github.com/storybookjs/storybook/assets/10626596/9c6322c7-ac66-4425-a78d-0c4bff02c355)


*except* now I'm running into Vite's problems with async CSS imports, so I'm fiddling with `optimizeDeps` to make sure my base styles don't override specific component styles.. (https://github.com/vitejs/vite/issues/3924)
Repository: godot
Issue: Setting mouse mode to captured while the window is minimized results in an error
Labels: bug,platform:linuxbsd,topic:porting

### Godot version

v4.0.stable.official [92bee43ad]

### System information

Linux/BSD, xorg server

### Issue description

If you minimize the game while its loading, have it set on ready to set mouse mode to captured, it will result in an error being logged.

### Steps to reproduce

Set in project settings window mode to minimized
Add a script that on ready, sets mouse mode to captured
![image](https://github.com/godotengine/godot/assets/69520693/1d3e6c58-faf6-4336-b6ba-1e43286755f5)


### Minimal reproduction project

[bugs.zip](https://github.com/godotengine/godot/files/11840496/bugs.zip)
Repository: rust
Issue: Type inference/coercion with optional function pointer
Labels: A-type-system,T-compiler,C-bug,A-coercions,T-types

It seems that type inference and/or coercion doesn't work properly when an `Option` function pointer is assigned to a temporary variable. See example:

```rust
fn takes_callback(_f: Option<extern "C" fn()>) {}

fn main() {
    extern "C" fn callback() {}

    // This is fine
    takes_callback(if true { Some(callback) } else { None });

    // This is also fine
    let maybe_callback: Option<extern "C" fn()> = if true { Some(callback) } else { None };
    takes_callback(maybe_callback);

    // This doesn't compile
    let maybe_callback = if true { Some(callback) } else { None };
    takes_callback(maybe_callback);
}
```

```
error[E0308]: mismatched types
  --> src/main.rs:15:20
   |
15 |     takes_callback(maybe_callback);
   |     -------------- ^^^^^^^^^^^^^^ expected `Option<extern "C" fn()>`, found `Option<extern "C" fn() {callback}>`
   |     |
   |     arguments to this function are incorrect
   |
   = note: expected enum `Option<extern "C" fn()>`
              found enum `Option<extern "C" fn() {callback}>`
   = note: when the arguments and return types match, functions can be coerced to function pointers
note: function defined here
  --> src/main.rs:1:4
   |
1  | fn takes_callback(f: Option<extern "C" fn()>) {}
   |    ^^^^^^^^^^^^^^ --------------------------

For more information about this error, try `rustc --explain E0308`.
```

This seems incorrect to me (`maybe_callback` should be inferred to be `Option<extern "C" fn()>` as required by `takes_callback`), but even if it is correct, it's not really clear from the error what has gone wrong or how to fix it because the 'expected' and 'found' types appear to be effectively the same.

### 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 (90c541806 2023-05-31)
binary: rustc
commit-hash: 90c541806f23a127002de5b4038be731ba1458ca
commit-date: 2023-05-31
host: x86_64-unknown-linux-gnu
release: 1.70.0
LLVM version: 16.0.2
```
Repository: flutter
Issue: [Impeller] Metal screenshotter in tests must wait until the GPU is done rendering to the texture before screenshotting.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

There is a `CommandBuffer::WaitUntilScheduled` now but I believe we will need a `CommandBuffer::WaitUntilCompleted` or something similar.

[The issue is here](https://github.com/flutter/engine/blob/7ff6a65b7183b6a45dd53da6f68fc6840d2fa4bf/impeller/golden_tests/metal_screenshoter.mm#L27) where the ToImage call is made but we don't wait for the GPU to complete operations before attempting to screenshot the texture.