sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Workspace Trust - Live Share guest session flow with restricted workspaces
Labels: polish,under-discussion,workspace-trust

Version: 1.57.0-insider (user setup)
Commit: 4f3d865a6b46a4ead49cf83fe1c30d95d0a34220
Date: 2021-05-31T05:14:38.041Z

Start a Collaboration Session on another computer
On your machine have Live Share installed and try to join the session.

a open an new empty window. 
b Live share `Join Session` can not be found  as it requires workspace trust.
c. Trust the empty workspace. The  `Join Session` is still not available as Live Share is still disabled, no explanation
d. reload the window makes the window untrusted again (also reported in https://github.com/microsoft/vscode/issues/124824)
e. open a trusted window to get the Live Share commands
f. Join the session
g. new window opens, with root rendered red. 
![image](https://user-images.githubusercontent.com/6461412/120179049-6a12a380-c20a-11eb-9da8-7e1efda8f9dd.png)

- The banner is very subtle here. It took me while to understand why the root node in the explorer is red
- I'm forced to trust the workspace

Looks like Live Share has not yet adopted the `untrustedWorkspaces` capability.
Repository: TypeScript
Issue: [Compiler API] Reuse default compiler host when customizing module resolution
Labels: Suggestion,Awaiting More Feedback

# Suggestion

A very similar question already has been asked here four years ago by @vivin:
[Implementing custom module-resolution logic using Compiler API - StackOverflow](https://stackoverflow.com/questions/46304944/implementing-custom-module-resolution-logic-using-compiler-api)

I need the same right now, and it is a pity that apparently, you still need to rewrite the entire compiler host configuration just in order to customize one aspect. What I would prefer to do would be something like:

```ts
const host = ts.createCompilerHost(options);
host.resolveModuleNames = myResolver;
const program = ts.createProgram(sourceFiles, options, host);
```

But this still seems to be impossible right now?

## 🔍 Search Terms

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

customize module resolution, configure compiler host, `resolveModuleNames`

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## 💻 Use Cases

- customize compiler more easily without reinventing the wheel
- if you need to reinvent the wheel, the code will get harder to maintain against future changes to the default compiler host
Repository: TypeScript
Issue: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type
Labels: Needs Investigation,Rescheduled

# Bug Report

The following code used to work on 4.2.3, but does not build with 4.3.2, reporting the error on the last line

```ts
type ObjectFixedKeys<T extends object> = {
    [K in keyof T]: string extends K ? never : K
} extends { [_ in keyof T]: infer U }
    ? U
    : never

type DistributeKeysUnion<U> = U extends string
    ? { [K in U]: any }
    : never

type ObjectDictionaryKeys<T extends object> = Exclude<
    T,
    DistributeKeysUnion<ObjectFixedKeys<T>>
    >

type Condition = { $and: Array<Condition> }
    | { $or: Array<Condition> }
    | { [member: string]: string }

type O = ObjectFixedKeys<Condition>
type D = DistributeKeysUnion<ObjectFixedKeys<Condition>>

declare const s: string
type CT = ObjectDictionaryKeys<Condition>
declare const ct : CT
const h = ct[s]
```

Error:

```
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'CT'.
  No index signature with a parameter of type 'string' was found on type 'CT'.
```

### 🕗 Version & Regression Information

I tracked the regression to the version 4.3.0-dev.20210422

Probably related to https://github.com/microsoft/TypeScript/commit/8ea4ec94967c9db8542ca229dedd656fe9e051df

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.4.0-dev.20210531#code/C4TwDgpgBA8gRgKwgY2AMQJYA8IBMDSEIAzgDwAqUEWwEAdrsVAPaIrAB8UAvFAN4AoKMKgBtfFAx0oAayLMAZlHIBdAFxRiwAE5SA5lRr1GUCQH4odCADcI2qBvwCAvodoMmfMQH1J0uSCKyup+CnZQAKpQzkIiFhGxwhpWttoCAqCQUAAiGFq6cACutIQkEXQYzHSkEVy8UdTuJvn6iVAWXuJ+kSEAhnQg0W3JNnbpmdDwSKi5qJV0vdogpWSUjcZMrNOcPFAAoljIADaFuBCkbeQANG25LUUlRMTl86RT7Jg4BE8UHBxt-wy4GgAGEqrgMMB5rsvAASfq4DQAQW02l6IFIYIYkPmXBiIigAB9+FBYcxtMjUejMeCcVU8W1iZ0ALYQZlwOwaFp0PQhbkGGICM7HRbQZBVLSaLk6VoTKAgyi8d4zDBzKqLZY-LEQqH08bA2C7ZXobB4FY07G6uj-OXZXZ3GUPCArF5VN5sVCfM1a2lWv7pYVHUVQcV0SWoBzy8gCUOSgAWu1QomIKn1WRWAHVIXHmMUAMoynkASQY1F+PDanQkUlk8iUqmluh5bg2pnallG9kc0RbHhJol8NYCQQboXCUXxcUiww7qTT0Fokt4mezueABabehLZywpE6Uh3jf0fMLegA3FAFMxmEeeRe4IsNAByB8ALyf0Q4QA)

Note how the last line is evaluated to `never`, however if you select version 4.2.3 it gets evaluated to `"foo" | "bar"` as expected.
Repository: terminal
Issue: [FEATURE] Ability (option) to change Acrylic Background Source
Labels: Area-UserInterface,Area-Settings,Product-Terminal,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->
Ability to change `AcrylicBrush.BackgroundSource`. It will be really useful when someone wants to set an image background and enable Acrylic *over* the image (instead  of the app background), and hence make a great feature! I personally love AcrylicBrush and have some images that suit acrylic really well, but can't use the Terminal acrylic on those background images since the BackgroundSource is different (`AcrylicBrush.BackgroundSource.HostBackdrop`, I believe). Adding an option in the settings to change the said background source of the acrylic brush (to lay it over the background image and not the app background/desktop) would be a gamechanger (at least in my humble opinion).  
  
# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
An ability to toggle(?) `AcrylicBrush.BackgroundSource` between `AcrylicBrush.BackgroundSource.Backdrop` and `AcrylicBrush.BackgroundSource.HostBackdrop` (if I remember the valid options/choices correctly) through the Terminal settings.  
Just a normal setting (maybe in the `Appearance` tab?) should be enough. Just two `RadioButtons` or a `ComboBox` to choose an acrylic background source. And of course, an `"acrylicBackgroundSource"` property whose possible values are `"backdrop"` and `"hostBackdrop"` (or whatever values you want here, whichever may be more understandable).  
  
Please let me know if you want more details for a better understanding. I'm ready to explain.
  
Thank you!
Repository: go
Issue: pthread_create crash: gofuzz, cgo, asan, go 1.16
Labels: NeedsInvestigation

As per
https://github.com/google/oss-fuzz/issues/5442

Some Go fuzzer programs (configured with whatever oss-fuzz does to combine Go with the address sanitizer) are crashing with:

```
Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
pthread_create
_cgo_try_pthread_create
pthread_create
```

The actual Go code under test does not spawn its own goroutines, although it does involve asm code which IIUC is similar to cgo:
https://github.com/google/oss-fuzz/blob/master/projects/go-snappy/fuzz.go
https://github.com/golang/snappy/blob/master/decode.go
https://github.com/golang/snappy/blob/master/decode_amd64.s

Another comment in that 5442 issue says:

> This bug happens for every golang project since go 1.16
> I think it happened as well in go 1.15 but only for fuzz targets running multiple goroutines

So perhaps the asm thing is unrelated??

Any suggestions on what to try next?

---

Also posted to https://groups.google.com/g/golang-dev/c/3DrZWztdaX0 but there's not much discussion there.
Repository: ant-design
Issue: Typography element inside Layout.Header|Layout.Sider with default less|css is unreadable.
Labels: Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-bl9r6)

### Steps to reproduce
* Import 'antd/dist/antd.css'
* Import Layout (Header, Sider, Content, Footer) and Typography (Title, Text)
* Add a Title or Text element to a Header or Sider

### What is expected?
Readable text

### What is actually happening?
Unreadable text

| Environment | Info |
|---|---|
| antd | 4.16.1 |
| React | 17.0.2 |
| System | Ubuntu 20.04 |
| Browser | Firefox 88.0.1 |

---
I'd suggest something like the example below for pretty much all components, with `@text-color` replaced with appropriate variables in special components (ie info|warning|error components). Any user-defined styles would still override them, but antd would still push a decent experience OOB.
```less
color: if(boolean(luma($background) > 50%)  and boolean(luma(@text-color) < 25%), @text-color, contrast($background));
```
> Note: Pretty new to less (and antd), which is why I'm not doing a pull request or anything. Might have missed something in the docs while trying to figure this out the past few days through simple css overrides and even by customizing the theme.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Clarify BLAS configuration option
Labels: module: build,module: docs,triaged,module: linear algebra

## 📚 Documentation

Currently the `BLAS` configuration option is documented as
> BLAS to be used by Caffe2. Can be MKL, Eigen, ATLAS, or OpenBLAS If set then the build will fail if the requested BLAS is not found, otherwise the BLAS will be chosen based on what is found on your system.

This is a bit confusing due to `Eigen` being part of that list. But there are multiple issues with that:

- Instead of "the build will fail" a default BLAS will be chosen (if nothing or "MKL" was selected) via some (AFAIK) undocumented procedure.
- Choosing "Eigen" will show `Preferred BLAS (Eigen) cannot be found, now searching for a general BLAS
  library` which is confusing: Eigen is part of the pytorch repo/submodules and hence is always found. In fact no attempt is made to locate it
- So choosing "Eigen" will still pick a BLAS library. It is unclear (and currently impossible) to choose which one
- It is unclear what the benefit of choosing Eigen + *BLAS is over just choosing a BLAS lib

It would be great, if this was clarified.

Maybe related: https://github.com/pytorch/pytorch/issues/32407#issuecomment-622580552 which hints that maybe using Eigen could be dropped as a BLAS lib is always required.

cc @malfet @seemethere @walterddr @brianjo @mruberry
Repository: go
Issue: x/website: go-talks.appspot.com present server still relies on defunct RawGit service
Labels: NeedsInvestigation,website

One can (and [the likes of Dave Cheney do](https://dave.cheney.net/2016/12/03/simulating-minicomputers-on-microcontrollers)) point `talks.godoc.org` to one's `present` slideshow hosted on GitHub. The slideshow then runs on the server, which obviates the need for installing and running the `present` command on one's local machine. For instance, see https://talks.godoc.org/github.com/jub0bs/poc_present/main.slide.

However, I noticed that SVG assets hosted `raw.githubusercontent.com` see their URL's host rewritten to `rawgithub.com`. https://rawgithub.com permanently redirects to https://rawgit.com, which states that the RawGit project is reaching the end of its life:

> RawGit is now in a sunset phase and will soon shut down. It's been a fun five years, but all things must end. [...] If you're currently using RawGit, please stop using it as soon as you can.

(my emphasis)

As a result of this URL rewrite and the RawGit project's status, such SVG assets fail to load (with a `403` response status) in `present` slides run on `talks.godoc.org`; for instance, see https://talks.godoc.org/github.com/jub0bs/poc_present/main.slide#2:

<img width="908" alt="failure to load SVG in slideshow" src="https://user-images.githubusercontent.com/52325150/120204257-e4eab700-c228-11eb-9436-f5beb2db9509.png">

Note: a WHOIS lookup confirms that `godoc.org` is owned by Google; `talks.godoc.org` is maintained by @dmitshur.

I tracked down [the offending URL rewrite](https://github.com/golang/gddo/blob/20d68f94ee1f7547de2b1c68627253df20c8d45e/gosrc/github.go#L245) to [the `golang/gddo` project](https://github.com/golang/gddo), but that project is marked as _archived_ and no longer accepts issues or pull requests. I privately reached out to @julieqiu for guidance on Gophers Slack, who suggested I open an issue about this here.

Relying on RawGit despite its sunset status may have security implications: when RawGit becomes truly defunct, its domain names may be acquired by a malevolent actor who could serve arbitrary SVGs in place of the slideshow's authors'. I've privately reached out to [Ryan Grove](https://twitter.com/yaypie) (RawGit's author) on Twitter, who indicated he has no plans to let domain names `rawgithub.com` and `rawgit.com` lapse any time soon, but his plans may change, especially if the cost of ownership becomes prohibitive.

Moreover, the ability to run a slideshow on https://talks.godoc.org is valuable to the community, and isn't yet (AFAIK) supported on https://pkg.go.dev. Fixing this issue (by no longer relying on RawGit) would be a good thing.
Repository: rust
Issue: `no_hash` queries bypass `-Z verify-ich` checks
Labels: T-compiler,A-incr-comp,A-query-system

[It was recently shown](https://blog.rust-lang.org/2021/05/10/Rust-1.52.1.html) that "incremental compilation hash verification" (i.e. `-Z verify-ich`) is an important tool for finding potentially dangerous bugs in query provider implementations. 

However, this verification of query result hashes naturally can only work if we actually compute hashes for the results of a given query. This is not the case for queries marked with the [`no_hash` attribute](https://rustc-dev-guide.rust-lang.org/queries/incremental-compilation-in-detail.html#query-modifiers). As a consequence, for such queries, an indeterministic query provider implementation cannot be detected by the measures we recently put in place.

There are two reasons for making a query `no_hash`:
- Performance: hashing some query results is a waste of time because 
  1. it is highly unlikely that a re-computed query can turn green or 
  2. the result of the query is effectively hashed a second time via cheap "projection queries".
- Necessity: The result of the query does not have a `HashStable` implementation and thus cannot be hashed.

There is also some good news here: if a query is marked as `eval_always` in addition to `no_hash` we don't have to worry about the kind of inconsistency bug that caused us to make the 1.52.1 point release because in that case there's always a single source of truth for the value of a query result. These also seem to be the kinds of queries that fall into the "necessity" category.

However, there still might be queries that are `no_hash` but not `eval_always`. There's usual a good (performance-related) reason for marking them as such. The question is: how can we make them still be checked by `-Zverify-ich`?

(@rust-lang/wg-incr-comp, @Aaron1011, or @cjgillot, please double check my thinking here, especially whether the combination of `eval_always` and `no_hash` is indeed safe)

cc https://github.com/rust-lang/rust/issues/85783
Repository: create-react-app
Issue: Add support for node 16 (current release) and scss
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

I start using node 16. My dependency `node-scss` require update to 6 version. When update this dependency and try build my app i have error: 

```
Node Sass version 6.0.0 is incompatible with ^4.0.0 || ^5.0.0.
```

### Describe the solution you'd like

We must update sass-loader to 10.2.0 version :) 
https://github.com/webpack-contrib/sass-loader/releases

### Describe alternatives you've considered

Try configure SCSS in CRA without `node-scss` because this package is deprecated : 

> Warning: LibSass and Node Sass are deprecated. While they will continue to receive maintenance releases indefinitely, there are no plans to add additional features or compatibility with any new CSS or Sass features. Projects that still use it should move onto Dart Sass.

https://www.npmjs.com/package/node-sass
Repository: go
Issue: proposal: syscall/js: allow passing a slice of bytes directly to JavaScript
Labels: Performance,Proposal,OS-JS

In the same way that you can pass a pointer to an element of a byte slice to a function via CGo without copying it, assuming the function you're calling doesn't hold on to the pointer after it returns, it should be possible to call JavaScript functions with a `Uint8Array` that points directly to Go memory.

This could be used to make calls to functions like [WebGLRenderingContext.bufferData](https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/bufferData) more efficient, as the data wouldn't need to be copied twice (once from Go to JavaScript and then again by the browser).

The same caveats as passing a `*byte` to CGo would apply: if the function you're calling holds on to the pointer after it returns, the pointer will probably eventually point to something else.
Repository: flutter
Issue: Unify Google login APIs
Labels: p: google_sign_in,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Intro

Currently there 3 different APIs to implement a user login using Google, with different functionality:

| Package(s) | API Abstraction Level | Platforms | Web API vs Rest API | Web Login UI | Native UI | Can use Google APIs |
|------------|-----------------------|-----------|---------------------|--------------|-----------|----------------------|
| `googleapis_auth` | medium/low        | all platforms | Different client code | Only popup | No          | Yes                              |
| `google_sign_in` w/ extension | high | mobile and web | Same client code | Only popup | Yes         | Yes (sort of)               |
| `firebase_auth` w/ `google_sign_in` | medium/high | mobile, web, macOS | Different client code | Popup and Redirect | Yes | No |

Each with different benefits, but it's impossible to combine them to get the best experience and all the functionality. Also having 3 APIs not only adds to the confusion, it makes people not having a clear guide as of what API should I use for each case.

## Use case

While implementing a flutter app to run on all platforms (including web), use a single API, with a medium/high level of abstraction, that allows me to implement a user login using Google credentials, then gives me access to the logged in user access/refresh token that can be used to call other Google APIs.

## Proposal

1. Offer a unified API for login with a user account from Google, with support for the most appropriate experience on each platform (native integration in android, redirect on web).
2. Clearly state the user case that each of the packages that implement login with Google credentials is supposed to address.

## Notes

From the 3 existing packages, `google_sign_in` seems the most appropriate (and closest to offer everything). It's simple to use and offers the same API for both web and native platforms. The `extension_google_sign_in_as_googleapis_auth` package is the bridge to `googleapis` although it seems there are multiple limitations currently (client does not auto refresh token?). My biggest pain is this package does not support the redirect flow, as popups are (IMHO) not considered a nice UX nowadays. (see https://github.com/flutter/flutter/issues/64457)

I can only get the redirect flow with `firebase_auth`, but although this package depends on `google_sign_in` for login in native platforms, it requires a different code for the web (no matter what UI you chose). And in web flow there is no way to get the tokens required to use google APIs.

The `googleapis_auth` package can be used to login anywhere, but being a dart only package, at least in Android it does not show the native UI (as does `google_sign_in`) and surprisingly also does not support web redirect. Finally, its harder to configure if I want to use different client config for web/desktop/mobile as does `google_sign_in`.
Repository: storybook
Issue: Controls addon date Control Type bug
Labels: bug,good first issue,addon: controls,needs triage

**Describe the bug**
Controls addon - date Control Type select month and type 11 by using keyboard, it automatically updated month to 12.  - this happened on March 31st and May 31st and It might happen again on July 31st, Aug 31st when the day is on 31st.  

**To Reproduce**
Create date Control Type on storybook 
`value: { control: "date" },`
change the system date to May 31st or March 31st and using keyboard to type on the month field part. month 11 will automatically change to 12. 

**System**
Storybook version:
  6.1.14
storybook/react: 
  v6.1.14
react version:
  17.0.1
Platform: 
  win32 x64

**Additional context**
![DatePickerControl](https://user-images.githubusercontent.com/85127600/120232812-55420a00-c222-11eb-8bb1-6484f9aaf94f.png)
Repository: material-ui
Issue: [List] Combine selected with aria-selected property in ListItem
Labels: new feature,component: list

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

If the consumer of the `ListItem` component uses the `selected` property, it should provide the same value to the `aria-selected` property.

## Examples 🌈

Instead of:

```jsx
<ListItem selected={true} aria-selected={true} />
```

you can use:

```jsx
<ListItem selected={true} />
```

and have the component set the `aria-selected` property.