sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Ḥ and ḥ for Arabic / Syriac
Labels: Idea-Enhancement,Help Wanted,Product-Quick Accent

### Microsoft PowerToys version

0.70.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Quick Accent

### Steps to reproduce

when I click h and want to output Ḥ and ḥ  I found nothing, but they are useful in romanization of Arabic and Syriac.
by the way I hope that after pressing letter key and left/right/space key, there are digitals below each letter with Accent, just like many chinese or japanese IME do.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: next.js
Issue: NextJS middleware crash does not target global-error.tsx
Labels: Middleware

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant packages:
      next: 13.4.5-canary.2
      eslint-config-next: 13.1.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.4
```


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

App directory (appDir: true), Middleware / Edge (API routes, runtime)

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

https://codesandbox.io/p/sandbox/nextjs-middleware-targets-error-tsx-on-crash-qz7cr5

### To Reproduce

1. Setup a basic repos with the latest NextJS (13.4.4, or canary)
2. Create an app folder with a RootLayout and a `global-error.tsx`
3. Add a `middleware.ts` outside of the app folder
4. Add `throw Error("test");` to the RootLayout

### Describe the Bug

Throw an error in the RootLayout inside the app directory while having a middleware, and you would expect it to use the `global-error.tsx`.

Instead this gets displayed:

<img width="599" alt="image" src="https://github.com/vercel/next.js/assets/101802812/5e3b1237-8a79-4dd3-9c5a-c4f480a47708">

Downgrading to for example NextJS 13.1.1 fixes the issue and does display the `global-error.tsx`.

### Expected Behavior

I would expect it to show the output of the `global-error.tsx`.

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

_No response_

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

_No response_
Repository: TypeScript
Issue: FAQ broken link
Labels: Docs

https://github.com/microsoft/TypeScript/wiki/FAQ#how-do-i-write-unit-tests-with-typescript

> How do I write unit tests with TypeScript?
> [Typescript Deep Dive](https://basarat.gitbooks.io/typescript/docs/testing/jest.html)

the link here is "Sorry page not found"
Repository: storybook
Issue: CLI: csf-2-to-3 codemod type improvements
Labels: help wanted,maintenance,csf3,codemods

### Describe the bug

The `csf-2-to-3` codemod currently produces the following CSF3 code:

```ts
export default { .... } as Meta<typeof Foo>;

export const MyStory = { ... }
```

It should produce:

```ts
const meta: Meta<typeof Foo> = { ... };
export default meta;

type Story = StoryObj<typeof Foo>;
export const MyStory: Story = { ... }
```

Discussion: https://discord.com/channels/486522875931656193/1110567774033559663

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: bitcoin
Issue: Remove Ambiguity of Script ASM Hex and Decimal Integer Representations
Labels: Feature,RPC/REST/ZMQ

### Please describe the feature you'd like to see added.

Distinguish between decimal and hex integers in the script ASM to avoid ambiguity. Hex integers/data can be prefixed with `0x` to avoid ambiguity.

### Is your feature related to a problem, if so please describe it.

When scripts are decoded into ASM, two different integers can be displayed identically, with one as hex and the other as decimal. `decodescript 0511121314150457c74942` produces ASM of `1112131415 1112131415` , despite the integers being different. There is no distinction between hex and decimal. 


### Describe the solution you'd like

Prefixing `0x` makes the most sense to me.

### Describe any alternatives you've considered

All data could be provided as hex, or "d" could be added to decimals. Removing ambiguity is the primary concern here.

### Please leave any additional context

_No response_
Repository: PowerToys
Issue: Peek - PDF Document properties units not reflect system regional settings
Labels: Issue-Bug,Needs-Triage,Product-Peek

### Microsoft PowerToys version

0.70.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Peek

### Steps to reproduce

Press the settings wheel when you preview a PDF. Press the Document properties.
[PowerToysReport_2023-05-31-13-15-58.zip](https://github.com/microsoft/PowerToys/files/11612367/PowerToysReport_2023-05-31-13-15-58.zip)


### ✔️ Expected Behavior

Showing The first PDF page size in the the units defined in the OS regional settings. 

### ❌ Actual Behavior

Showing The first PDF page size in inches. The regional settings are defined as metric.
![Screenshot 2023-05-31 130716](https://github.com/microsoft/PowerToys/assets/18667126/5a731f25-7bbf-4aaf-899e-da1f0278e9e3)


### Other Software

_No response_
Repository: storybook
Issue: [Feature Request]: Default attached docs page to start of components stories list
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

Using the autodocs feature the docs page for a component appears before it's stories pages in the sidebar, meaning when you click on the root of the folder it selects the docs page automatically. However in the cases where we're writing custom mdx files for a component and attaching it with the Meta block of prop, the docs page appears at the end of the list, creating an inconsistent experience. 

The only workaround I've found for this is to provide custom sorting function in the preview file, but this isn't ideal as it prevents us using the object syntax for story sorting which is far more convenient for the rest of our sorting requirements.

### Describe the solution you'd like

I think it makes more sense for the docs page to always appear at the beginning of the stories for a component, with both autodocs and custom docs.
Repository: rust
Issue: Tracking Issue for `std::ffi::c_str` module
Labels: T-libs-api,C-tracking-issue,disposition-merge,finished-final-comment-period

Feature gate: `#![feature(c_str_module)]`

