sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: new vendor feature: Stack traces point to original `https:` urls
Labels: needs discussion

With the new vendor feature added in #20065 and #15633 dependencies are resolved locally which is fantastic. I noticed that when an error is thrown the stack trace still points to the original `https:` urls instead of the local files. This means that I'm transfered to the website in the browser when I click on the url instead of it opening the local file.

<img width="762" alt="Screenshot 2023-08-07 at 11 25 49" src="https://github.com/denoland/deno/assets/1062408/c6c4df6d-3934-4c16-93be-0a67ec75fa40">


## Steps to reproduce

1. Clone https://github.com/marvinhagemeister/deno-vendor-stack
2. Run `deno run -A main.ts`
Repository: storybook
Issue: [Bug]: UseGlobal not available on vue
Labels: bug,vue3,needs triage

### Describe the bug

I'm trying to get global value reactively, so when global config (e.g theme) is changed
i can change my theme without reloading

I Found this artilcle and was trying to use useGlobal
since in decorator, the context args is not reactive

https://storybook.js.org/docs/vue/essentials/toolbars-and-globals

![image](https://github.com/storybookjs/storybook/assets/7564844/71749b44-c44c-4b2c-8191-623a94bb5ab7)


### To Reproduce

```ts
// .storybook/withVeutifyTheme.decorator.js
import { watch, toRef, isReactive } from "vue";
import { DecoratorFunction } from "@storybook/types";
import { VueRenderer } from "@storybook/vue3";
import { useTheme, useLocale } from "vuetify";
import { VThemeProvider } from "vuetify/components";

export const DEFAULT_THEME = "light";
export const DEFAULT_LOCALE = "ja";

export const withVuetifyTheme: DecoratorFunction<
  VueRenderer,
  { [x: string]: any }
> = (story, context) => {
  const globalTheme = context.globals.theme || DEFAULT_THEME;
  const locale = context.globals.locale || DEFAULT_LOCALE;

  return {
    components: { VThemeProvider, story },
    setup() {
      const theme = useTheme();
      const { current: currentLocale } = useLocale();
      const { globals } = context.getStoryContext(story);
      console.log();
      theme.global.name.value = globalTheme;
      currentLocale.value = locale;
      return {
        theme,
      };
    },
    template: `<v-theme-provider>
      <story />
    </v-theme-provider>`,
  };
};

```

i created a decorator with this 

### System

```shell
https://storybook.js.org/docs/vue/essentials/toolbars-and-globals
```


### Additional context

_No response_
Repository: stable-diffusion-webui
Issue: The analytics function cannot be used
Labels: asking-for-help-with-local-system-issues

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

How to enable the analytics function of Gradio? Can record my data and my team's.

### Steps to reproduce the problem

I don't know

### What should have happened?

I don't know

### Version or Commit where the problem happens

1.2.3

### What Python version are you running on ?

None

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

Windows

### What device are you running WebUI on?

Other GPUs

### Cross attention optimization

Automatic

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

_No response_

### Command Line Arguments

```Shell
no
```


### List of extensions

no

### Console logs

```Shell
no
```


### Additional information

_No response_
Repository: godot
Issue: Godot freeze after rename a child node of a duplicated scene
Labels: bug,topic:editor,needs testing

### Godot version

4.1.1 stable

### System information

Pop OS 22 LTS Nvidia

### Issue description

I had an area2d node with a sprite and a collision2d as child. A script attached to the area2d have onready variables pointing at both children. 
I have tested the scene and works with no problem, so I duplicated with a new name, then I have duplicated the script with a new name as well and connected to the new scene using the inspector.
At this point I have renamed the sprite child without problem, but then I renamed the collision2d child and Godot freeze.
When I press windows+tab to switch application I can see Godot but also, like a separate application (see circle) the selected node I was renaming. 
Clicking on any of them didn't make any difference
![Screenshot from 2023-08-07 21-45-13](https://github.com/godotengine/godot/assets/64071585/f079f673-5a04-419e-b739-ae191c2e3761)
I have to kill from the monitor and restart Godot.
Once restarted I have tried to duplicate the issue, but without luck
Attached the actual project I was working

### Steps to reproduce

Create an area2d node
add a sprite and a collision 2d child
add a script to the area2d with onready variables for both child
save
duplicate the scene with a new name
duplicate the script with a new name
connect the new script from the inspector
rename all child

### Minimal reproduction project

this is the correct version
[System.zip](https://github.com/godotengine/godot/files/12279597/System.zip)
Repository: rust
Issue: Miri violation in std/src/sys/sgx/waitqueue/unsafe_list.rs
Labels: C-bug,T-libs,O-SGX

As of Aug 7, 2023, the [unsafe list implementation in sgx waitqueue](https://github.com/rust-lang/rust/blob/master/library/std/src/sys/sgx/waitqueue/unsafe_list.rs) has a violation against Stacked Borrows.
Here is the [playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=20eef563e21f5ef6c97abdf6e97ced97); executing it with miri produces an error.

```
......

error: Undefined Behavior: trying to retag from <1601> for SharedReadOnly permission at alloc960[0x0], but that tag does not exist in the borrow stack for this location
   --> /playground/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/non_null.rs:377:18
    |
377 |         unsafe { &*self.as_ptr().cast_const() }
    |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                  |
    |                  trying to retag from <1601> for SharedReadOnly permission at alloc960[0x0], but that tag does not exist in the borrow stack for this location
    |                  this error occurs as part of retag at alloc960[0x0..0x18]
    |
    = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
    = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information

......
```

I basically copy-pasted `library/std/src/sys/sgx/waitqueue/unsafe_list{.rs,/tests.rs}` into the playground link. I made a few minor modifications that should not affect the result:
* Changed `use crate::ptr::NonNull` to `use std::ptr::NonNull` and `rtassert!(...)` to `assert!(...)`
* Manually invokes the `push_pop()` test in `main()` (other test cases exhibit the same error)

It looks like an actual violation to me. Because
* `self.head_tail` is a mutable reborrow from `self.head_tail_entry` constructed in `init()`
* Later in `pop()`, the compiler retags (which is a Stacked Borrows rule) fields of `self`, invalidating any old references to its fields including `self.head_tail`.
* In the `is_empty()` called by `pop()`, we try to use the invalidated pointer.

The last change to unsafe_list.rs was two years ago and it's a private module only used in `sys/sgx/waitqueue`, so the problem might not be that severe.
Still, I wonder whether this is a false positive of miri, or can we confirm it's a Stacked Borrows/memory-safety violation.
Repository: opencv
Issue: Inconsistent charuco board detection
Labels: bug,category: objdetect

### System Information

OpenCV python version: 4.7.0.72/4.8.0.74
OS: Debian 11 bullseye
Python: 3.9.2

### Detailed description

OpenCV 4.7.0.72
![charuco-4 7](https://github.com/opencv/opencv/assets/1102205/55f72d53-3ece-471f-8c66-07164eb3f33b)
detector
OpenCV 4.8.0.74
![charuco-4 8-fragment](https://github.com/opencv/opencv/assets/1102205/e1aa66ce-67a3-4701-b9cd-fb169e4d6290)

Both versions detect the board in the wrong way: all markers of the visible border should be found and all markers detected outside the board should be excluded. 

### Steps to reproduce

```python
# Set detector parameters
detector_parameters = cv.aruco.DetectorParameters()
detector_parameters.cornerRefinementMethod = cv.aruco.CORNER_REFINE_SUBPIX

# Create detector
detector = cv.aruco.CharucoDetector(board)
detector.setDetectorParameters(detector_parameters)

# Detect board
gray = cv.cvtColor(image, cv.COLOR_BGR2GRAY)

charuco_corners, charuco_ids, markers_corners, markers_ids = detector.detectBoard(gray)

cv.aruco.drawDetectedCornersCharuco(image, charuco_corners, charuco_ids)
cv.imshow("Image", image)
cv.waitKey(0)
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: deno
Issue: Watch mode for deno compile is documented but not implemented
Labels: bug,compile

Hello,

Watch mode is documented as working on `deno compile` in the CLI docs:

https://deno.land/manual@v1.36.0/getting_started/command_line_interface#watch-mode

However, it doesn't appear to be implemented in denoo 1.36 at present:

```
% deno -V
deno 1.36.0
% deno compile --watch src/main.ts
error: unexpected argument '--watch' found
```

I'm working on a CLI app, so this would make testing easier. For now, I'll just use `watchexec`.
Repository: next.js
Issue: Can't navigate to all radio options via arrow keys in Firefox
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 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.2.0
      npm: 8.9.0
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.13-canary.18
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


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

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/ariross-ef/nextjs-issue-radio-arrow-nav

### To Reproduce

This bug is only observed in Mozilla Firefox.   Arrow key behavior for radio options works as expected in Chrome

1. Run with npm run dev
2. Navigate to the home page (http://localhost:3000/) in Mozilla Firefox
3. Use `Tab` key to navigate to first radio option
4. Use `ArrowRight` or `ArrowDown` key to try to reach each radio option

### Describe the Bug

When navigating through radio options using arrow keys in Mozilla Firefox, only the first two radio options are cycled through


https://github.com/vercel/next.js/assets/106100062/17e5eaa4-8690-4df9-ad7c-c4bc3a4452c6



### Expected Behavior

Users should be able to navigate to all radio options using keyboard arrow keys (ArrowRight and ArrowDown to navigate forward, ArrowLeft and ArrowUp to navigate back).  See working example by viewing the homepage in Chrome, or you can test the radio buttons on the [MDN radio button docs](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/radio) (which also works as expected in Firefox)

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

Firefox 116.0.1

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

_No response_
Repository: youtube-dl
Issue: HTTP Error 503: Service Unavailable on www3.nhk.or.jp
Labels: broken-IE

## Checklist

- [*] I'm reporting a broken site support
- [*] I've verified that I'm running youtube-dl version **2021.12.17**
- [*] I've checked that all provided URLs are alive and playable in a browser
- [*] I've checked that all URLs and arguments with special characters are properly quoted or escaped
- [*] I've searched the bugtracker for similar issues including closed ones


## Verbose log
```

$ ./youtube-dl -v https://www3.nhk.or.jp/nhkworld/en/ondemand/video/2032293/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www3.nhk.or.jp/nhkworld/en/ondemand/video/2032293/']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2023.08.07 [86e3cf5e5] (single file build)
[debug] ** This version was built from the latest master code at https://github.com/ytdl-org/youtube-dl.
[debug] ** For support, visit the main site.
[debug] Python 3.11.4 (CPython x86_64 64bit) - Linux-6.4.2-060402-generic-x86_64-with-glibc2.37 - OpenSSL 3.0.8 7 Feb 2023 - glibc 2.37
[debug] exe versions: ffmpeg 5.1.2, ffprobe 5.1.2, rtmpdump 2.4
[debug] Proxy map: {}
[NhkVod] 2032-293: Downloading JSON metadata
[Piksel] nw_vod_v_en_2032_293_20230803113000_01_1691031888: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 503: Service Unavailable (caused by <HTTPError 503: 'Service Unavailable'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/storage/tmp/./youtube-dl/youtube_dl/extractor/common.py", line 665, in _request_webpage
    return self._downloader.urlopen(url_or_request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/storage/tmp/./youtube-dl/youtube_dl/YoutubeDL.py", line 2465, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 525, in open
    response = meth(req, response)
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 634, in http_response
    response = self.parent.error(
               ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 563, in error
    return self._call_chain(*args)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 496, in _call_chain
    result = func(*args)
             ^^^^^^^^^^^
  File "/usr/lib/python3.11/urllib/request.py", line 643, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

```




## Description

For some time, youtube-dl no longer works on NHK World, i.e. https://www3.nhk.or.jp/nhkworld/en/ondemand/video/2032293/

It errors as above.
Tried the last "stable" version 2021.12.17 and the last "nightly" (2023.08.07).
Repository: rust
Issue: `OsString` `Debug` implementation prints escaped single quotes
Labels: T-libs,A-fmt

```rust
fn main() {
    let string = "'";
    assert_eq!(
        format!("{:?}", string),
        format!("{:?}", std::ffi::OsString::from(string))
    );
}
```
produces
```
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `"\"'\""`,
 right: `"\"\\'\""`', src/main.rs:3:5
```

[(playground)](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=1e909c9c03f2832a570d0be23a0fd373)

#83046 reported the behavior of `<str as Debug>::fmt` escaping single quotes, and it was changed in #83079. Should we do the same for `OsString`?

I ran into this in #114132. It seems easy to fix for unix:
```diff
diff --git a/library/core/src/str/lossy.rs b/library/core/src/str/lossy.rs
index 59f873d1268..7e5ae364361 100644
--- a/library/core/src/str/lossy.rs
+++ b/library/core/src/str/lossy.rs
@@ -1,3 +1,4 @@
+use crate::char::EscapeDebugExtArgs;
 use crate::fmt;
 use crate::fmt::Formatter;
 use crate::fmt::Write;
@@ -85,7 +86,11 @@ fn fmt(&self, f: &mut Formatter<'_>) -> fmt::Result {
                 let valid = chunk.valid();
                 let mut from = 0;
                 for (i, c) in valid.char_indices() {
-                    let esc = c.escape_debug();
+                    let esc = c.escape_debug_ext(EscapeDebugExtArgs {
+                        escape_grapheme_extended: true,
+                        escape_single_quote: false,
+                        escape_double_quote: true,
+                    });
                     // If char needs escaping, flush backlog so far and write, else skip
                     if esc.len() != 1 {
                         f.write_str(&valid[from..i])?;
```
But on windows `OsString` is implemented using `Wtf8`, which is in `std` rather than `core`, which means it can't call `char::escape_debug_ext`: https://github.com/rust-lang/rust/blob/139b49b99523c43219b39079aa8fb2e084c52a1c/library/std/src/sys_common/wtf8.rs#L532
Repository: next.js
Issue: Custom 500.tsx not shown when using rewrites and dynamic routes
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 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.17.0
      npm: 9.6.7
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.14-canary.0
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


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

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/kletse/custom-error-with-redirects-bug

### To Reproduce

When you have a custom 500.tsx, a dynamic page with getServerSideProps that throws an error, and (any) rewrites in your next.config.js, the page renders instead of the 500 error.

Test this with a build (npm run build && npm run start), not in dev-mode.

pages/[id].tsx
```tsx
import { GetServerSideProps } from "next";

export default function Home() {
  return (
    <main>
      This page should not be visible because an error is thrown in
      getServerSideProps
    </main>
  );
}

export const getServerSideProps: GetServerSideProps = async () => {
  throw new Error("Server Error");
  return {
    props: {},
  };
};
```

pages/500.tsx
```tsx
import { NextPage } from "next";

const Custom500: NextPage = () => {
  return <div>Custom 500</div>;
};

export default Custom500;
```

next.config.js
```javascript
/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  rewrites: async () => [
    {
      source: "/source",
      destination: "/destination",
    },
  ],
};

module.exports = nextConfig;
```

Visiting http://localhost:3000/some-id renders the content of the page, not an error.  
Remove the rewrites in next.config.js, and the custom error page works again.





### Describe the Bug

Having rewrites in next.config.js breaks custom error pages (500.tsx) when using dynamic routes with the page router.

### Expected Behavior

Display the custom 500.tsx error-page.

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

Chrome 115.0.5790.170 (Official Build) (arm64)

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

next start
Repository: go
Issue: x/net/netutil: TestLimitListenerSaturation killed with SIGQUIT after apparent deadlock
Labels: OS-NetBSD,NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/net/netutil" && test == "TestLimitListenerSaturation" && `SIGQUIT: quit` && `^golang\.org/x/net/netutil\.\(\*limitListener\)\.Accept` && goos == "netbsd"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/1f6b7b312b214b798c70a2ec4bb3856bd44dcc37)):

    SIGQUIT: quit
    PC=0x7be5c m=7 sigcode=0
    
    r0      0x4
    r1      0x0
    r2      0x0
    r3      0x0
    r4      0x400003d748
    r5      0x0
    r6      0x5
    ...
    	/var/gobuilder/buildlet/go/src/runtime/proc.go:404
    runtime.semacquire1(0x40002060b8, 0x78?, 0x1, 0x0, 0x28?)
    	/var/gobuilder/buildlet/go/src/runtime/sema.go:160 +0x208 fp=0x400004cdf0 sp=0x400004cda0 pc=0x5bdd8
    sync.runtime_Semacquire(0x400011e340?)
    	/var/gobuilder/buildlet/go/src/runtime/sema.go:62 +0x2c fp=0x400004ce30 sp=0x400004cdf0 pc=0x772bc
    sync.(*WaitGroup).Wait(0x40002060b0)
    	/var/gobuilder/buildlet/go/src/sync/waitgroup.go:116 +0x74 fp=0x400004ce50 sp=0x400004ce30 pc=0x82114
    golang.org/x/net/netutil.TestLimitListenerSaturation(0x4000224000)
    	/var/gobuilder/buildlet/gopath/src/golang.org/x/net/netutil/listen_test.go:203 +0x230 fp=0x400004cf60 sp=0x400004ce50 pc=0x137840
    testing.tRunner(0x4000224000, 0x1926b0)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: Straight Moving Cursor
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

A tool that is activated by hotkeys and after activation, causes the mouse pointer to move only horizontally or only vertically. It means that we can fix the mouse on the X axis and move it only on the Y axis. (or vice versa)

### Scenario when this would be used?

In graphic works that require very high accuracy. (For example, when we want to move a part of an image slightly to the right without moving a pixel up or down.)
In the UI design of software and applications on platforms that have a visual interface for design.

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: Theming not working
Labels: bug,needs triage

### Describe the bug

I followed [this instructions](https://storybook.js.org/docs/react/configure/theming) to change theme, brandTitle and brandImage are working, instead colors are not changing.
This is my theme:
```
// .storybook/theme.ts
import { create } from '@storybook/theming/create'

export default create({
    base: 'light',
    brandTitle: "Linealight's Storybook",
    brandUrl: 'https://www.linealight.com',
    brandImage: '/logo-full.png',
    brandTarget: '_blank',
    colorPrimary: '#00ff1e',
    colorSecondary: '#f50035',
    // UI
    appBg: '#f50035',
    appContentBg: '#f50035',
    appBorderColor: '#f50035',
    appBorderRadius: 4,

    // Text colors
    textColor: '#10162F',
    textInverseColor: '#00ff1e',

    // Toolbar default and active colors
    barTextColor: '#9E9E9E',
    barSelectedColor: '#585C6D',
    barBg: '#00ff1e',
})
```

### To Reproduce

_No response_

### System

```shell
Environment Info:

  System:
    OS: macOS 13.3.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 3.5.1 - /opt/homebrew/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  Browsers:
    Chrome: 115.0.5790.114
    Safari: 16.4
  npmPackages:
    @storybook/addon-designs: ^7.0.1 => 7.0.1 
    @storybook/addon-essentials: ^7.2.1 => 7.2.1 
    @storybook/addon-interactions: ^7.2.1 => 7.2.1 
    @storybook/addon-links: ^7.2.1 => 7.2.1 
    @storybook/blocks: ^7.2.1 => 7.2.1 
    @storybook/manager-api: ^7.2.1 => 7.2.1 
    @storybook/nextjs: ^7.2.1 => 7.2.1 
    @storybook/react: ^7.2.1 => 7.2.1 
    @storybook/testing-library: ^0.2.0 => 0.2.0 
    @storybook/theming: ^7.2.1 => 7.2.1
```


### Additional context

_No response_