sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Tags for properties contribution is missing from completion
Labels: feature-request,extensions-development

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.64.0
- OS Version: fedora 35

Steps to Reproduce:

1. open the package.json
2. provide a contributes -> properties ->> xxx
3. call completion, there is no "tags" provided

see https://github.com/microsoft/vscode/issues/140972#issuecomment-1016650114 where the `tags` is mentioned.

Note: there is neither no mention of this attribute in the documentation https://code.visualstudio.com/api/references/contribution-points#contributes.configuration
Repository: TypeScript
Issue: Assertion Functions cannot assert over private properties - unnecessary/wrong error message?
Labels: Suggestion,Domain: Error Messages,Awaiting More Feedback

Assertion Function  "Private identifiers are not allowed outside class bodies." 

# Bug Report


### 🔎 Search Terms

assertion function, asserts, #, private members, Private identifiers are not allowed outside class bodies.

### 🕗 Version & Regression Information

This happens in 4.0.5, 4.4.3, 4.5.4 and the latest nightlies - so probably in all TS versions that support assertion functions and private class members.

### ⏯ Playground Link

[A playground showcasing the problem](https://www.typescriptlang.org/play?ts=4.0.5#code/MYGwhgzhAEAqCmEAu0DeAoaXoGIBO8YAJgJ4Bc0ARgPbUiEB20AvNAGZggTwDc6m2HJG54kAJUKkAFAEoKw+KJhIAFgEsYGtAOzYA9HugAFPGoBuYJPGhqi8BkjVs1imGALQG1FJxDUA7vBE0NQArkgQttagwlTURC4QAHRSAIwAHAAMqQBsMjq6uATE5NBIeKHWBmXqmjD+1HgA1moMAObQAA6KbPDASCAk7K3WqmFtKklTBQC+2oXYTtBSqhpJ+JIkMvMLhap4AZ7w-tAAongHeFIARF4oxaTX+bvQM7P8ulbIsjsL1QACEQAtPAAB7dfogi6NGpaRSXNwwMEQqxEAq6YDUBjIMqpCjlSosWHJDYldHYVYkhSiCQlWTkrDVMAMYKU6ANZqI6DIvqohnQTHYlBIABM+Iq1lYlPWDxI7xmQA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
class Test {
    #ready: boolean = false;

    #assertReady(): asserts this is {
        // Private identifiers are not allowed outside class bodies.(18016)
        #ready: true // this is working perfectly fine though...
    } {
        if (this.#ready) {
            throw new Error("not ready")
        }
    }
}
```

### 🙁 Actual behavior

The code above works 100% as expected (the assertion function also narrows the type of `this.#ready` down to `true` correctly), but TS displays an error message:

> Private identifiers are not allowed outside class bodies.(18016)

### 🙂 Expected behavior

The error message should be removed - this seems to work absolutely fine as it is. The error message seems to be a red herring.
Repository: PowerToys
Issue: Custom commanding for explorer style integrations for per interaction customization
Labels: Idea-Enhancement,Product-PowerToys Run

### Description of the new feature / enhancement

Currently, the containing folder of a file/an app or the folder itself that's been found in the PT Run list can only be opened in the standard system file explorer. One should also be able to open the file/folder in a third-party file manager such as [double commander](https://doublecmd.sourceforge.io/).  In other words, this button's behavior can be customized: 

![image](https://user-images.githubusercontent.com/32868278/152811797-6c9f6614-a5ae-4610-94b7-b11d1c2d342f.png)


### Scenario when this would be used?

This is helpful for users who use double commander/total commander to manage files.

### Supporting information

_No response_
Repository: youtube-dl
Issue: [media.un.org] New site support
Labels: site-support-request

This site uses kaltura, but it is not recognized by youtube-dl. Could it be added? Thank you!

$youtube-dl -v https://media.un.org/en/asset/k1r/k1r3vy9ikk
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://media.un.org/en/asset/k1r/k1r3vy9ikk']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.8.5 (CPython) - Linux-5.15.0-3-amd64-x86_64-with-glibc2.10
[debug] exe versions: avconv 4.4.1, avprobe 4.4.1, ffmpeg 4.4.1, ffprobe 4.4.1, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] k1r3vy9ikk: Requesting header
WARNING: Falling back on generic information extractor.
[generic] k1r3vy9ikk: Downloading webpage
[generic] k1r3vy9ikk: Extracting information
ERROR: Unsupported URL: https://media.un.org/en/asset/k1r/k1r3vy9ikk
Traceback (most recent call last):
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "./youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "./youtube-dl/youtube_dl/extractor/generic.py", line 3489, in _real_extract
    raise UnsupportedError(url)
