sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Get the Device Camera Supported resolution list
Labels: c: new feature,p: camera,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
- We want to compare the image resolution with camera supported resolution list.

## Proposal

- There should be a class that defines media formats and capture settings that capture devices support.
Repository: PowerToys
Issue: Settings process hangs indefinitely after editing any color setting
Labels: Issue-Bug,Product-Settings,Priority-1

### Microsoft PowerToys version

main

### Running as admin

- [ ] Yes

### Area(s) with issue?

Settings

### Steps to reproduce

1. open settings
2. go to Find my mouse / Screen Ruler settings page
3. edit any color setting
4. close settings window


### ✔️ Expected Behavior

PowerToys.Settings process exits properly

### ❌ Actual Behavior

PowerToys.Settings.exe process hangs and you can't open settings from the tray anymore.

### Other Software

_No response_
Repository: deno
Issue: Add an API for fast HTML escaping
Labels: suggestion

In various benchmarks that @littledivy and @billywhizz did we see that escaping HTML that a huge chunk of time in React SSR examples. 

It's clearly a bottleneck that could be addressed by having a dedicated API for escaping HTML (probably as an op implemented in Rust). 

This should allow us to top various React SSR benchmarks.
Repository: axios
Issue: axios.create does not keep interceptors
Labels: state::triage

#### Describe the bug

If you create an axios instance from an existing axios instance, it will keep its `config` parameter, **but not its interceptors**

#### To Reproduce

In the code below we are going to create `axios2` from `axios1` that has custom `config` and intertceptors:
```js
import '../environment.test.js';
import axios from 'axios';
import HttpRequestMock from 'http-request-mock';

const BASE_URL = 'https://demo.com';
const httpRequestMock = HttpRequestMock.setup();

describe('Axios', () => {
  it('Axios create test', async () => {
    const axios1 = axios.create({
      headers: {
        test1: 'value1',
      },
    });

    // Interceptors
    axios1.interceptors.request.use(config => {
      console.log('axios1.interceptors.request');
      return config;
    }, error => Promise.reject(error));
    axios1.interceptors.response.use(response => {
      console.log('axios1.interceptors.response');
      return response;
    }, error => Promise.reject(error));

    httpRequestMock.mock({
      url: `${BASE_URL}/axios1`,
      method: 'get',
      status: 200,
      body: request => {
        console.log(`axios1 request.headers: ${JSON.stringify(request.headers)}`);
        return {};
      },
    });
    await axios1.get(`${BASE_URL}/axios1`);

    // Create axios2 from axios1
    const axios2 = axios1.create({
      headers: {
        test2: 'value2',
      },
    });
    httpRequestMock.mock({
      url: `${BASE_URL}/axios2`,
      method: 'get',
      status: 200,
      body: request => {
        console.log(`axios2 request.headers: ${JSON.stringify(request.headers)}`);
        return {};
      },
    });
    await axios2.get(`${BASE_URL}/axios2`);
  });
});
```

#### Expected behavior

Result:
```
axios1.interceptors.request
axios1 request.headers: {"accept":"application/json, text/plain, */*","test1":"value1","user-agent":"axios/0.27.2"}
axios1.interceptors.response
axios2 request.headers: {"accept":"application/json, text/plain, */*","test1":"value1","test2":"value2","user-agent":"axios/0.27.2"}
```
=> As you can see, `axios2` prints `"test1":"value1"` from `axios1`, but doesn't have `axios1`'s interceptors

Expected:
```
axios1.interceptors.request
axios1 request.headers: {"accept":"application/json, text/plain, */*","test1":"value1","user-agent":"axios/0.27.2"}
axios1.interceptors.response
axios1.interceptors.request
axios2 request.headers: {"accept":"application/json, text/plain, */*","test1":"value1","test2":"value2","user-agent":"axios/0.27.2"}
axios1.interceptors.response
```


#### Environment

 - Axios Version: 0.27.2
 - Node.js Version: v16.17.0
 - OS: Ubuntu 20.04 LTS
Repository: pytorch
Issue: Install LibTorch by Conan or other C++ package manager
Labels: module: cpp,triaged,topic: binaries

### 🚀 The feature, motivation and pitch

At present, There is no detailed guide for how to install LibTorch or construct the environment. The official tutorial does not show where should I put the downloaded library, or how to write a correct `CMakeList.txt` file.

### Alternatives

