sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Search & Replace is behaving strange for readonly files
Labels: bug,search,confirmed

We support readonly file system providers and indicate this typically with a lock icon and a readonly editor. When you do a search & replace operation from the view over these files, the edits are still applied, even though the underlying model is not writeable. 

When you close and reopen the editor, these changes are gone. 

**Steps:**
* open a workspace and take note of the path
* do a search & replace over a subfolder
* it will work fine
* edit the [`isReadonly`](https://github.com/microsoft/vscode/blob/d6290ef6582acecbf3bca1558111f2ee64375801/src/vs/workbench/services/textfile/common/textFileEditorModel.ts#L1158) condition of text models to return `true` when the resource is in the subfolder
* repeat the steps after restart
* you should see a lock icon when opening files of the sub folder
* the edits are applied but lost when you close and reopen the editor
Repository: PowerToys
Issue: Extended Task View - Add Common group
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

The Task View feature toggles between all applications. Since there are apps that you want to use in common, such as chat and browser, it would be convenient to have a function to create a common display group.

### Scenario when this would be used?

When you drag and drop an attachment onto an email screen that is open in your browser, you don't need to reopen the explorer or move the explorer view in the email screen view.

### Supporting information

_No response_
Repository: vscode
Issue: Merge Editor: Add a single line diff view on 3-way-merge
Labels: feature-request,merge-editor

<!-- ⚠️⚠️ 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. -->
Beyond compare 4 has a small header above the result pane, that shows the selected line from the 3 merged versions (base, current, incoming), and highlights the changes.

This is very useful when trying to inspect the changes between them.

Example:
![image](https://user-images.githubusercontent.com/1246544/234778666-75e4e5ae-e9cc-4c1e-adbc-28160bd1c731.png)

Notice that in the side-by-side diff it's harder to notice the exact changes in each side, while the single-line view utilizes the whole window width, and it's easier to compare them. On this example, you can notice that Current (the left side, top row, light-blue arrow) added `, [BotFramework]` and did *not* delete the parenthesis, while the Incoming (right side, bottom row, purple arrow) added `, [InboundTeamsConnAmount],` and *did* delete the parenthesis (it moved to the next line). The changed parts are also highlighted.

It would be very nice to have this kind of diff in the merge editor.
Repository: storybook
Issue: [Bug]: Story with `render` will show the full story CSF definition in "Show Code" in docs
Labels: question / support,has workaround,addon: docs

### Describe the bug

If a story has a `render` function, the code emitted to the source viewer in docs will be the full story definition, instead of just the content of the render function. It shouldn't show the full object, including `play`, `args`, etc.

### To Reproduce

Reproduced here: https://stackblitz.com/edit/github-kja1qs?file=src/stories/Button.stories.tsx

![image](https://user-images.githubusercontent.com/5678122/234806598-f379aacf-641c-4618-9698-9a6e326c5ea5.png)


### System

```shell
Storybook `^7.1.0-alpha.9`
```


### Additional context

Originally reported here https://github.com/storybookjs/storybook/issues/21747#issuecomment-1520128615 by @bratanon and @zb-sj
Repository: rust
Issue: "LoadLibraryExW failed" when loading proc macros with too many -L search paths
Labels: O-windows,C-bug

On Windows, when the total length of `-L` search paths exceeds about 32k characters, `rustc` fails to load proc macro DLLs with the message:

```
error: LoadLibraryExW failed (retried 5 times)
 --> user.rs:2:1
  |
2 | extern crate procmacro;
  | ^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error
```

WinDbg suggests that the error returned is
```
LastErrorValue: (Win32) 0x8 (8) - Not enough memory resources are available to process this command.
LastStatusValue: (NTSTATUS) 0xc0000017 - {Not Enough Quota}  Not enough virtual memory or paging file quota is available to complete the specified operation.
```

I noticed that the search paths get added to the `PATH` environment variable (not sure where), but [environment variables have a limit of 32,767 characters](https://learn.microsoft.com/en-us/windows/win32/api/processenv/nf-processenv-setenvironmentvariablew). So my guess is that an overly full environment causes LoadLibraryExW to fail.

Repro gist: https://gist.github.com/goffrie/4fd3553a5417fda17d78e0f8a7252335
Run the commands in repro.ps1. Basically we just need an argfile to run rustc with a very long list of search paths, and then importing proc-macros fails.

This scenario is not likely when using Cargo, but rules_rust for Bazel generates one `-L` per transitive crate dependency which makes this not super difficult to hit.

### Meta
`rustc --version --verbose`:
```
rustc 1.69.0 (84c898d65 2023-04-16)
binary: rustc
commit-hash: 84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc
commit-date: 2023-04-16
host: x86_64-pc-windows-msvc
release: 1.69.0
LLVM version: 15.0.7
```
Repository: next.js
Issue: not rendered Suspense fallback when change route
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
react: >= 18
next: >= 12.1.0
```


### Which example does this report relate to?

all

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

not rendered Suspense fallback when change route

```tsx
function Component () {
  const { query: { page } } = useRouter();
  const { data } = useQuery([page], () => api.get('...', { params: { page } }) );

  return (
    <p>{data}</p>
  )
}

function App () {
  return (
    <Suspense fallback="loading...">
      <Component /> 
    </Suspense>
  )
}
```

**I think it's because of the startTransition of react**
https://github.com/vercel/next.js/blob/canary/packages/next/src/client/index.tsx#L518-L522

### Expected Behavior

render fallback component

can i perform this when provide startTransition option like priority of `next/image`?

ex) 
```tsx
function Component () {
  const { query: { page } } = useRouter({ priority: false });
}
function Component () {
  const router = useRouter();
  
  return <button onClick={() => router.push('/', '/', { priority: false })} />
}
```

### To Reproduce

[codesandbox](https://codesandbox.io/p/sandbox/react18-next13-c6hiw0?file=%2Fsrc%2Fcomponents%2FTest.tsx)
Repository: vscode
Issue: some snippet show suggestion preview, but some not
Labels: bug,suggest,inline-completions

`imp` can trigger

![image](https://user-images.githubusercontent.com/41773861/234835885-2ffa9e03-69d2-4a24-a3f9-9cbc37541d80.png)

`imb` can't:

![image](https://user-images.githubusercontent.com/41773861/234835986-db75c598-c11f-4ae1-b312-c50a6d1530cb.png)

both of them are one line suggest.

Snippet extension: https://marketplace.visualstudio.com/items?itemName=YuTengjing.ytj-snippets

Settings: 

```json
{
    "workbench.iconTheme": "vscode-icons",
    "editor.inlayHints.enabled": "on",
    "editor.inlineSuggest.enabled": true,
    "typescript.inlayHints.parameterNames.enabled": "all",
    "editor.suggest.preview": true,
}
```

@hediet 

```
Version: 1.77.3 (Universal)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:19:37.325Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin x64 22.4.0
Sandboxed: No
```
Repository: youtube-dl
Issue: rutube TVshow tabs
Labels: geo-restricted,site-update-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar site feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a site feature request
- [] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've searched the bugtracker for similar site feature requests including closed ones


## Description

<!--
Provide an explanation of your site feature request in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

WRITE DESCRIPTION HERE
rutube has tvshow tabs
https://rutube.ru/metainfo/tv/283095/tab27106/ example link(not working anymore)

Got updated to https://rutube.ru/metainfo/tv/283095/deep/

However tabs are beeing ignored
![msedge_Y6wNDO0qQW](https://user-images.githubusercontent.com/82664161/234836184-4f8eed82-cca9-4627-98ff-74589b44dd32.png)
Repository: react-native
Issue: Xcode IOS run YogaKit.modulemap' not found
Labels: Platform: iOS,Needs: Triage :mag:,Newer Patch Available

### Description

/Users/qinque/Library/Developer/Xcode/DerivedData/otam-hgtpqpfwdvlloxhkrzdsjqyxdctg/Build/Intermediates.noindex/otam.build/Debug-iphonesimulator/otam.build/DerivedSources/otam_vers.c module map file '/Users/qinque/Library/Developer/Xcode/DerivedData/otam-hgtpqpfwdvlloxhkrzdsjqyxdctg/Build/Products/Debug-iphonesimulator/YogaKit/YogaKit.modulemap' not found


When Xcode runs, it prompts an error

<img width="1255" alt="image" src="https://user-images.githubusercontent.com/38272529/234841948-d2adc36a-9a47-46b3-a1aa-d40de46bf856.png">
<img width="1255" alt="image" src="https://user-images.githubusercontent.com/38272529/234842052-11bb9d06-a576-4b82-86f4-61e0c7dfbbfa.png">


### React Native Version

0.70.4

### Output of `npx react-native info`

info Fetching system and libraries information...
System:
    OS: macOS 13.0
    CPU: (8) arm64 Apple M1
    Memory: 93.95 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
    Watchman: 2023.04.24.00 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.12.1 - /Users/qinque/.rvm/gems/ruby-2.7.5/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 14.1/14B47b - /usr/bin/xcodebuild
  Languages:
    Java: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.1.0 => 18.1.0 
    react-native: 0.70.4 => 0.70.4 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

### Steps to reproduce

xxx. xcodeproj  Xcode -> build

### Snack, code example, screenshot, or link to a repository

![image](https://user-images.githubusercontent.com/38272529/234842397-630ac292-bda9-4a4b-9d99-d9e702fcde26.png)


And I found that the Libraries file is empty

<img width="235" alt="image" src="https://user-images.githubusercontent.com/38272529/234842697-3067f943-f8c0-4acd-bfc7-20793b7d24e7.png">
Repository: storybook
Issue: [Bug]: Code of React components showing as <forwardRef>
Labels: bug,help wanted,react,sev:S3

### Describe the bug

I'm using the generated React components of [Stencil Output React](https://stenciljs.com/docs/react) inside a Storybook instance running with React, everything works perfectly but when I click to check the component code it appears as follows:

```js
<forwardRef>
  Button
</forwardRef>
```

The correct view should be:

```js
<MyButton>
  Button
</MyButton>
```

I haven't found anything that could help me with this, especially since these wrappers are automatically generated by the Stencil and I have no way of modifying the output.

Can anyone help me?

### To Reproduce

_No response_

### System

```shell
Environment Info:
  System:
    OS: macOS 13.2.1
    CPU: (8) x64 Apple M1 Pro
  Binaries:
    Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v18.13.0/bin/npm
  Browsers:
    Chrome: 111.0.5563.64
    Firefox: 109.0.1
    Safari: 16.3
  npmPackages:
    @storybook/addon-a11y: ^7.0.1 => 7.0.2 
    @storybook/addon-docs: ^7.0.1 => 7.0.7 
    @storybook/addon-essentials: ^7.0.1 => 7.0.7 
    @storybook/addon-mdx-gfm: ^7.0.2 => 7.0.2 
    @storybook/addons: ^7.0.1 => 7.0.2
    @storybook/preset-typescript: ^3.0.0 => 3.0.0 
    @storybook/react: ^7.0.7 => 7.0.7 
    @storybook/react-webpack5: ^7.0.1 => 7.0.7 
    @storybook/theming: ^7.0.1 => 7.0.2
```


### Additional context

<img width="782" alt="image" src="https://user-images.githubusercontent.com/3603793/234870208-3d405ee4-9d30-4722-81cb-75669b7d7ec4.png">
Repository: material-ui
Issue: Grid2 and Fragment: missing padding on Grid item
Labels: component: Grid,enhancement

### 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/festive-ully-7fjqbf


### Current behavior 😯

In the provided example the grid item "L2 (Fragment) - Node" doesn't get the padding.

### Expected behavior 🤔

In the provided example the grid item "L2 (Fragment) - Node" should get the padding according to the container.

### Context 🔦

I have a complex structure with nested Grid2 containers, the new implementation (from v5.12.1) breaks the layout of my components.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 13.3.1
  Binaries:
    Node: 20.0.0 - /usr/local/bin/node
    Yarn: 3.4.1 - /opt/homebrew/bin/yarn
    npm: 9.6.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 112.0.5615.137
    Edge: Not Found
    Firefox: 112.0.2
    Safari: 16.4
  npmPackages:
    @emotion/react: ^11.10.6 => 11.10.6 
    @emotion/styled: ^11.10.6 => 11.10.6 
    @mui/base: ^5.0.0-alpha.127 => 5.0.0-alpha.127 
    @mui/core-downloads-tracker:  5.12.2 
    @mui/icons-material: ^5.11.16 => 5.11.16 
    @mui/lab: ^5.0.0-alpha.128 => 5.0.0-alpha.128 
    @mui/material: ^5.12.2 => 5.12.2 
    @mui/private-theming:  5.12.0 
    @mui/styled-engine:  5.12.0 
    @mui/system: ^5.12.1 => 5.12.1 
    @mui/types:  7.2.4 
    @mui/utils:  5.11.13 
    @mui/x-data-grid:  6.2.1 
    @mui/x-data-grid-premium: ^6.2.1 => 6.2.1 
    @mui/x-data-grid-pro:  6.2.1 
    @mui/x-date-pickers:  6.2.1 
    @mui/x-date-pickers-pro: ^6.2.1 => 6.2.1 
    @mui/x-license-pro:  6.0.4 
    @types/react:  18.0.14 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript:  4.7.4 
```
</details>

I'm using Google Chrome
Repository: rust
Issue: Tracking issue for cleaning up std's thread_local implementation details
Labels: C-cleanup,A-thread-locals,T-libs

`std::thread_local`, `std::thread::local`, `std::thread::local_impl`, `std::sys_common::thread_local_key`, `std::sys_common::thread_local_dtor`, `std::sys::thread_local_key`, etc. etc. are all messy and form quite a confusing maze. Just look at this map I tried to draw of it all:

![tlmap](https://user-images.githubusercontent.com/783247/234870944-1af910ef-81b7-4e7a-b748-e4212f86e2ca.jpg)

AAAaaaaAaa

Time to clean it up.

And maybe also fix some bugs while we're at it. ^^

---

- [x] Initial name and module cleanup without touching implementation: https://github.com/rust-lang/rust/pull/110861
- [x] Remove unused `Key` type: https://github.com/rust-lang/rust/pull/110898
- [x] Fix panic-in-drop handling
  - [x] https://github.com/rust-lang/rust/issues/112285
    - [x] https://github.com/rust-lang/rust/pull/112292
- [x] Stop calling everything `Key`, because most of those things are actually not keys, and drop `LazyKeyInner`
   - [x] rust-lang/rust#116123
   - [x] rust-lang/rust#122494
   - [x] rust-lang/rust#123724
- [x] Reduce the amount of code in the `thread_local!{}` expansion. rust-lang/rust#125525 
- [x] Use `*const T` rather than `&'static T` when it's not really `'static`: rust-lang/rust#125525 
- [x] Clean up implementation more
   - [x] rust-lang/rust#126523
   - [x] rust-lang/rust#126953
   - [x] rust-lang/rust#128135 
- [x] Store thread ID and stack guard range in thread locals without destructors (on platforms with `#[thread_local]`)?
   - [x] Stack guard range: rust-lang/rust#123265 
   - [x] thread ID: rust-lang/rust#124881
- [x] Make `thread::current` thread local more efficient and make it available in (most) TLS destructors: rust-lang/rust#127912 
- [ ] Detect stack overflow in TLS destructors: rust-lang/rust#131282 

Related issues to solve, maybe:

- [x] https://github.com/rust-lang/rust/issues/110708
- [ ] https://github.com/rust-lang/rust/issues/111272
  - ~~https://github.com/rust-lang/rust/issues/109785~~ 
- [ ] Maybe [this](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=06885c38ad9982ec799d012a26d92305) shouldn't work? See conversation around [this comment](https://github.com/rust-lang/rust/issues/110897#issuecomment-1525738849).
- [ ] ...?
Repository: storybook
Issue: [Feature Request]: Provider for Apollo client in Angular storybook returns undefined client
Labels: feature request,compatibility with other tools,angular

### Is your feature request related to a problem? Please describe

When I supply the angular apollo provider below to a story I get undefined client, but if I use applicationConfig provider it works fine. The issue is that i am then unable to supply different mocks to stories as applicationConfig provider makes it global.

This fails with client undefined
```
export const Deferred: Story = {
  decorators: [
    moduleMetadata({
      providers: [
        {
          provide: APOLLO_OPTIONS,
          useFactory() {
            return {
              link: mockSingleLink(deferredMock),
              cache: new InMemoryCache({}),
            };
          },
        },
      ],
    }),
  ],
}
```



### Describe the solution you'd like

N/A

### Describe alternatives you've considered

N/A

### Are you able to assist to bring the feature to reality?

yes, I can

### Additional context

_No response_
Repository: vscode
Issue: Increase maximum problems per file (or allow customization)
Labels: feature-request,languages-diagnostics

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Currently we limit the number of problems a file shows to 1000. This was bumped from 250 to the current limit in #49687.

This limit is still fairly low on a "larger" file. If performance is the concern, it'd be nice to at least have this user-customisable.

A previous request was closed in #159223.
Repository: go
Issue: cmd/compile: support -buildmode=pie on OpenBSD
Labels: OS-OpenBSD,NeedsInvestigation,FeatureRequest

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version go1.20.1 openbsd/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes, I think so.

### What operating system and processor architecture are you using (`go env`)?

OpenBSD 7.3 on amd64

### What did you do?

I tried to build a PIE binary with -buildmode=pie


### What did you expect to see?

I was expecting to build a binary with PIE enabled.

### What did you see instead?

<pre>-buildmode=pie not supported on openbsd/amd64</pre>


Is there any particular reason that buildmode=pie is not supported on openbsd? Building with that buildmode returns that the buildmode=pie is not supported. 

clang on OpenBSD/amd64 defaults and produces PIE static/dynamic binaries without issue. But even external linking in Go suppresses PIE with LDFlags -Wl,-nopie. You can append -Wl,-pie through -extldflags option, the result will be expectedly an invalid function entry symbol table or a segmentation fault.

I could not find an open issue that works on this or explains the situation for the missing support. There are some that are years old and closed or some old mailing list entries. I get that openbsd is a secondary port, but why is there not even an issue that addresses the state/progress and situation? 

I'm just genuinely interested to see progress at this.

Thank you.
Repository: go
Issue: proposal: text/template: option for ignoring/returning errors in function calls
Labels: Proposal

The proposal is to add options like `error=zero`, `error=default` in a likewise fashion as in `missingkey=...`.

The intention is to let users specify how function calls inside templates should be handled. In a template pipeline with functions (or methods) calls with 2 returns, a value and an error, execution stops if the error is not nil. I think it would be useful if the user could specify how to proceed. So passing options seems to be a natural way. For example:

- the option `error=default` keeps the same behavior: stop execution
- `error=zero` sets the returned value to be the zero value for that type and keeps executing
- `error=errorvalue` sets the returned value to be the error and keeps executing

Of course the key name could be different I just used `error` here to clarify. Implementing this would make error handling in templates possible, thus making it much more powerful. E.g.:

```
// Run function returns (string, error)
{{with .Run}}
{{if .}}
        no error case with error=zero or error value with error=errorvalue
        run is {{.}}
{{else}}
       error case, . is empty string on option `error=zero`
{{end}}
{{end}}
```
Thanks!