sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Add a `@visibleForTesting` way to override commonly modified template values in apps created by tests (such as AGP version)
Labels: c: new feature,c: proposal,P2,team-android,triaged-android,fyi-infra

We have a lot of integration tests with hardcoded versions of files that get output from `flutter create` or `flutter create <template>`.

Ex (but there are more):
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/integration.shard/test_data/deferred_components_project.dart
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/integration.shard/test_data/plugin_project.dart
https://github.com/flutter/flutter/blob/master/dev/devicelab/lib/framework/dependency_smoke_test_task_definition.dart

These test won't accurately test the state of our current templates if the templates change. Perhaps we could refactor the flutter tool to expose something like [`_overwriteFromTemplate`](https://github.com/flutter/flutter/blob/87abed2b23ea3c71855eafb3e616da8121a6ea27/packages/flutter_tools/lib/src/project.dart#L787) at a `@visibleForTesting` level for the purposes of integration tests? So that we aren't relying on the specific text content of the gradle build files, but rather just on the versions that we are intending to overwrite.

This functionality is not a feature to lower the maintenance effort it is a feature that will increase the fidelity of our testing that ensures a broad range of AGP/Gradle/Kotlin values continue to work and not regress.
Repository: react
Issue: [DevTools Bug]: Cannot view source with remote sourcemap containing absolute `sources`
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

www.airbnb.com

### Repro steps

1. Visit www.airbnb.com
2. Use component inspector to inspect a React component
3. Attempt to jump to source and observe that it fails

You won't be able to repro this since the sourcemaps aren't publicly accessible, but hopefully my issue description below explains the matter clearly:

Our sourcemaps contain no `sourceRoot`, but the `sources` are absolute paths (e.g `/foo/bar/baz/main.js`). The sourcemaps are uploaded to a domain `sourcemaps.d.musta.ch` and our minified JS files contain `sourceMappingURL=https://sourcemaps.d.musta.ch/foo/bar/baz.js.map` comments pointing to them. 