This is a tracking issue for the `std::ffi::c_str` module.

<!--
Include a short description of the feature.
-->

### Public API

This adds `{core, alloc, std}::ffi::c_str` modules and migrates some existing types into them. Types will still be re-exported in their current places to ensure compatibility.

The following migrations are made:

* `core::ffi::CStr` => `core::ffi::c_str::CStr`
* `core::ffi::FromBytesUntilNulError` => `core::ffi::c_str::FromBytesUntilNulError`
* `core::ffi::FromBytesWithNulError` => `core::ffi::c_str::FromBytesWithNulError`
* `alloc::ffi::CString` => `alloc::ffi::c_str::CString`
* `alloc::ffi::FromVecWIthNulError` => `alloc::ffi::c_str::FromVecWIthNulError`
* `alloc::ffi::IntoStringError` => `alloc::ffi::c_str::IntoStringError`
* `alloc::ffi::NulError` => `alloc::ffi::c_str::NulError`

And these types are also migrated on the `std` crate as well.

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] API change proposal (ACP)[^1]: rust-lang/libs-team#134
- [x] Implementation: #112136
- [ ] Final comment period (FCP)[^2]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- [ ] Should `c_str` and `c_string` be separated? This was not discussed in the original ACP.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/api-change-proposals.html
[^2]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: PowerToys
Issue: Peek does not work when using separate Explorer processes 
Labels: Issue-Bug,Needs-Triage,Product-Peek

### Microsoft PowerToys version

0.70.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Peek

### Steps to reproduce