youtube_dl.utils.UnsupportedError: Unsupported URL: https://media.un.org/en/asset/k1r/k1r3vy9ikk
Repository: go
Issue: cmd/go: eliminate test dependencies on cloud.google.com/go
Labels: Testing,NeedsFix,GoCommand

```
#!watchflakes
post <- pkg == "cmd/go" && log ~ `https://cloud\.google\.com/go.*: 5\d\d\b`
```

[CL 196961](https://go.dev/cl/196961) added a test that fetched a module from `cloud.google.com/go`.

Unfortunately, the rate of 5XX-series errors for fetches from that repo has increased substantially since around 2021-11-04, quite possibly due to the same underlying problem as #50541.

Since the `cloud.google.com` server isn't controlled by the Go project proper, we should probably eliminate this test dependency.
(CC @matloob)

`greplogs --dashboard -md -l -e 'https://cloud\.google\.com/go.*: 5\d\d\b'`

[2022-02-04T23:42:58-7c9885d/linux-386-longtest](https://build.golang.org/log/7f4bd01966181b82ae529790a5a9dc018cf6dd59)
[2022-01-25T00:39:08-16d6a52/linux-386-longtest](https://build.golang.org/log/e9f20e767f2093184d2c730e6b0086df8a6399c9)
[2022-01-20T19:24:26-2c2e081/linux-386-longtest](https://build.golang.org/log/4817f8416202d679733c88b235c161ccbe8d7817)
[2022-01-17T09:23:25-897b3da/linux-386-longtest](https://build.golang.org/log/90587bec8d75a1c90118b353450b428dac4c7980)
[2021-12-21T18:34:03-cfb0cc3/linux-amd64-longtest](https://build.golang.org/log/4f7bfcb2daec9d2353e57e377d481bf0a3ad229d)
[2021-12-20T23:46:23-1555062/linux-amd64-longtest](https://build.golang.org/log/3e2adf0adca25767baf8ed9d51565d80acbcc394)
[2021-11-16T06:36:08-a52e4b9/linux-386-longtest](https://build.golang.org/log/63cda198beb46c982152387352b6007989ad5a99)
[2021-11-13T02:30:25-c546052/linux-386-longtest](https://build.golang.org/log/358c29e07d441ec317f99de6db07237b5ee227b2)
[2021-11-04T17:07:48-5772877/linux-amd64-longtest](https://build.golang.org/log/017c5e7eb90d6c65ca8d34493bc3fd7698e9df8d)
[2021-11-04T16:59:45-6e7b82a/linux-386-longtest](https://build.golang.org/log/1faaccf234162b16651f913e5c64f0964bc98eae)
[2021-08-16T20:22:08-4466141/linux-386-longtest](https://build.golang.org/log/c319421c7af9c7f7902a884727b4e70ce3c7251f)
[2020-07-09T16:26:07-72735e7/linux-386-longtest](https://build.golang.org/log/c5d098af99b354a4fe2083a8a2e73a8e04105705)
Repository: create-react-app
Issue: Docs for importing Sass partials shows broken use of @use
Labels: needs triage,issue: bug report

### Describe the bug

When importing Sass partials one must use @import and not @use as [the docs](https://create-react-app.dev/docs/adding-a-sass-stylesheet) suggest.

### Did you try recovering your dependencies?

yes. npm version = 8.4.1

### Which terms did you search for in User Guide?

'use import sass partial'

### Environment

current version of create-react-app: 5.0.0
  running from /Users/alexkio/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

  System:
    OS: macOS 12.2
    CPU: (10) x64 Apple M1 Pro
  Binaries:
    Node: 14.16.0 - ~/.nvm/versions/node/v14.16.0/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.16.0/bin/yarn
    npm: 8.4.1 - ~/.nvm/versions/node/v14.16.0/bin/npm
  Browsers:
    Chrome: 98.0.4758.80
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.3
  npmPackages:
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    react-scripts: 5.0.0 => 5.0.0
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

1. npx create-react-app my-app
2. cd my-app
3. npm start
4. npm install sass
5. rename App.css to App.scss
5. create _variables.scss with `$grey-dark: #282c34;`
6. in App.scss `@use './_variables.scss';` and change `background-color: #282c34;` to `background-color: $grey-dark;`

### Expected behavior

npm start should load without errors

### Actual behavior

Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
SassError: Undefined variable.
   ╷
19 │   background-color: $grey-dark;

### Reproducible demo