Per the [spec](https://sourcemaps.info/spec.html#h.75yo6yoyk7x5):
> Resolving Sources
If the sources are not absolute URLs after prepending of the “sourceRoot”, the sources are resolved relative to the SourceMap (like resolving script src in a html document).

Chrome follows the spec. `/foo/bar/baz/main.js` is an absolute *filesystem path*, but it is not an absolute `URL` - it would need to be something like `file:///foo/bar/baz/main.js` to be an absolute URL. Therefore, Chrome resolves the path relative to the sourcemap, resulting in `https://sourcemaps.d.musta.ch/foo/bar/baz/main.js`. This is the path that shows up in the Sources tab. 

However, the React code here does not follow the spec:
https://github.com/facebook/react/blob/8e60bacd08215bd23f0bf05dde407cd133885aa1/packages/react-devtools-shared/src/symbolicateSource.js#L101

As a result, the sourceURL remains `/foo/bar/baz/main.js`. The "View Source" functionality is broken since that doesn't point to a valid path. 

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: TypeScript
Issue: Design Meeting Notes, 8/13/2024
Labels: Design Notes


# Ordering Parameter Properties and Class Fields

https://github.com/microsoft/TypeScript/issues/45995

* When we adjusted our class field emit (with `useDefineForClassFields`), we also adjusted the relative ordering of class fields and parameter properties.
* Under JS, class fields run before the body of the constructor.
* Under TS, previously, class fields ran *after* parameter properties, but before the body of the constructor.
* Under `useDefineForClassFields` we error on any access to parameter properties, but otherwise it's fine.
* Should we adjust the ordering to be consistent?
* `useDefineForClassFields` was introduced as a legacy behavior to avoid breaks, why break people?
    * Could deprecate setting it to false.
* We could run a PR where it always errors, see what breaks.
    * Is there an argument for making things more spec-compliant over time?
* Is there something clever we could do with emit?
    * Witnessable side-effects.
* The tough part is that most codebases that would be affected by running on GitHub won't be uncovered. Typically these are more mature codebases.
* Could always do a codemod. We typically rely on quick fixes here.

  ```ts
  // Before
  class A {
      x = 1;
      constructor(public y: number) {
          console.log(this.y);
      }
  }
  ```

  ```ts
  // After
  class A {
      declare x;
      constructor(public y: number) {
          this.x = 1;
          console.log(this.y);
      }
  }
  ```
* Some of us feel like it's a good idea to get consistent emit. Picking a date in the future to deprecate and eventually remove is the proposed plan. But need to experiment first.
* Maybe 6.0 deprecation is the plan.
* This has only been available since ES2022 though!
* 6.0 deprecation = 6.5 removal, which is just over 2 years from now.
* Aside: we should investigate parameter properties in ECMAScript.
Repository: node
Issue: Re-order Node.js `src` directory 🥷
Labels: feature request,lib / src

### What is the problem this feature will solve?

## Hi Team 👋

Lately, I've been delving into the Node.js source code quite extensively. 
This has been both to gather ideas for future improvements and to understand how specific features work under the hood.

One thing that came to mind is the current organization of the source files, specifically the C++ files that define the Node.js runtime functions.


## Proposed Improvement

I believe it would be much better if we could organize the files instead of leaving them all in the root of the `src` directory. 🙏

Think of it as the "breaking the monolith" process. 
Our goal is to create a well-organized codebase, complete with a clear dependencies graph, while ensuring it remains fully backward-compatible (we are not Python) 🎉


I'd be happy to take on this task, if that sounds like a good idea. 
I understand that many people are currently working on features, so I suggest we handle this step by step. 

### Mitigation Strategy
We can migrate small groups of related files together, ensuring that the corresponding `h` and `c` files are kept together.


*Before I proceed with showing anything, I'd appreciate knowing your thoughts on this 🤞*

### Side Note
I believe the structure shouldn't be too complex—ideally, no more than two levels deep. This way, we can avoid having files scattered everywhere.

### What is the feature you are proposing to solve the problem?

-

### What alternatives have you considered?

_No response_
Repository: vscode
Issue: Esc closes the attach picker and doesn't go back to quick chat
Labels: bug,quick-chat

ref https://github.com/microsoft/vscode/pull/225538

Steps to Reproduce:

1. Open quick chat 
2. Hit paperclip
3. Hit ESC
4. 🐛 The Quick Chat is not displayed
Repository: vscode
Issue: Allow Shift+Tab to focus on first attachment in Quick Chat
Labels: feature-request,quick-chat

ref https://github.com/microsoft/vscode/pull/225538

Steps to Reproduce:

1. Open Quick Chat
2. Click paperclip
3. pick an item
4. :bug: shift+tab goes somewhere random in the UI (in panel chat it goes to the `x` on the attached item

This is due to tab index. The attachments no longer being on top of the input causes this behavior. We should consider having a Shift+Tab keybinding that goes to the attachment section to maintain similar behavior between Quick Chat and Panel.

As a workaround, you can TAB TAB TAB TAB to it.

cc @joyceerhl
Repository: vscode
Issue: [html] Relative links don't work with <base> element 
Labels: bug,html


Type: <b>Bug</b>

1.  Make a file structure like this
- index.html
- images
  - skibidi.jpg
2. Make HTML code like this
```
<head>
  <base href="images/">
</head>
<body>
  <img src="skibidi.jpg>
</body>
```
When you open the HTML page, the image will load from images/skibidi.jpg
But, when you click on the link within VS Code, it just takes you just to skibidi.jpg instead of images/skibidi.jpg
(keep in mind if you're the one fixing this that you can have a reverse href like ../../)

VS Code version: Code 1.92.1 (eaa41d57266683296de7d118f574d0c2652e1fc4, 2024-08-07T20:16:39.455Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (6 x 2904)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.93GB (10.27GB free)|
|Process Argv|--crash-reporter-id eadc9fd3-1184-4a7b-9972-faeaaebf8100|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
impr_priority:31102340
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-c:31111717
wkspc-ranged-c:31111712

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: [Inductor] Remove dead code from triton kernels
Labels: triaged,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

Inductor generates triton code for numels and range trees regardless of whether it's going to be used. Block pointers often don't use this code. For example, see the kernels in the description of https://github.com/pytorch/pytorch/pull/132937.

Numels are generated here: https://github.com/pytorch/pytorch/blob/main/torch/_inductor/codegen/triton.py#L2701

Masks are generated here: https://github.com/pytorch/pytorch/blob/main/torch/_inductor/codegen/triton.py#L2888

This is not a performance issue, as the triton compiler eliminates dead code. However, it does make the code a bit harder to read and debug.

We may want to remove this code if it turns out not to be used later in the kernel. However, this could also increase the complexity of the system. This feature is probably only a good idea if the solution is simple, robust and relatively easy to maintain. One option would be to search the generated code for occurrences of `"xmask"` to tell whether `xmask` needs to be computed.

See more discussion here: https://github.com/pytorch/pytorch/pull/132937#issuecomment-2276616208

### Alternatives

Do nothing, as the code is still valid and will ultimately be ignored by the triton compiler.

### Additional context

To run some tests with block pointers, try the command `TORCH_COMPILE_DEBUG=1 TORCH_LOGS=+inductor python test/inductor/test_torchinductor_strided_blocks.py ` from the root of your `pytorch` clone. 

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: create-react-app
Issue: I am so angry i just cant take it
Labels: needs triage

I just cant take it. The way they did away with errors and warnings in the console.
Making the dev experience worse and worse.
And now that CRA is dead how the hell do you get warnings back to the console in Vite???? 😤

Lord Help
Repository: tensorflow
Issue: The average should not be computed in L2Pool2d
Labels: type:bug,comp:lite

The [ONNX L2Pool2d](https://github.com/onnx/onnx/blob/main/docs/Operators.md#lppool), [DirectML L2 Pooling Desc](https://docs.microsoft.com/en-us/windows/win32/api/directml/ns-directml-dml_lp_pooling_operator_desc) and [CoreML's l2_pool2d](https://apple.github.io/coremltools/source/coremltools.converters.mil.mil.ops.defs.html#coremltools.converters.mil.mil.ops.defs.iOS15.pool.l2_pool) calculate the l2 pooling by the expression `Y = (X1^2 + X2^2 + ... + Xn^2) ^ (1/2)`,  but [TFLite L2_PooL2d kernel implementation](https://source.chromium.org/chromium/chromium/src/+/main:third_party/tflite/src/tensorflow/lite/kernels/internal/optimized/optimized_ops.h;l=3341?q=src%2Ftensorflow%2Flite%2Fkernels%2Finternal%2Foptimized%2Foptimized_ops.h) has the average with the count of sum elements  `Y=((X1^2 + X2^2 + ... + Xn^2)/n) ^ (1/2)`,  is it an issue of the kernel implementation?

BTW, [the kernel of l2_norm](https://source.chromium.org/chromium/chromium/src/+/main:third_party/tflite/src/tensorflow/lite/kernels/internal/optimized/optimized_ops.h;l=1424?q=L2Normalization&ss=chromium%2Fchromium%2Fsrc) also has no the average.
Repository: flutter
Issue: Improvements for animation APIs
Labels: framework,a: animation,c: API break,perf: speed,P3,c: tech-debt,team-framework,triaged-framework

I'm creating this issue to cover a couple of things from #24722:

> - [ ] Instead of one `AnimationController`, have one for each type of controller (bounded, unbounded, simulation, repeating, etc).
> - [ ] `ImplicitlyAnimatedWidget` and its subclasses should be named consistently.

<br>

Here are my thoughts:
- If we can improve performance by doing less work each frame, we probably should.
- If we can improve performance _and_ make an API more simple/easy to read, then it's a no-brainer.
Repository: deno
Issue: Release GitHub Copilot extension for Deno
Labels: suggestion,needs discussion

Deno is a rapidly growing JavaScript/TypeScript runtime with a huge and thriving ecosystem. Having a dedicated [GitHub Copilot extension](https://github.com/marketplace?type=apps&copilot_app=true) for Deno would be immensely helpful for the large and active Deno community.

**The copilot extension of deno could provide the following features**

Developers can use @deno to learn about server-side JavaScript, generate Deno Deploy assets for local development workflows, or leverage Deno's built-in security features for project analysis.

Deno in GitHub Copilot

1. Generate the right Deno assets for your project: Get help with Deno Deploy and watch it generate the deploy.ts, import_map.json, and configuration files tailored to your project's specific needs: "@deno How would I deploy this project with Deno Deploy?"
2. Scaffold Fresh or Lume projects: Kickstart your web development projects with boilerplate code for popular frameworks like Fresh or Lume: "@deno Create a new Fresh project with a basic counter component" or "@deno Set up a Lume blog with Markdown support"
3. Get Deno-specific code suggestions: Streamline your development process with context-aware code completions and snippets optimized for the Deno ecosystem: "@deno Fetch data from an API and display it in a table"
4. Find and fix project vulnerabilities: The Deno extension integrates with Deno's built-in security features to surface potential issues and provide guidance on resolving them: "@deno Analyze my project for security vulnerabilities"

**Additional Information**

1. [Docker Copilot Extension as Example](https://github.com/marketplace/docker-for-github-copilot)
1. [VS Code Blog](https://code.visualstudio.com/blogs/2024/06/24/extensions-are-all-you-need)
Repository: go
Issue: cmd/internal/testdir: Test/initexp.go failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/internal/testdir" && test == "Test/initexp.go"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8739665118851862049)):

    === RUN   Test/initexp.go
    === PAUSE Test/initexp.go
    === CONT  Test/initexp.go
        testdir_test.go:145: compilation timed out
    --- FAIL: Test/initexp.go (34.87s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: godot
Issue: Can I use part of a sprite as the light texture?
Labels: documentation,topic:2d

### Tested versions

4.3rc2

### System information

MacOS Monterey 12.7.5

### Issue description

Sorry, I know this isn't the right place, but I've asked around and no one has given me a definitive answer.

![image](https://github.com/user-attachments/assets/7fd86be8-ab79-4c1d-8350-4740bd9b07c3)
When I try to add light textures to my light nodes, I find that light textures are a bit different from Sprite2D textures that can be cut from large sprites.
Currently, I create separate files for each light texture, but this is a bit inconvenient because I have too many light textures and if I create a file for each texture, there will be a lot of files.
My question is, am I doing something wrong or is it really only possible to generate separate texture files for each light node?


### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: ollama
Issue: The quality of answer significantly deteriorates after Automatic Quantization
Labels: bug

### What is the issue?

Using gemma2-27b for test, after ollama create -q Q8_0, the quality of answer is not very good. The accuracy seems more worse than origin gemma2-9b in hf.  What's the principle behind Ollama's quantization? Is it something like post-training quantization?  Thanks.

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.5
Repository: vscode
Issue: [12f] potential listener LEAK detected, having 1005 listeners already. MOST frequent listener (442):
Labels: error-telemetry

```javascript
Error
at c.create in src/vs/base/common/event.ts:921:15
at h.q [as onDidChange] in src/vs/base/common/event.ts:1128:34
at Object.A [as onWillAddFirstListener] in src/vs/platform/actions/common/menuService.ts:425:34
at u.q [as onDidChange] in out/vs/workbench/workbench.desktop.main.js:91:1280
at D.G in src/vs/workbench/contrib/notebook/browser/view/cellParts/cellOutput.ts:352:36
at p._runFn in src/vs/workbench/contrib/notebook/browser/view/cellParts/cellOutput.ts:218:11
at p.j in src/vs/base/common/observableInternal/autorun.ts:196:10
at p.endUpdate in src/vs/base/common/observableInternal/autorun.ts:237:10
at d.finish in src/vs/base/common/observableInternal/base.ts:372:13
at s.set in src/vs/base/common/observableInternal/base.ts:445:9
at y.setVisible in src/vs/workbench/contrib/notebook/browser/viewModel/cellOutputViewModel.ts:31:16
at a.updateOutputHeight in src/vs/workbench/contrib/notebook/browser/viewModel/codeCellViewModel.ts:449:34
at Pe.Wc in src/vs/workbench/contrib/notebook/browser/notebookEditorWidget.ts:3039:9
at u.value in src/vs/workbench/contrib/notebook/browser/view/renderers/backLayerWebView.ts:623:29
at o.B in src/vs/base/common/event.ts:1230:13
at o.fire in src/vs/base/common/event.ts:1261:9
at <anonymous> in src/vs/workbench/contrib/webview/browser/webviewElement.ts:198:20
at handler in src/vs/workbench/contrib/webview/browser/webviewElement.ts:510:35
at Set.forEach (<anonymous>)
at H.onmessage in src/vs/workbench/contrib/webview/browser/webviewElement.ts:510:16
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=eaa41d57266683296de7d118f574d0c2652e1fc4&bH=2d6032d6-676f-ae2f-c993-48baf5ca24b1)
Repository: vscode
Issue: Uncaught TypeError: Cannot read properties of undefined (reading 'element')
Labels: error-telemetry

```javascript
TypeError: Cannot read properties of undefined (reading 'element')
at I.element in src/vs/base/browser/ui/list/listView.ts:795:28
at w.element in src/vs/base/browser/ui/list/listWidget.ts:1601:20
at w.elementAt in src/vs/workbench/contrib/notebook/browser/view/notebookCellList.ts:329:15
at c.w in src/vs/workbench/contrib/notebook/browser/view/cellParts/cellDnd.ts:138:37
at HTMLDivElement.<anonymous> in src/vs/workbench/contrib/notebook/browser/view/cellParts/cellDnd.ts:86:33
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=eaa41d57266683296de7d118f574d0c2652e1fc4&bH=fb73dbd2-7cbf-d857-c48c-ec207aac5fdd)
Repository: vscode
Issue: Cannot read properties of undefined (reading 'setVisible')
Labels: error-telemetry

```javascript
TypeError: Cannot read properties of undefined (reading 'setVisible')
at a.updateOutputHeight in src/vs/workbench/contrib/notebook/browser/viewModel/codeCellViewModel.ts:449:34
at Pe.Wc in src/vs/workbench/contrib/notebook/browser/notebookEditorWidget.ts:3039:9
at u.value in src/vs/workbench/contrib/notebook/browser/view/renderers/backLayerWebView.ts:638:30
at o.B in src/vs/base/common/event.ts:1230:13
at o.fire in src/vs/base/common/event.ts:1261:9
at <anonymous> in src/vs/workbench/contrib/webview/browser/webviewElement.ts:198:20
at handler in src/vs/workbench/contrib/webview/browser/webviewElement.ts:510:35
at Set.forEach (<anonymous>)
at H.onmessage in src/vs/workbench/contrib/webview/browser/webviewElement.ts:510:16
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=eaa41d57266683296de7d118f574d0c2652e1fc4&bH=284b878d-d997-4d55-108a-7e4617c7ee84)