I find out that there are some good C++ package managers like [Conan](https://conan.io). It is kind of like `pip` and `conda` for Python. It would be easier to install and use LibTorch if we can access it by a C++ package manager, say [Conan](https://conan.io).

### Additional context

_No response_

cc @jbschlosser
Repository: rust
Issue: Constructing a simple HashSet<char> requires RandomState type annotation
Labels: A-diagnostics,T-compiler,D-confusing

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
pub fn is_pangram(sentence: &str) -> bool {
    let mut letters = std::collections::HashSet::from_iter("abcdefghijklmnopqrstuvwxyz".chars());
    sentence.to_lowercase().chars().any(|c| {
        letters.remove(&c);
        letters.is_empty()
    })
}
```

I expected to see this code to compile, just like this code does:
```rust
pub fn is_pangram_bytes(sentence: &str) -> bool {
    let mut letters = std::collections::HashSet::from(*b"abcdefghijklmnopqrstuvwxyz");
    sentence.to_lowercase().bytes().any(|c| {
        letters.remove(&c);
        letters.is_empty()
    })
}
```

Instead, this happened:

```
error[[E0282]](https://doc.rust-lang.org/nightly/error-index.html#E0282): type annotations needed for `HashSet<char, S>`
 --> src/lib.rs:3:9
  |
3 |     let mut letters = std::collections::HashSet::from_iter("abcdefghijklmnopqrstuvwxyz".chars());
  |         ^^^^^^^^^^^
  |
help: consider giving `letters` an explicit type, where the type for type parameter `S` is specified
  |
3 |     let mut letters: HashSet<char, S> = std::collections::HashSet::from_iter("abcdefghijklmnopqrstuvwxyz".chars());
  |                    ++++++++++++++++++
```

I can fix it by including a type annotation for the RandomState:
```rust
pub fn is_pangram_with_randomstate_annotation(sentence: &str) -> bool {
    let mut letters: std::collections::HashSet<_, std::collections::hash_map::RandomState> =
        std::collections::HashSet::from_iter("abcdefghijklmnopqrstuvwxyz".chars());
    sentence.to_lowercase().chars().any(|c| {
        letters.remove(&c);
        letters.is_empty()
    })
}
```

But since
```rust
pub struct HashSet<T, S = RandomState>
```
I do not think I should need to do this.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
1.63.0 up to nightly 2022-08-31 9243168fa5615ec8ebe9 (tested on playground)
```
Repository: vscode
Issue: `DebugService` has high cost
Labels: debt,perf-startup

* Profile startup/reload (w/ simple text editor, just the explorer visible)
* Drill into code editor creation
* Notice that ~30% its creation time is spend in the `CallStackEditorContribution` contribution

That itself is cheap but it "force creates" the delay/lazy debug service which causes a ripple of events and other things. It would be better if we can keep this lazy and depend on the service to soon

<img width="580" alt="Screenshot 2022-09-02 at 12 55 10" src="https://user-images.githubusercontent.com/1794099/188124952-e439aa7a-9b94-49bf-8a91-baadc4131c74.png">
Repository: create-react-app
Issue: New Error of handleErrorFromBinding(ctx); 
Labels: needs triage,issue: bug report

node:fs:2490
      handleErrorFromBinding(ctx);
![image](https://user-images.githubusercontent.com/103554076/188129058-91260dac-8884-4989-a115-c560cf9284a2.png)
Repository: TypeScript
Issue: Unexpected assignability
Labels: Bug

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
I have created a [question](https://stackoverflow.com/questions/73580368/why-doesnt-typescript-complain-about-an-incorrect-return-type) on stackoverflow and several people (with me) came to conclusion that it imight be a bug.

### 🕗 Version & Regression Information
Version 4.7.4

It might be regression . Because there was an error in  [3.5.1](https://tsplay.dev/WzeBkm) and there is no error in [3.6.2/3.6.3](https://tsplay.dev/mx3zxN)
<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This changed between versions 3.5.1 and 3.6.2 or 3.6.3

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://tsplay.dev/wQxLJW)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type Item = {
    id?: number
}

export type ResultType =
    {                           //
        list: Item[];       // -------> comment these lines and you will get an error. Using this intersection somehow blinds TS compiler
    }                           //
    & {
        list: Item[];
    }


let a = {
    list: ['a']
};

let result: ResultType = a;

```
As per my understanding, there should be an error, because `a` is not assignable to `ResultType`, however there is no error. Further more, if you remove one `{list: Item[]}` from intersection , TS will throw an error. THis behaviour is strange and I am unable to understand/explain it.
### 🙁 Actual behavior

No assignability error when there are two equal literal types are intersected

### 🙂 Expected behavior

Should be an error
Repository: flutter
Issue: Add allItemsCached property and change implementation in CachingIterable
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

Recently I tried to use CachingIterable. But it doesn't have some features. 
I can't check is all items was cached or not. Yes, we can use it foreach cycle, but, sometimes, we need access by `elementAt` , but we can't check its index by `length`, because `length` property will force to compute all sequence. That won't be lazy iterable. 
CachingIterable has List under hood, but it doesn't override `void elementAt(int i)` from Iterable. So this method has complexity O(N), but can have O(1).
## Use case
I have tried to implement ListView which can work with iterables, but this implementation can work only with infinite sequence. https://gist.github.com/webnickell/14e7dddc154aee2a76690e0cee017c8a
I would rewrite build method in this way

```dart
@override
Widget? build(BuildContext context, int index) {
  final item = iterable.allItemsCached
      ? iterable.length >= index
          ? null
          : iterable.elementAt(index)
      : iterable.elementAt(index);
  return Text('$item');
}
```


## Proposal

Add this implementation for elementAt
```dart
CachingIterable(this._prefillIterator);

final Iterator<E> _prefillIterator;
final List<E> _results = <E>[];

@override
E elementAt(int index) => _results[index]; 
```
And change implementation for this method
```dart
bool _allItemsCached = false;

bool get allItemsCached => _allItemsCached;

bool _fillNext() {
  if (!_prefillIterator.moveNext()) {
    _allItemsCached = true;
    return false;
  }
  _results.add(_prefillIterator.current);
  return true;
}

```
Repository: godot
Issue: MultiplayerSpawner isn't working
Labels: needs testing,topic:network

### Godot version

4.0 dev

### System information

AMD on Fedora

### Issue description

Hello,
I used a networking tutorial to try to implement networking for my game. And the synchronizer works just fine but I cannot get the multiplayer spawner to do anything at all. Would you be willing to take a look at what I am doing wrong in my game? No one on IRC seems particularly knowledgeable about the MultiplayerSpawner since I get crickets when I ask about how it works.
If you could also type up an explanation of how it works programatically that would be enlightening; but I am grateful for any help you can spare.
Here is the link to my project:
https://code.bkeys.org/Game_Projects/zombie-shooter
The tutorial and example project seem to work just fine and I have modeled the networking exactly as it does in the example and tutorial. It seems the Spawner doesn't work outside of 2D worlds.

### Steps to reproduce

Clone my repo, run a server using --headless --server and a client, it should auto connect. The player never spawns and I have code that prints out the tree to show this.

### Minimal reproduction project

https://code.bkeys.org/Game_Projects/zombie-shooter
Repository: godot
Issue: Input.get_vector() does not process EventActions from TouchScreenButton 
Labels: bug,topic:input

### Godot version

3.5 stable, 3.5.1 rc1

### System information

MacBook Pro m1, Big sur 11.4, gles3

### Issue description

Hello! Input.get_vector("ui_left", "ui_right", "ui_up", "ui_down") function reacts to keyboard input, but does not reacts to TouchScreenButton's assigned actions. I tried the same in Godot 4.0 and it worked fine there. It looks like a bug in Godot 3.
I have checked that actions were emitted with using following code:
if Input.is_action_pressed("ui_up"):
       print("got an action")
Text was printed after pushing the TouchScreenButton.

### Steps to reproduce

1.Create a root Node2D.
2.Add KinematicBody.
3.Create a CanvasLayer with TouchScreenButtons and add instance to the root node.
2.Add script to KinematicBody:

extends KinematicBody2D

onready var input_direct: Vector2 = Vector2()
export var speed: float = 100.0


func _physics_process(delta):
	input_direct = Input.get_vector("ui_left", "ui_right", "ui_up", "ui_down")
	input_direct = input_direct.normalized()
	self.move_and_slide(input_direct*speed)

### Minimal reproduction project

[BugTouchScreenButton.zip](https://github.com/godotengine/godot/files/9479510/BugTouchScreenButton.zip)
Repository: flutter
Issue: macos platform channels can't distinguish `nil` and empty data
Labels: engine,a: desktop,P3,team-macos,triaged-macos

The following platform channel integration tests fail on macos:
- https://github.com/flutter/flutter/blob/f57fcac717092e9d55d25a63d79505b455719609/dev/integration_tests/channels/lib/main.dart#L113:L113
- https://github.com/flutter/flutter/blob/f57fcac717092e9d55d25a63d79505b455719609/dev/integration_tests/channels/lib/main.dart#L117:L117

I spent some time debugging it and it ended up being a bit of an investment tracking down all the places we throw away the distinction between `nil` and empty data.

cc @cbracken @stuartmorgan
Repository: next.js
Issue: Nextjs with jest example will not work if there is an esm dependency in node_modules
Labels: bug

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Fri Apr 2 22:23:49 UTC 2021
    Binaries:
      Node: 16.16.0
      npm: 8.11.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 12.2.5
      eslint-config-next: 12.2.5
      react: 18.2.0
      react-dom: 18.2.0

### Which example does this report relate to?

https://nextjs.org/docs/testing

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

_No response_

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

_No response_

### Describe the Bug

If you have a project with a dependency that is published as an es modules in node_modules, running jest will not work..even though nextjs works with it e.g. running the project normally with npm run dev.

Test does not run even if ignoring the package. Please check this repo that reproduce the problem:

https://github.com/wmira/banana/

if you run npm run dev here..works fine.. npm run test here does not and this follow the jest example.


### Expected Behavior

running test via jest works as per the docs

### To Reproduce


repo is below:
https://github.com/wmira/banana/

1. npm run dev -- nextjs works fine with an es module dependency under node_modules
2. npm run test -- throws error
Repository: rust
Issue: unused_crate_dependencies false positives for dev-dependencies added for Doctests
Labels: A-lints,T-compiler,C-bug,A-doctests,A-crates

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```toml
[dev-dependencies]
once_cell = "1.14"
```
```rust
/// ```rust
/// use once_cell::sync::Lazy;
/// ```
fn foo() {}
```

I expected to see this happen: *No warning since once_cell is used in the Doctest*

Instead, this happened: *The warning is still emitted*

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.62.1 (e092d0b6b 2022-07-16)
binary: rustc
commit-hash: e092d0b6b43f2de967af0887873151bb1c0b18d3
commit-date: 2022-07-16
host: aarch64-apple-darwin
release: 1.62.1
LLVM version: 14.0.5
```
Repository: TypeScript
Issue: referencesCodeLens count is wrong
Labels: Needs Investigation,Domain: Symbol Navigation,Rescheduled

<!-- ⚠️⚠️ 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

<!-- 🪓 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.71.0 
- OS Version: Darwin x64 21.5.0

wrong_referencesCodeLens.ts file: https://gist.github.com/Southhill/a89406054990d1ae86fcebf7124d125f

Steps to Reproduce:

1. setting: "typescript.referencesCodeLens.enabled": true
2. open wrong_referencesCodeLens.ts
3. expect class `A` method `destroy` only 1 references but 6 references
Repository: TypeScript
Issue: If a tsc command is not able to run because there is no tsconfig.json file give the user some sort of hint about that
Labels: Suggestion,Help Wanted,Experience Enhancement

# Suggestion

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 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:
-->

tsconfig.json

## ✅ 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.)
* [?] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

Here's what I did: 

```
✗ cat package.json | grep type
    "typecheck": "tsc --noEmit",
    "typescript": "~4.8.2",

✗ npx which tsc
/Users/justin.collum2@nutrien.com/work/recommendations-dp/node_modules/.bin/tsc

✗ yarn typecheck
```

Result: I get the help text, which implies that I used an invalid CLI flag. But the CLI flag I used is in the help text! So it was very confusing. 

Then I realized that this is a monorepo and it doesn't have a root tsconfig file: 

```
✗ ls -alh | grep tsconfig

✗
```

I suspect that's the issue. 

<!-- A summary of what you'd like to see added or changed -->

If `tsc` can't proceed because there is no config file that it is able to find, say so. Don't emit the help text, emit an error like "Can't proceed, no config file found, search paths: ..." 

Just getting the CLI help text was very misleading. 

## 📃 Motivating Example

<!--
  If you were announcing this feature in a blog post, what's a short explanation that shows
  a developer why this feature improves the language?
-->

## 💻 Use Cases

<!--
  What do you want to use this for?
  What shortcomings exist with current approaches?
  What workarounds are you using in the meantime?
-->