[Project](https://github.com/alexmkio/react-css-practice/tree/use) that fails to build using npm start and @use as suggested in the [docs](https://create-react-app.dev/docs/adding-a-sass-stylesheet)

[Project](https://github.com/alexmkio/react-css-practice/tree/import) that builds using npm start and @import
Repository: yt-dlp
Issue: Support media.un.org
Labels: site-request,patch-available

### Checklist

- [X] I'm reporting a new site support request
- [X] I've verified that I'm running yt-dlp version **2022.02.04**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've checked that none of provided URLs [violate any copyrights](https://github.com/ytdl-org/youtube-dl#can-you-add-support-for-this-anime-video-site-or-site-which-shows-current-movies-for-free) or contain any [DRM](https://en.wikipedia.org/wiki/Digital_rights_management) to the best of my knowledge
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [X] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and am willing to share it if required

### Region

Worldwide

### Example URLs

https://media.un.org/en/asset/k1r/k1r3vy9ikk
https://media.un.org/en/asset/k1r/k1r5enfiwb

### Description

The site at media.un.org uses Kaltura, but yt-dlp doesn't recognize it and is unable to extract/construct the URL. This is the main UN Media Site containing recordings of UN meetings and events. Would be great to be able to download these recordings for offline viewing/listening. Thanks!


### Verbose log

```shell
[debug] Command-line config: ['--verbose', 'https://media.un.org/en/asset/k1r/k1r3vy9ikk']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, err utf-8, pref UTF-8
[debug] yt-dlp version 2022.02.04 [c1653e9ef]
[debug] Python version 3.9.10 (CPython 64bit) - Linux-5.15.0-3-amd64-x86_64-with-glibc2.33
[debug] exe versions: avconv 4.4.1, avprobe 4.4.1, ffmpeg 4.4.1 (setts,fdk), ffprobe 4.4.1, phantomjs 2.1.1, rtmpdump 2.4
[debug] Optional libraries: Cryptodome, secretstorage, mutagen, sqlite, websockets
[debug] Proxy map: {}
[debug] [generic] Extracting URL: https://media.un.org/en/asset/k1r/k1r3vy9ikk
[generic] k1r3vy9ikk: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] k1r3vy9ikk: Downloading webpage
[generic] k1r3vy9ikk: Extracting information
[debug] Looking for video embeds
ERROR: Unsupported URL: https://media.un.org/en/asset/k1r/k1r3vy9ikk
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/yt_dlp/YoutubeDL.py", line 1381, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/yt_dlp/YoutubeDL.py", line 1451, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3/dist-packages/yt_dlp/extractor/common.py", line 612, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3/dist-packages/yt_dlp/extractor/generic.py", line 3986, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://media.un.org/en/asset/k1r/k1r3vy9ikk
```
Repository: pytorch
Issue: ProcessGroupWrapper: Additional Improvements
Labels: oncall: distributed,better-engineering,module: c10d,module: ddp

### 🚀 The feature, motivation and pitch

Couple of additional improvements to ProcessGroupWrapper that will help debugging experience:

1. Attach sequence number in log output / collective mismatch error as in https://github.com/pytorch/pytorch/blob/master/torch/csrc/distributed/c10d/ProcessGroupWrapper.cpp#L92 to help debug the relative collective order across ranks.
2. Store and log the last N (maybe N = 10 or 50?) collectives executed when reporting a desync issue to provide additional context as to what sort of communication the application was doing and allow log comparison across ranks.
3. When reporting inconsistent collectives such as https://github.com/pytorch/pytorch/blob/master/torch/csrc/distributed/c10d/ProcessGroupWrapper.cpp#L92, on each rank, log the collectives the other rank was running that was deemed inconsistent. This will be useful as sometimes one rank crashes and brings all the others down so currently we don't always get the complete picture.

### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: go
Issue: x/benchmarks/sweet/cmd/sweet: timeout in TestSweetEndToEnd
Labels: NeedsInvestigation

`greplogs --dashboard -md -l -e 'panic: test timed out .*\n(?:\ngoroutine \d+ .*:\n(.+\n)*)*^golang\.org/x/benchmarks/sweet/cmd/sweet_test.TestSweetEndToEnd' --since=2022-01-01`

[2022-02-07T07:14:28-e4ea61d-334a591/linux-amd64-longtest](https://build.golang.org/log/f553f0951195b42f8c49d12787f7f403f1d0919b)

----

(attn @mknyszek)
Repository: rust
Issue: Tracking Issue for str::{floor, ceil}_char_boundary
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(round_char_boundary)]`

This is a tracking issue for `str::{floor, ceil}_char_boundary`.

<!--
Include a short description of the feature.
-->

### Public API

<!--
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.)
-->

```rust
impl str {
    // Returns the character boundary at or immediately before `index`
    fn floor_char_boundary(&self, index: usize) -> usize;

    // Returns the character boundary at or immediately after `index`
    fn ceil_char_boundary(&self, index: usize) -> usize;
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #86497
- [ ] Final comment period (FCP)
- [ ] 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 stabilzation 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 `ceil_char_boundary` panic when indices are out of bounds? #112387 is an existing PR to change this to return the length instead.
Repository: opencv
Issue: Deprecations and planned breaking changes for the Apple build pipeline should be resolved in 5.0
Labels: category: build/install,platform: ios/osx

Hi there! I saw that there's a milestone for 5.0, so I wanted to throw this on the pile if this is the proper way to do it.

In #18826, @chrisballinger and I retooled a lot of the build pipeline for Apple platforms. To recall, we created a new `apple` platform folder that builds XCFrameworks, which supports multiple Apple platforms. To do this, it uses the existing `ios` and `osx` platform folders to generate each platform's `.framework`s, and then stitches them together into a `.xcframework`. In making this new platform, we had to make some changes to `build_framework.py` in the `ios` and `osx` platform folders. Some of these changes are essentially deprecations that should be revisited in 5.0, when we get to make breaking changes.

These are the items that should be resolved:

* https://github.com/opencv/opencv/blob/08356007c952daf5db97beaec79419b8143dc5b6/platforms/ios/build_framework.py#L515-L516
* https://github.com/opencv/opencv/blob/08356007c952daf5db97beaec79419b8143dc5b6/platforms/osx/build_framework.py#L61-L62
* https://github.com/opencv/opencv/blob/08356007c952daf5db97beaec79419b8143dc5b6/platforms/osx/build_framework.py#L105-L106
* https://github.com/opencv/opencv/blob/08356007c952daf5db97beaec79419b8143dc5b6/platforms/osx/build_framework.py#L90-L94

---

Also noted in the PR:
> We'd also like to put in a PR to move the `ios` and `osx` build scripts and supporting files into the new `apple` platform directory, though this would be a breaking change for CI.

It's not strictly necessary to do this, but Apple recommends using XCFrameworks for everything going forward, even when you're targeting a single platform. Because of this, in my opinion, a user should be discouraged from building a `.framework` directly with the existing `ios` and `osx` `build_framework.py` scripts. To reflect this, I think it makes sense to move those scripts into the `apple` platform folder, as they would basically be intermediate steps for `build_xcframework.py`.

In concrete terms, this would mean:
* Moving `build_framework.py` and supporting files from the `ios` and `osx` platform folders into the `apple` platform folder
* Adjusting each platform's `build_framework.py` to indicate that you really should be using `build_xcframework.py` to generate an XCFramework

---

Thanks!
Repository: pytorch
Issue: Use Module `__getattr__` in `torch.ops` and friends
Labels: triaged,better-engineering

We currently do a trick in `torch._ops` which involves creating a module type and returning that when `torch.ops` is requested. This is so that we can customize `__getattr__` to perform lazy loading of operators.

Since Python 3.7, this behavior can be achieved by defining `__getattr__` directly on the Module (see: [PEP562](https://www.python.org/dev/peps/pep-0562/)). Doing it this way is simpler and uses Python's native functionality instead of our own thing. Since we have now [dropped support for Python 3.6](https://github.com/pytorch/pytorch/issues/66462), we should be able to use it.

@ezyang also mentioned `co` and `backends.cudnn` as other places where we do a similar trick.
Repository: pytorch
Issue: Memory parity with JAX attention
Labels: module: memory usage,triaged

Our attention module is essentially standard multi-head attention, just with arbitrarily many bias tensors. It’s approximately as follows:

```
a = torch.matmul(q, k)

for b in biases:
    a += b

a = softmax(a, dim=-1)

o = torch.matmul(a, v.transpose(-1, -2))
```

where `q`, `k`, and `v` are `[batch_dim, heads, Q/K/V, C]` query, key, and value tensors, respectively, and `biases` is a list of bias tensors (e.g. a mask), all of which broadcast along at least one dimension such that their sizes are insignificant (they’re much smaller than the full `[batch_dim, heads, Q, K]` attention logit matrix `a`, in any case). During training, since `batch_dim`, `Q` and `K` are >> `C`, memory consumption is dominated by the first matrix multiplication and the softmax, which together contribute (`2 * batch_dim * heads * Q * K * (2 bytes)`) to the module total. Equivalent JAX code requires just (`batch_dim * heads * Q * K * (2 bytes)`), half as much.

torch doesn’t have anything like an in-place softmax, and for various reasons I’ve been unable to shrink the memory requirements using keops (apparently incompatible with the bias tensors) or by manually building an in-place softmax myself (breaks auto-differentiation).

Is there a (`batch_dim * heads * Q * K * (2 bytes)`) solution in torch?

cc @jbschlosser @bhosmer @cpuhrsch
Repository: transformers
Issue: DeepMind Retro
Labels: New model

# 🌟 New model addition

Basically a retrieval augmented model like RAG, but without expensive retriever end2end training



## Open source status

* [ ] the model implementation is available: Not available 
* [ ] the model weights are available:  Not available 
* [ ] who are the authors:(https://arxiv.org/pdf/2112.04426.pdf)