While testing the Peek function I noticed that it only worked for the first explorer window when using the 
![image](https://github.com/microsoft/PowerToys/assets/6932991/c0e3239b-2dde-4535-872b-d5038a45f943)
setting.

### ✔️ Expected Behavior

That the Peek window should be triggered when selecting a file in any explorer window.

### ❌ Actual Behavior

Nothing happens when activating peek for files in other explorerwindows than the first.

### Other Software

_No response_
Repository: deno
Issue: Support "JavaScript Debug Terminal" from VS Code in Deno inspector
Labels: cli,suggestion

https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_javascript-debug-terminal

It seems to inject a `VSCODE_INSPECTOR_OPTIONS` and some `NODE_OPTIONS` env vars that are used to start and attach the inspector.
Repository: go
Issue: x/build/cmd/gerritbot: TestCommitMessage failures with dynamic link warnings on macOS
Labels: OS-Darwin,Builders,NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/build/cmd/gerritbot" && test == "TestCommitMessage" && `One of the two will be used. Which one is undefined.`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/7e5f77acfdc5767d78d6aab434a0015ec5065a2e)):

    --- FAIL: TestCommitMessage (9.87s)
        --- FAIL: TestCommitMessage/simple (9.85s)
            gerritbot_test.go:119: got unexpected commit message (-got +want)
                  (
                  	"""
                - 	objc[4533]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x1f33237e8) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x111e2c2b8). One of the two will be used. Which one is undefined.
                - 	objc[4533]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1f3323838) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x111e2c308). One of the two will be used. Which one is undefined.
                - 	objc[4781]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x1f33237e8) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x10df1c2b8). One of the two will be used. Which one is undefined.
                - 	objc[4781]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1f3323838) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x10df1c308). One of the two will be used. Which one is undefined.
                  	cmd/gerritbot: title of change
    
                  	... // 6 identical lines
                  	"""
                  )


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: Inconsistent Link component cache behaviour while prefetching using page router
Labels: bug,Navigation,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #43~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 21 16:51:08 UTC 2
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0
```


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

Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

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

https://github.com/saldomik/next-js-link-behavoiur

### To Reproduce

1. Build & start the provided example app
2. Click on Page1 link
3. A cookie my-token should now be created (simulating a login)
4. Now click on Home link
5. Despite the control in the middleware, the home page is still loaded. The console log entered in the middleware appears correctly but the redirect is not performed.

### Describe the Bug

Presumably the caching mechanism during prefetching performed by the Link component no longer functions consistently. Until version 12 of the framework, the described situation did not occur and the redirect in the middleware was executed. It seems as if the application saves the first prefetch of the url, which takes place on the Home page, and does not re-evaluate it afterwards. This behaviour is breaking for anyone who relies on this logic to manage content after authentication.
In addition, the structure of the application is always linked to the routing within the page folder.

### Expected Behavior

The Link component performs the prefetch but the cache must not break other application logic. Cache re-evaluation must be allowed for applications that need it.

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

Chrome

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

Aws
Repository: stable-diffusion-webui
Issue: [Bug]: img2img api
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

i use img2img api  ,i want to implement  inpaint ,but iThe picture I got is like this
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/3301385/f939cff3-549e-42f7-8794-3d9a231decf5)
It looks like there's a mask, 
and my paramter is this 
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/3301385/89a5e844-69bd-4009-b32d-c0542e15be49)
how to solve it ?

### Steps to reproduce the problem

1. Go to .... 
2. Press ....
3. ...


### What should have happened?

i want corrent image

### Commit where the problem happens

89f9faa63388756314e8a1d96cf86bf5e0663045

### What Python version are you running on ?

Python 3.10.x

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

Windows

### What device are you running WebUI on?

Other GPUs

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

Google Chrome

### Command Line Arguments

```Shell
no
```


### List of extensions

no

### Console logs

```Shell
no
```


### Additional information

_No response_
Repository: next.js
Issue: [App Router] The redirect function of 'next/navigation' package stay in pending status
Labels: Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #136-Ubuntu SMP Fri Jun 10 13:40:48 UTC 2022
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 1.22.18
      pnpm: N/A
    Relevant packages:
      next: 13.4.5-canary.2
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


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

App directory (appDir: true)

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

https://gitlab.com/incubateur-territoires/startups/donnees-et-territoires/nextjs-bug-reproduction

### To Reproduce

Start the project in local with `npm run dev`
Open the inspector on network tab
Click on the `Submit` button and see that the page `/redirection` stay in `pending` state. But if you go directly to the url `http://localhost:3000/redirection` it's work. 

### Describe the Bug

The redirection from route is not working
With nextjs version `13.3.0` it was working fine

### Expected Behavior

I expect that when you click on the submit button it go to the `/redirection` page.

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

Chrome 110.0.5481.77

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

npm run dev
Repository: create-react-app
Issue: createRoot causes various issues with performance and css behaviour 
Labels: needs triage,issue: bug report

### Describe the bug
After upgrading our project, I realised that all the antd components with the tooltips or menus has the flickering issue when hovering off them as well as our table which is used to be very fast in performance, with the new upgrades became slow in scrolling responses and rendering. So I debugged down to 1 line of code which was causing this issue. It was the way we render the App component using createRoot.

### Steps to reproduce
1. Go to https://codesandbox.io/s/jolly-kalam-5mu6oi?file=/src/index.js
2. Try hover on the button, you will see the tooltip flickering when you hover off the button. 
3. Try to modify the index.js and render the App the old way using ReactDOM.render
4. Hover on the button and the tooltip will act normally 

### Expected behavior
Tooltips of antd components should not flicker on hover off 

### Actual behavior
Tooltips, menus of antd components flicker on hover off
Repository: flutter
Issue:  In the team's development mode, Flutter SDK Version Consistency Management.
Labels: c: new feature,tool,P3,team-tool,triaged-tool

Under the development of the team. This dependency on downloading the Flutter SDK locally for each developers cannot guarantee the consistency of the Flutter SDK version and automatic management. If the Flutter SDK version is inconsistent at development time. This may cause problems with the Api compatibility of the Dart layer and the inconsistency of the Flatter virtual machine.
Repository: material-ui
Issue: [Tooltip] Stays open when the anchor is moved away from the cursor (Firefox only)
Labels: component: tooltip,package: material-ui,package: joy-ui,browser: Firefox

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/s/condescending-solomon-7vrktj

Steps:

1. Open the demo in Firefox
2. Hover a list item
3. Wait for the list to shuffle


### Current behavior 😯

The tooltip stays open even though the anchor is not hovered anymore (the anchor was moved)

https://github.com/mui/material-ui/assets/13808724/6cd18c6a-91de-485a-926d-2b3de3eb7d62



### Expected behavior 🤔

Same as in Chrome - the tooltip should close once the anchor is not hovered anymore

### Context 🔦

I can reproduce the issue using `Tooltip` both from `@mui/material` and `@mui/joy`:
- `@mui/material`: https://codesandbox.io/s/condescending-solomon-7vrktj
- `@mui/joy`: https://codesandbox.io/s/fast-leaf-oyfx1x?file=/demo.tsx

It seems like the `mouseleave` event is not emitted in Firefox when the order of the elements changes.

This issue was originally reported in https://github.com/mui/mui-x/issues/9161

### 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>
Repository: next.js
Issue: Next dev or Next build doesn't keep running stops automatically
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: x64
      Version: Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.5-canary.2
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


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

Package manager (npm, pnpm, Yarn)

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

https://github.com/JesusGerardoAguiar/nextjs-template

### To Reproduce

Just having my same node version, i don't know if it is exactly related to the node version or what

### Describe the Bug

Basically I'm trying to run the latest version of Nextjs (13.4.4) with Node Version v18.16.0 and it just stops without any error message,

![image](https://github.com/vercel/next.js/assets/42016025/e80f9ea8-1223-48ce-9819-4eb2eb707554)


Same happens with next build command, also, i tried with Yarn resulting in the same output, yarn version being 1.22.10

Also, for some reason, this doesn't happen with Nextjs version 13.0.0

I've tried everything, from changing node versions, to deleting caches, nothing works

my package.json is: 

`{ "name": "nextjs", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint" }, "dependencies": { "eslint": "8.41.0", "eslint-config-next": "13.4.4", "next": "13.4.4", "react": "18.2.0", "react-dom": "18.2.0" } }`

IMPORTANT: this doesn't happen in Next 13.0, goes only from 13.1 to 13.4

### Expected Behavior

for expected behavior i would say that it should work haha

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

_No response_

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

Vercel
Repository: vscode
Issue: Nonce does not appear to work on fish shell
Labels: bug,help wanted,terminal-shell-fish

Testing https://github.com/microsoft/vscode/issues/181522

Other shells are okay, but fish shell did not appear to have a nonce, and prompted for confirmation when rerunning a command

<img width="1220" alt="image" src="https://github.com/microsoft/vscode/assets/2230985/1e4cf5db-b3ca-4773-b72e-82f2e5db68bc">
Repository: PowerToys
Issue: Fancy Zone Editor Pixel With Input
Labels: FancyZones-Editor,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

I think it would be good to have it to where we can input the pixel width we'd like on the FancyZones editor. Currently after you create the layout and click the "Edit Pen" on that layout there is a slider with a Label next to it for the amount. This is fine, I would suggest changing the label to an input so we can just enter a value.

### Scenario when this would be used?

Can be helpful getting all of the different layouts to look uniform in the distance between them.

### Supporting information

![FancyZones1](https://github.com/microsoft/PowerToys/assets/8476472/226b170a-ee5a-4bbd-8e57-e712d45e1f2a)