sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Add informative messaging for `flutter config` when on a feature branch
Labels: P2,team-tool,triaged-tool

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

~~1. Run `flutter --disable-telemetry` to disable telemetry (it should say `Analytics reporting disabled.`)
2. Run `flutter config` to see the current status of analytics opt in (it should say`Analytics reporting is currently disabled.` at the bottom)
3. Run `flutter --enable-telemetry` to re-enable it, it should say (it should say `Analytics reporting enabled.)
4. Run `flutter config` again... it still says `Analytics reporting is currently disabled.` at the bottom even though the configuration files say it is enabled~~

Turns out that this issue was a result of not being on the main/master branch when running `flutter config`. Analytics is always suppressed when the developer is on a feature branch.

Instead, we should update the output of `flutter config` to print out that analytics is disabled/suppressed for the current command invocation because they are on a feature branch.

Possible example for message when running from a feature branch
```text
// Old
Analytics reporting is currently disabled.

// New
Analytics reporting is currently disabled when running from feature branch.
```
Repository: PowerToys
Issue: MWB "hide at screen edge" only works on secondary screen, and position is wrong when returning
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.72.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

I have two computers with the same version of PowerToys, and the setting "Hide mouse at the screen edge" enabled on both.

When I move to the secondary screen, the mouse cursor is not hidden on the primary screen. When I move back to the primary screen, the mouse cursor is hidden on the secondary screen as expected.

When I move back from the secondary screen, the cursor isn't placed at the edge, instead it is placed at the top center of the primary screen. This behavior is new in version 0.72.0.

If I disable the setting "Hide mouse at the screen edge", the cursor is placed at the center of the primary screen when I return from the secondary screen. I.e. this behaviour occurs regardless of the setting, the setting only changes where the cursor is placed when returning.

### ✔️ Expected Behavior

The cursor should be hidden on the primary screen.

When moving back from the secondary screen, the cursor should be positioned at the edge of screen.

### ❌ Actual Behavior

The cursor is not hidden, it is visible at the top center of the primary sceen.

When moving back from the secondary screen, the cursor is positioned at the top center on the primary screen.

### Other Software

_No response_
Repository: flutter
Issue: `dividerThickness: 0` in DataTable stills renders a visible divider
Labels: framework,f: material design,has reproducible steps,P3,found in release: 3.10,team-design,triaged-design,found in release: 3.13

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

1. Use the code sample in dartpad
2. Observe, that there are dividers rendered

### Expected results

Using `dividerThickness: 0` should not render a visible border. 
Actually, using `dividerThickness: 0.1` renders a smaller visible border, so it looks like using `0` falls back to some default.

### Actual results

A border of thickness 1 seems to be rendered.

### Code sample

<details><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

const Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(
        scaffoldBackgroundColor: darkBlue,
      ),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        DataTable(
          dividerThickness: 0,
          columns: const [
            DataColumn(label: Text('h1')),
            DataColumn(label: Text('h2')),
          ],
          rows: const [
            DataRow(cells: [DataCell(Text('1')), DataCell(Text('2'))]),
            DataRow(cells: [DataCell(Text('3')), DataCell(Text('4'))]),
          ],
        ),
        DataTableTheme(
          data: Theme.of(context).dataTableTheme.copyWith(dividerThickness:0),
          child: DataTable(
            dividerThickness: 0,
            columns: const [
              DataColumn(label: Text('h1')),
              DataColumn(label: Text('h2')),
            ],
            rows: const [
              DataRow(cells: [DataCell(Text('1')), DataCell(Text('2'))]),
              DataRow(cells: [DataCell(Text('3')), DataCell(Text('4'))]),
            ],
          ),
        ),
      ],
    );
  }
}
```

</details>


### Screenshots or Video

<details>
<summary>Screenshots / Video demonstration</summary>

![image](https://github.com/flutter/flutter/assets/740791/600c83ec-defb-4a31-a3fe-68cbaee4e571)

</details>


### Logs

<details><summary>Logs</summary>

Not needed.

</details>


### Flutter Doctor output

<details><summary>Doctor output</summary>

Not needed.

</details>
Repository: PowerToys
Issue: Would love a search selected page.
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Would love to be able to select a windows and the be able to search text on that page.

### Scenario when this would be used?

I work a fair amount in group policys. Would be good to click setting, get the report, expand all, then ctrl + F or some other combination and then search the entire page for what i am looking for.

### Supporting information

_No response_
Repository: vscode
Issue: layout or display issue
Labels: bug,quick-pick

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.81.0
- OS Version: windows 64

Steps to Reproduce:

1.  minimize the vs code window
2.  try to publish a repo to GitHub
3.  encountering a layout or display issue within (VS Code) that is affecting the ability to interact with the OK 
    button when trying to publish a repository to GitHub.

![Screenshot 2023-08-09 180126](https://github.com/microsoft/vscode/assets/71914071/ede9e01f-3304-4446-b708-a61a8ab2011a)
Repository: godot
Issue: Unable to convert polygon2D on android
Labels: bug,platform:android,topic:editor,topic:porting

### Godot version

4.1.1

### System information

Android 12 - VIVO Y20i

### Issue description

Unable to convert and save a sprite to polygon2D because a preview window will does't show the save button.

### Steps to reproduce

1. Open the given project in any android phone.
2. Open world scene and click on sprite.
3. Click on Sprite2D and click convert to polygon2D.
4. then a preview window will appear but can't save it.
   Again only on android

### Minimal reproduction project

[Polygon 2d Problem.zip](https://github.com/godotengine/godot/files/12302591/Polygon.2d.Problem.zip)
Repository: godot
Issue: TileSet editor is still displayed when disabled with Editor Feature Profile
Labels: bug,topic:editor,topic:2d

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Windows 10.0.19045

### Issue description

When editing a **TileMap**, the **TileSet** editor shows alongside the **TileMap** editor, in the bottom dock. If the TileSet editor is disabled from an Editor Feature Profile, this should not happen. 

![image](https://github.com/godotengine/godot/assets/66727710/4f182f7f-8847-4c87-968e-d0da866aeb24)

I wouldn't want some people to modify the **TileSet** resource by mistake.

### Steps to reproduce

- Go to **Editor/Manage Editor Features**;
- Find TileSet and disable "Enable Contextual Editor";
    - Alternatively, disable the TileSet entirely. 
- Click on any TileSet node containing a valid TileMap
- Notice that the TileSet editor still appears

### Minimal reproduction project

N/A on the project, however the profile is as follows:
[Dungeon Maker.txt](https://github.com/godotengine/godot/files/12302702/Dungeon.Maker.txt)

Change the file extension of this file to `.profile`, then import it in the editor, if you'd like.
Repository: vscode
Issue: Git - Add commit (no verify) option to Commit dropdown
Labels: feature-request,git

I thought it would be useful to add a Commit (no verify) option to the commit dropdown in the built-in Git extension in order to skip commit pre-hooks.

![imatge](https://github.com/microsoft/vscode/assets/46191980/b11253de-d5e0-4ccb-a1bd-48837563907d)

This is useful for cases where the pre-hooks fail or take very long to complete.

Note: I am working on this issue myself. Where do I start? I came here to ask: where is the code for the git panel under `extensions/git`?
```[tasklist]
### Tasks
- [x] Add no verify command (internal)
- [x] Add to git explorer UI
```
Repository: PowerToys
Issue: Keyboard Language typing mistake
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

When we have multiple keyboard layouts installed, and we type by mistake in an unintended language; allow to select and convert the mistaken text into the intended language

### Scenario when this would be used?

When typing with the wrong keyboard layout selected

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: Render Vue component directly in MDX files
Labels: bug,needs triage

### Describe the bug

In Storybook@6.5, we were able to easily add Vue content in our `mdx` files:

```
// colors-table.story.mdx
import { Meta, Story, Canvas } from "@storybook/blocks;
import ListOfColors from "./colors-table.vue";

<Meta title="Styles/Colors" />

## Definitions
<Story name="table">
  {{
    components: { ListOfColors },
    template: `<ListOfColors />`,
  }}
</Story>
```

----


I'm trying to achieve the same in Storybook@7, but since this is not supported, it creates a huge overhead.
- I have to create a file `colors-table.story.ts`, adding a default export, and a single story with my Vue component.
- Later, I have to create a `colors-table.mdx` and include the story file.

How can I achieve to just render a Vue file inside of a `mdx` file, without having to create stories for it? I just need to render pure docs components.
Repository: storybook
Issue: [Bug]: Performance regression when using many Source components in one mdx page
Labels: bug,performance issue,block: source,needs triage

### Describe the bug

We got a report that when using the Source component:
https://storybook.js.org/docs/react/api/doc-block-source

```mdx
<Source language="html" code={`<some>html</some>`} />
```

You can get very severe runtime performance regressions in storybook. 
The page takes very long time to render and sometimes the tab even crashes.

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Plugins don't use `--local-engine` framework on macOS/iOS
Labels: c: regression,team,platform-ios,tool,platform-mac,a: build,P2,a: plugins,team-ios,triaged-ios

STR:
- Add new plugin API to the engine for iOS or macOS
- Build the engine
- Add use of the new API in a plugin, locally, for testing
- Try to run the plugin's example with `--local-engine`

Compilation will fail, because podhelper.rb is unconditionally using the actual tool cache dir [here](https://github.com/flutter/flutter/blob/f4c25bbb351cc59ffdefe980c0c993196a8a6d47/packages/flutter_tools/bin/podhelper.rb#L42) and [here](https://github.com/flutter/flutter/blob/f4c25bbb351cc59ffdefe980c0c993196a8a6d47/packages/flutter_tools/bin/podhelper.rb#L124). It looks like this regressed in https://github.com/flutter/flutter/pull/59044 and https://github.com/flutter/flutter/pull/72020; prior to those, we were using `FLUTTER_FRAMEWORK_DIR`, which the tool used to set to point to the local engine build.

This makes testing plugin API changes much harder than it used to be since it requires modifying `flutter` in some way.
Repository: opencv
Issue: GaussianBlur Performance Difference between OpenCV 3.3.0 and OpenCV 4.7.0
Labels: question (invalid tracker),incomplete

### System Information

OpenCV version: 4.7.0 and 3.3.0
Operating System / Platform: Windows 10
Compiler & compiler version: Visual Studio 2017

### Detailed description

I recently upgraded an older software project that used to run using OpenCV 3.3.0 to the version of OpenCV that was then up-to-date (4.7.0). For some reason, somewhere inside the project, a grayscale image is blurred using the function GaussianBlur. Even though the input images and all parameters are similar, the output is very different between the output that is obtained from the 3.3.0-version and the 4.7.0-version.
I call the function as follows:

```
#include <opencv2/opencv.hpp>

int main()
{
cv::Mat img = cv::imread("<path>", IMREAD_GRAYSCALE);
cv::Mat blurred;
cv::resize(img , img , { 160, 90 });
cv::GaussianBlur(frame, blurred, {0, 0}, 7.5);
}
```

**The result is different in almost every pixel**, by usually less than 10, but always around 3-5 intensity steps. I tried to debug into OpenCV and found a completely new implementation using the OpenCV parallel_for_ in the newer version in contrast to a simpler hal::sepFilter2D in OCV 3.3.0, so it was hard to compare intermediate steps. 

It seems highly suspicious and very unlogical for me, though, that the results for a fixed algorithm are this different between the two versions. I did not find anything mentioned in any of the release notes up to now stating that the old version of the Gaussian blur was wrong to some degree, so this leaves me very confused.

Does anyone have any insights? Imho, a software update should not change the quality of standard algorithms, at least not if it's not purely concerning speed.

[This is a question, but related to critical insights in the code, so I figured this is the better place to put it than in the forum where users are probably more present than contributors.]

### Steps to reproduce

Generate two projects, one with OpenCV 3.3.0 and one with OpenCV 4.7.0 and use the same main-file (above). Look at the differences. e.g. with the help of Image Watch.

### Issue submission checklist

- [ ] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: ant-design
Issue: 增加手机浏览器访问时的文档列表结构
Labels: 📝 Documentation,Inactive,📱Mobile Device

### What problem does this feature solve?

可以解决例如官网使用手机浏览《设计》标签页时只能显示《介绍》文档而不能《设计价值观》等所有其它文档。

### What does the proposed API look like?

无

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: electron
Issue: [Bug]: Minimize and restore the browserWindow, and the webview that renders PDF will freeze.
Labels: component/webview,bug :beetle:,platform/all,status/confirmed,has-repro-gist,component/webcontents,25-x-y,26-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

25.x

### What operating system are you using?

Windows

### Operating System Version

windows 11 22h2

### What arch are you using?

x64

### Last Known Working Electron version

electron@20.0.0-beta.11

### Expected Behavior

Webview will not freeze.

### Actual Behavior

The webview on the browserWindow that renders PDF with the backgroundThrottling attribute turned off will freeze when the browserWindow is minimized and restored.

### Testcase Gist URL

https://gist.github.com/asd281533890/81db70e531254faf4981026637f3493f

### Additional Information

_No response_
Repository: next.js
Issue: Unable to fix logs `[BABEL] Note: The code generator has deoptimised the styling of`
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

All environments are impacted.

### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

Not available.

### To Reproduce

By default, Babel will show these types of logs:

`[BABEL] Note: The code generator has deoptimised the styling of some.generated.file.ts as it exceeds the max of 500KB.`

It's very easy to fix them, by using the [Babel Compact Option](https://babeljs.io/docs/options#compact)

Unfortunatelly the current [Next.js config loader](https://github.com/vercel/next.js/blob/canary/packages/next/src/build/babel/loader/get-config.ts) does not support the `compact` option so there is no way to get rid of this error.

The only avilable workaround is to use `overrides` in the Webpack Next.js config:

```ts
config.module.rules.forEach((rule) => {
    rule?.oneOf?.forEach((nestedRule) => {
      if (nestedRule?.use?.loader?.includes('babel')) {
        nestedRule.use.options.overrides = nestedRule.use.options.overrides ?? []
        // Prevents duplicate overrides in dev.
        if (
          !nestedRule.use.options.overrides.some(
            (override) => override.test === nestedRule.test && override.compact === true
          )
        ) {
          nestedRule.use.options.overrides.push({
            test: nestedRule.test,
            compact: true,
          })
        }
      }
    })
  })
```
### Describe the Bug

This will happen in any project with files bigger than 500KB that uses Babel.

### Expected Behavior

I would expect to be able to get rid of those logs by setting the `compact` Babel option. Currently this option is being ignored.

### Which browser are you using? (if relevant)

N/A

### How are you deploying your application? (if relevant)

_No response_
Repository: rust
Issue: llvm wrapper's target feature filtering breaks UI tests, is difficult to debug
Labels: A-LLVM,A-testsuite,T-compiler,C-bug

Every attempt to ask LLVM "does the target support this feature?" either succeeds or causes a [side effect](https://github.com/llvm/llvm-project/blob/25a4a9360e1dedb572dc007cf8cc97dfc3efdeac/llvm/lib/MC/MCSubtargetInfo.cpp#L82-L83) of writing a message to stderr:

```c++
  // If there is a match
  if (FeatureEntry) {
    // ...   
  } else {
    errs() << "'" << Feature << "' is not a recognized feature for this target"
           << " (ignoring feature)\n";
  }
```

Since the UI tests are very strict about matching exactly the same stderr output across LLVM versions, this means teaching rustc about an LLVM feature that exists in only some versions but not others creates a contradiction: if that error line is expected, the tests will fail against newer versions of LLVM, and if it's absent then the tests can't pass against the older versions. Since rustc runs the filter at target selection time, any UI tests at all for this architecture will fail, regardless of their contents.

What's worse is the developer experience. I ran into it introducing UI tests for riscv targets as part of adding an ABI (see https://github.com/rust-lang/rust/pull/111891#issuecomment-1562122922 ) and since the issue presents as having forgotten to `--bless` some output, I went back and forth a number of times adding and removing the line. It's not at all clear from the failure  that an unused feature supported-on-some-but-not-other-LLVMs is the culprit, and because it fails in CI the feedback loop for this condition is terribly long. 
 
Some possible resolutions include:

1. Remove the preemptive LLVM target feature filtering entirely and rely on LLVM to ignore  unknown features; this matches the current state of the codebase, in that it's not possible to get CI to approve a version of rustc that relies on the filtering, so it's effectively a no-op.
2. Plan to remove, suspend, or modify UI tests for any architectures that have partial feature support when new features are added; the challenge here would be decidedly DX shaped in effectively communicating this plan to anyone touching these tests who might not be otherwise aware of it (such as myself).
3. Remove the side effect from the filter code path. The only workable implementation of this approach that I found is in https://github.com/rust-lang/rust/commit/70b2188c36ea4730a22b219617cefab82e2e7baa ; the carrying cost there can be time-bounded by asking upstream LLVM to add a getter and then waiting for that change to percolate all throughout the various packaging ecosystems. That's work I'm willing to take on, if that would make this change acceptable to repair rustc in the meantime.

/cc @nikic