sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: rewriteRelativeImportExtensions & enforce consistent extensions
Labels: Suggestion,In Discussion

### 🔍 Search Terms

"rewriteRelativeImportExtensions", "extensions"

### ✅ Viability Checklist

- [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 isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

An option/param to enforce `import`s with relative paths to point to files existing in sources rather than in built files, in short, make `import`s only allowing `.ts` and not `.js` extensions when importing a Typescript file.

### 📃 Motivating Example

`rewriteRelativeImportExtensions` is a great new feature and it works well. It permits to create hybrid projects directly executed by recent nodejs versions, but also buildable by tsc for distributing them. But since we now have the possibility to use the `.ts` extensions in `import`s because they will be rewritten at compilation time, we still can continue to use the `.js` extensions in parallel, pointing to built files.
As everyone knows, nodejs requires relative `import`s to have an extension and to point to an existing file and so, extensions have to be `.ts` (or `.mts`/`.cts`) to import other Typescript files.
It would be probably great that Typescript gives us an error when using unreachable file in this context, like its quasi-exact opposite: `TS5097: An import path can only end with a .ts extension when allowImportingTsExtensions is enabled` when `.ts` extensions are not allowed by configs.


### 💻 Use Cases

1. What do you want to use this for?
In projects where nodejs can be used for any reason (tests, various scripts) and where code have to be built to be distributed over npm or any other repository, to avoid detecting bad `import`s extensions at nodejs runtime and to keep a consistent code base.

2. What shortcomings exist with current approaches?
Only its permittivity, allowing to use inconsistent `import`s styles, that may don't run in nodejs, without detecting them at coding time.

3. What workarounds are you using in the meantime?
It's not a bug, there's no need of workarounds, only vigilance.
Repository: pytorch
Issue: [EXPORT AOTI] `aoti_compile_and_package` custom_ops dependecies
Labels: oncall: pt2,export-triaged,oncall: export

### 🐛 Describe the bug

I was trying to `export` and `aoti_compile_and_package` a model with this custom op:
https://github.com/state-spaces/mamba/pull/651

`aoti_load_package` is working correctly on the same export env. 
But it is not going to work in a fresh env when I don't have the custom ops dependency installed (e.g. `selective_scan_cuda.cpython-311-x86_64-linux-gnu.so`).
 In this case  we have  `Error during testing: Could not find schema for custom_ops::selective_scan_fwd`

Is this cause the custom_op `.so` isn't included in the packaged  `aoti_compile_and_package`?

If yes, Is it an expected behavior by design?

/cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 @zou3519 

### Versions

nightly
Repository: angular
Issue: `HttpFeature` only accepts type `Provider` as providers
Labels: feature,area: common/http

### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

No

### Description

Since `HttpFeature` providers passed to `provideHttpClient()` are being type cast to `EnvironmentProviders`, is there a reason why they only accept `Provider[]` and not `(Provider | EnvironmentProvider)[]` ?

```ts
export interface HttpFeature<KindT extends HttpFeatureKind> {
  ɵkind: KindT;
  ɵproviders: Provider[]; // <-- why does this not accept `EnvironmentProvider`?
}
```

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_
Repository: vscode
Issue: [wsl] bring back "Reopen Folder in WSL" to the remote menu
Labels: feature-request,WSL

<!-- ⚠️⚠️ 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. -->


Whoever did this, you probably inconvenienced millions of people. Good one.
Repository: flutter
Issue: Create benchmarking app for flutter. It should have minimal assets, ios only, (optional) with endless scrolling.
Labels: platform-ios,f: scrolling,team: benchmark,team-ios
Repository: flutter
Issue: Create equivalent app for SwiftUI.
Labels: platform-ios,team: benchmark,team-ios
Repository: flutter
Issue: Time to first frame
Labels: platform-ios,c: rendering,perf: speed,team: benchmark,team-ios
Repository: flutter
Issue: Scrolling
Labels: platform-ios,f: scrolling,team: benchmark,team-ios
Repository: rust
Issue: `f16` creates doc-link ambiguity on stable
Labels: T-rustdoc,C-bug,A-intra-doc-links

I `cargo doc`ed this code:

```rust
#[allow(non_camel_case_types)]
pub struct f16 {}

/// Blah blah blah [`f16`]
pub fn foo() -> f16 {
    f16 {}
}
```

I got:

```
warning: `f16` is both a struct and a primitive type
 --> src/lib.rs:4:22
  |
4 | /// Blah blah blah [`f16`]
  |                      ^^^ ambiguous link
  |
  = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default
help: to link to the struct, prefix with `struct@`
  |
4 | /// Blah blah blah [`struct@f16`]
  |                      +++++++
help: to link to the primitive type, prefix with `prim@`
  |
4 | /// Blah blah blah [`prim@f16`]
```

and the link was missing in the generated documentation. Instead, because `f16` is unstable, it should have no effect and there should be no warning.

Additionally, even when `f16` is stable, the link should not be considered ambiguous since primitive `f16` is being shadowed. (Otherwise, currently valid code will get broken links when `f16` stabilizes.)

### Meta

`rustc --version --verbose`:
```
rustc 1.86.0-nightly (ed43cbcb8 2025-01-21)
binary: rustc
commit-hash: ed43cbcb882e7c06870abdd9305dc1f17eb9bab9
commit-date: 2025-01-21
host: aarch64-apple-darwin
release: 1.86.0-nightly
LLVM version: 19.1.7
```

Also occurs on stable 1.84.
Repository: TypeScript
Issue: TypeScript 5.8 Iteration Plan
Labels: Planning

This document outlines our focused tasks for TypeScript 5.8. It minimally indicates intent to investigate tasks or contribute to an implementation. Nothing is set in stone, but we will strive to complete these tasks in a reasonable timeframe.

Date           | Event
---------------|-------------------------
2024-11-22     | TypeScript 5.7 Release
2025-01-24     | Create 5.8 Beta (5.8.0) Build for Testing
2025-01-28     | **TypeScript 5.8 Beta Release**
2025-02-07     | Create 5.8 RC (5.8.1) Build for Testing
2025-02-11     | **TypeScript 5.8 RC Release**
2025-02-21     | Create 5.8 Final (5.8.2) Build for Testing
2025-02-25     | **TypeScript 5.8 Final Release** 🚀

```mermaid
gantt
    dateFormat  YYYY-MM-DD
    TypeScript 5.7 Stabilization Period : 2024-11-18, 2024-11-22
    TypeScript 5.8 Beta Development : 2024-11-18, 2025-01-24
    TypeScript 5.8 RC Development : 2025-01-25, 2025-02-07
    TypeScript 5.8 Stabilization Period : 2025-02-08, 2025-06-21
todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5
```

# Compiler and Language

* [Checked Return Statements for Conditional and Indexed Access Types](https://github.com/microsoft/TypeScript/pull/56941)
* [`--module node18`](https://github.com/microsoft/TypeScript/pull/60722) and [`--module node20`](https://github.com/microsoft/TypeScript/pull/60761)
* [`--erasableSyntaxOnly` Option](https://github.com/microsoft/TypeScript/issues/59601)
* [Investigate Preserving Computed Properties with Entity Names for Declaration Emit](https://github.com/microsoft/TypeScript/pull/60052)
* [Introduce `--libReplacement`](https://github.com/microsoft/TypeScript/pull/60829)
* [`lib.d.ts` Updates](https://github.com/microsoft/TypeScript/issues/60985)

# Editor and Language Service

* [Iterate on Expandable Hovers](https://github.com/microsoft/TypeScript/pull/59940)

# Performance

* [Normalize Paths with Fewer Allocations](https://github.com/microsoft/TypeScript/pull/60812)
* [Skip `tsconfig.json` Checks on Program Updates](https://github.com/microsoft/TypeScript/pull/60754)

# Website and Docs

* [Simplify and Refactor Website for Faster Builds](https://github.com/microsoft/TypeScript-Website/issues/2730)
Repository: kubernetes
Issue: Add conversion function to translate between `corev1.LabelSelector` and apimachinery `labels.Selector`
Labels: sig/api-machinery,kind/feature,needs-triage

### What would you like to be added?

While writing k8s controllers, I have found a need to translate between the K8s API model type `LabelSelector` and the API Machinery `labels.Selector` type. While searching online has yielded a [stack overflow issue](https://stackoverflow.com/questions/77870908/convert-kubernetes-labels-selector-to-metav1-labelselector) which recommends translating to a string and parsing said string, it would be beneficial for the community to have a method which handles this translation. 

### Why is this needed?

String serialization/de-serialization has the potential to fail silently if the logic behind the serialization changes which is why having a method to handle this would be better.
Repository: storybook
Issue: [Bug]: Storybook v8.5 First Test Fails on Cypress
Labels: question / support,compatibility with other tools

### Describe the bug

When running Storybook v8.5 with Cypress for end-to-end (E2E) tests, the first test always fails, irrespective of the test content. Subsequent tests execute and pass as expected. The failure occurs because the Storybook server does not appear to be running for the first test, displaying a white screen. However, the server is loaded for the second test onward.

### Reproduction link

N/A

### Reproduction steps

1. Use the following nx script for running E2E tests:

```
"targets": {
    "e2e": {
      "executor": "nx:run-commands",
      "options": {
        "command": "start-server-and-test 'nx run shared-react-design-system:storybook' http-get://localhost:4400  'nx run shared-react-design-system-e2e:e2e:cypress'"
      }
    },
    "e2e:cypress": {
      "executor": "@nx/cypress:cypress",
      "options": {
        "cypressConfig": "libs/shared/react/design-system-e2e/cypress.config.ts",
        "testingType": "e2e"
      },
      "configurations": {
        "ci": {
          "devServerTarget": "shared-react-design-system:storybook:ci"
        }
      }
    }
  }
```

2. Run the e2e target.
3a. The first test fails, displaying a white screen when running from localhost on port 4400. 
3b. Logged errors:
` CypressError: `cy.visit()` failed trying to load:`
`We attempted to make an http request to this URL but the request failed without a response.`
` Error: ESOCKETTIMEDOUT`
4. The subsequent tests complete successfully.

### System

```bash
macOS: "15.0.1"
nx: "20.2.2"
cypress: "13.17.0"
```

### Additional context

This still occurs when the first test is removed and the next available test is bumped up to run first.

Updating just the storybook package to v8.5 is fine, this issues occurs when updating the storybook addon packages to:

```
   "@storybook/addon-a11y": "8.5.0",
    "@storybook/addon-essentials": "8.5.0",
    "@storybook/core-server": "8.5.0",
    "@storybook/nextjs": "8.5.0",
    "@storybook/react": "8.5.0",
```
Repository: flutter
Issue: [Impeller] Re-enable PowerVR GPU support.
Labels: P3,e: impeller,team-engine,triaged-engine

Most of the remaining severe crashes or rendering issues on Vulkan Impeller are specific to certain PowerVR GPUs. For example, we have flickering when rendering on the Google TV streamer, or a complete black screen on an Oppo-Something. Both are 9000 series (though I don't have a fully understanding of how the model numbers work yet).

For now we've disabled PowerVR. This issue tracks figuring out:

1. Are the sets or subsets of PowerVR GPU / Drivers that work OK?
2. Are there reasonable workarounds we can do to make them work?
3. Are there existing known issues we can use to bootstrap this discovery process.
Repository: flutter
Issue: [pigeon]pigeon documentation is missing task queue usage
Labels: package,team-ecosystem,p: pigeon,P3,triaged-ecosystem

### Use case

I'm trying to understand how pigeon's task queue works. It looks like there's no such example in both https://github.com/flutter/packages/tree/main/packages/pigeon and https://github.com/flutter/packages/blob/main/packages/pigeon/example/README.md



### Proposal

A example usage of TaskQueue API would be helpful for me to understand
Repository: go
Issue: x/build: run platform/arch specific builders when platform/arch constrained files are changed
Labels: Builders,NeedsInvestigation

When making changes to platform or arch constrained files (.go/.s) it would be nice for LUCI to automatically include builders of those types in the set that is run. Currently this has to be done manually, which is not always particularly obvious, and can lead to changes appearing to pass builders when they would fail in the specific builders were included.

This doesn't seem to be easily done with location filters regexps in the luci main.star, since we want to be more specific when there is a platform suffix (e.g. if `example_linux_amd64.go` changes, we only want to run the linux-amd64 builder), and less specific when there is only an arch suffix (e.g. if `example_amd64.go` changes, we want to run all of the amd64 builders). I fiddled around with this and couldn't find an obvious way to accomplish it.

One possible option is to add a special mode to golangbuild which scans the file names changed in a CL, and does this matching itself, spawning an additional set of builders.

Ideally we'd also do this for build constrained files which use the `//go:build` syntax, but this seems a lot more complex, as it's not particularly easy to extract this information via the gerrit API (as far as I can tell). For a first pass, it'd probably be fine to just do the file name based approach, since that covers the majority of use cases.

cc @golang/release
Repository: PowerToys
Issue: Please add folder comparison function
Labels: Needs-Triage

### Description of the new feature / enhancement

Compare two folders, such as the number of files inside, whether each file has a corresponding file in another file, MD5 verification, etc.

### Scenario when this would be used?

Development!!!

### Supporting information

_No response_
Repository: pytorch
Issue: torch.compile has different numerics for var_mean
Labels: oncall: pt2,module: inductor

### 🐛 Describe the bug

```
import torch
from torch._dynamo.utils import same

def foo(x):
    return torch.ops.aten.var_mean.correction(x, [1], correction = 0, keepdim = True)

inp = torch.rand([112958, 384], device="cuda", dtype=torch.float16)
print(same(foo(inp), torch.compile(foo)(inp)))
```

> [ERROR]:Accuracy failed: allclose not within tol=0.0001


Maybe this is a numerics sensitive op, but it throws up bisecting and is a general pain. 

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov @ezyang 

### Versions

master
Repository: PowerToys
Issue: Key swap sticky issue
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.81.0

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

this bug happens when I _**switched on Keyboard Manager and replaced the CapsLock to CTRL and vice versa.**_

I am an architect who deal with rhino for most of the time, the bug occurs when PowerToys is on for a while (after startup from reboot) and rhino is on for a while. The duration is uncertain, can be minutes, hours or days depending on the heavyness of the rhino model. 

_**The symptom is the replaced CTRL key would became sticky, behavior like a CapsLock key but function as a CTRL key.**_

### ✔️ Expected Behavior

No misfunction between desired key and changed key.

### ❌ Actual Behavior

CTRL key replacing over CapsLock will act like a CapsLock key but with CTRL key functions. 
(i.e., unintentional multiselection in Windows Explorer, unintentional viewtype orientation in certain software)

### Other Software

Rhino 8
Repository: ollama
Issue: I should not have to write the full model name
Labels: feature request

If I want to run mistral, and mistral is the only model I have starting with an "m", i should just have to type "ollama run m"
if theres something called "mestral", then i can type "ollama run mi", and so on
Repository: rust
Issue: `extern` symbols are always mangled on `wasm32-unknown-emscripten`
Labels: T-compiler,C-bug,O-emscripten,A-name-mangling

Attempting to compile a program with `EMCC_CFLAGS="-s ERROR_ON_UNDEFINED_SYMBOLS=0" cargo build --target wasm32-unknown-emscripten --release` results in all `extern` functions having unpredictable names, whether or not they have `#[no_mangle]`.

I tried this code:

```rust
extern "C" {
    fn foo() -> f64;
}

fn main() {
    println!("{}", unsafe { foo() });
}
```

I expected to see this happen: A generated `.js` loader with a stub in `wasmImports["foo"]`.

Instead, this happened: The js loader renames the function to a practically random symbol. In this case:

```js
function _foo() {
    abort("missing function: foo")
}
_foo.stub = true;
var wasmImports = {
    // .. more
    y: _foo,
    // .. more
};
```

### Meta
Tested against 1.83.0 and latest nightly.

`rustc --version --verbose`:
```
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: aarch64-apple-darwin
release: 1.83.0
LLVM version: 19.1.1
```
Repository: godot
Issue: Wrong window height in project conversion dialogue
Labels: bug,topic:editor,regression

### Tested versions

reproducible in version 4.4 beta 1
not reproducible in version 4.3 stable

### System information

Windows 11 (build 26100) - Multi-window, 2 monitors

### Issue description

When converting an old Godot project from version 3 to version 4.4 beta 1, there is bug, where the height of the window displaying the conversion dialogue is too high, so the window controls extend beyond the screens dimensions. This happens on a 4K monitor, on full hd resolution this bug does not appear.

<img width="432" alt="Image" src="https://github.com/user-attachments/assets/95ea56ae-5afb-4b07-adb3-3113573af8ec" />

On Godot version 4.3 stable, the window is much greater in height, but its height is still reasonable, so that the control elements can be used.

<img width="437" alt="Image" src="https://github.com/user-attachments/assets/e880feff-a359-453c-844e-20f525db8a5a" />

### Steps to reproduce

Import the example project and follow the dialogues until the conversion dialogue appears.
This must be done on a 4K monitor.

### Minimal reproduction project (MRP)

[ExampleProject.zip](https://github.com/user-attachments/files/18511407/ExampleProject.zip)
Repository: langchain
Issue: ChatPerplexity does not implement `bind_tools` for structured output
Labels: Ɑ:  models

### Checked other resources

- [x] I added a very descriptive title to this issue.
- [x] I searched the LangChain documentation with the integrated search.
- [x] I used the GitHub search to find a similar question and didn't find it.
- [x] I am sure that this is a bug in LangChain rather than my code.
- [x] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

```
ChatPerplexity(
    temperature=0,
    model="llama-3.1-sonar-huge-128k-online",
    pplx_api_key=config.perplexity_key,
).with_structured_output(schema=OutputSchema)
```

returns a Not Implemented Error

### Error Message and Stack Trace (if applicable)

```
backend-glen_ai-1  |   File "/usr/local/lib/python3.9/site-packages/langchain_core/language_models/chat_models.py", line 1242, in with_structured_output
backend-glen_ai-1  |     llm = self.bind_tools([schema], tool_choice="any")
backend-glen_ai-1  |   File "/usr/local/lib/python3.9/site-packages/langchain_core/language_models/chat_models.py", line 1119, in bind_tools
backend-glen_ai-1  |     raise NotImplementedError
backend-glen_ai-1  | NotImplementedError
```

### Description

* Documentation says `with_structured_output` is supported (https://python.langchain.com/api_reference/community/chat_models/langchain_community.chat_models.perplexity.ChatPerplexity.html#langchain_community.chat_models.perplexity.ChatPerplexity.with_structured_output)
* Perplexity has structured output support (https://docs.perplexity.ai/guides/structured-outputs)

### System Info

langchain-community = "^0.3.15"
langchain = "^0.3.15"
Repository: bitcoin
Issue: `DEFAULT_TRANSACTION_MAXFEE` is 0.1 ₿
Labels: Brainstorming,Wallet,TX fees and policy

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

I was reviewing a pull request, when I noticed that the `DEFAULT_TRANSACTION_MAXFEE` is set to 0.1×COIN.

`src/wallet/wallet.h:constexpr CAmount DEFAULT_TRANSACTION_MAXFEE{COIN / 10};`

### Describe the solution you'd like

 It seems to me that given the current exchange rate we might want to lower that by about a magnitude.
Repository: flutter
Issue: [Impeller] Playground and golden generator generate different images
Labels: engine,P3,e: impeller,team-engine,triaged-engine

### Steps to reproduce

When I generate goldens for some Impeller playground tests they are scaled differently than they are in playground and as a result their content can be clipped. This is on MacOS.

For example, try running a golden output for `Play/AiksTest.MaskBlurVariantTestOuterTranslucent/Metal` and compare it to its playground view. The playground view looks correct, but the golden output is scaled larger than what I see in playground and as a result some of the content is clipped.

I noticed this first when looking at some golden failures for this test on a PR. The local goldens didn't indicate any errors because the differences were in the clipped-out part in my local tests. So, it looks like the golden checks in PR pre-submits are fine as they don't exhibit this "scaling and clipping" issue, but it makes debugging those errors difficult locally because the problem happens locally on my MBP.

### Expected results

The output of the two mechanisms should match and the golden results should not be clipped.

### Actual results

The content looks correct in playground, but over-scaled and clipped in the locally produced golden images.

### Code sample

`impeller_unittests --gtest_filter="Play/AiksTest.MaskBlurVariantTestOuterTranslucent/Metal" --enable_playground`

vs

`impeller_golden_tests --gtest_filter="Play/AiksTest.MaskBlurVariantTestOuterTranslucent/Metal" --working_dir=<...>`

### Screenshots or Video

<details>
<summary>Playground image</summary>

<img width="1017" alt="Image" src="https://github.com/user-attachments/assets/2307891d-70a7-4683-ac98-f00a7942f26b" />
</details>

<details>
<summary>Golden image</summary>

![Image](https://github.com/user-attachments/assets/51acfd59-b2c5-4774-8c1e-b43c73cf2bb2)

</details>