sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Allow editor cursor blinking rate to match rate provided by the OS
Labels: feature-request,accessibility,editor-input,electron

<!-- ⚠️⚠️ 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. -->
Ref https://github.com/microsoft/vscode/issues/131941#issuecomment-1510386941.

This issue likely requires exposing API in Electron, ref https://github.com/microsoft/vscode/issues/131941#issuecomment-1076376732.

CC @deepak1556
Repository: next.js
Issue: Tauri + NextJS app directory using router.push from next/navigation doesn't render page correctly
Labels: Navigation

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: 7.24.2
    Relevant packages:
      next: 13.3.1-canary.16
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Routing (next/router, next/navigation, next/link), Static HTML Export (output: "export")

### Link to the code that reproduces this issue

https://github.com/Royceb/nextjs-app-dir-tauri-router-push-example

### To Reproduce

1. Ran `npx create-next-app@latest --experimental-app`
2. Set up Tauri

   2.1: Ran `pnpm add -D @tauri-apps/cli`

   2.2: Added `tauri` to package.json scripts. Ran `pnpm tauri init`.

3. Updated next.config.js to use `output: "export"` for SSG (Static Generation).
4. Made a simple page at `app/examplePage/page.tsx`
5. Imported `next/navigation` in `app/page.tsx` and added a button that calls `router.push('/examplePage')`.
6. Ran `pnpm tauri dev` and clicked the button. The app navigated to the example page as expected and rendered it properly.
7. Ran `pnpm tauri build` and opened the app. Clicked the button. The app did naviate to the example page, but it did not render it properly. The page rendered code as text instead of rendering the page.

### Describe the Bug

I was uncertain whether to open this in Tauri or NextJS, so I opened issues in both platforms.

While utilizing a NextJS application, version 13, and the experimental app directory, I encountered an issue where using router.push to navigate to a new page fails to render correctly. Although the navigation occurs successfully, the page only displays code as text instead of rendering the expected content. I have not found any console logs or errors related to this issue.

This problem only arises after building and running the application. Locally, everything seems to be functioning correctly.


Recording: https://user-images.githubusercontent.com/3469263/233444738-73f955e9-2aae-43fb-a92b-d0a4c1dd3c3e.mov

Screenshot: <img width="1505" alt="image" src="https://user-images.githubusercontent.com/3469263/233444957-2b8b4145-bdd9-4287-98ad-f4b46ce9c4cc.png">



### Expected Behavior

The page should render correctly.

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

_No response_

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

_No response_
Repository: next.js
Issue: code EPERM, path: ...\\trace
Labels: bug

### Verify canary release

- [x] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.13.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.16
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://github.com/Felipe-Emanuel/Pablo-Studio

### To Reproduce

`npm run dev` to run project and this api to get products mocked/api to freigth request and side by side run `npm run build` to get this problem in your screen

### Describe the Bug
uncaughtException [Error: EPERM: operation not permitted, open <project path\.next\trace>'] {
  errno: -4048,
  code: 'EPERM',
  syscall: 'open',
  path: 'F:\\projeto-teste\\.next\\trace'
}

Dev server should not be online while building, but building static page require API and my API's are running by next api...

to build an aplication is necessary to access file trace in .next. U can do it if are u in development, but (and u can check in your computer with prop trace file in .next folder) when run `npm run build` u will just lost your admin powers and cannot more access trace, so u can't do build 

### Expected Behavior

a normal comportament is a full build completelly or any tipcal error to be resolved, but this I don't know if is in my hand once time that I lost my admin power in trace

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Yeah, but since this error, it's impossible deploying with build problems
Repository: excalidraw
Issue: Custom themes
Labels: discussion

Hi there!

Currently your canvas has 2 color modes: dark / light

Did you considered adding opportunity to include custome themese like Material, Dracula ?

Regards.
Repository: flutter
Issue: android tests timing out fetching maven artifacts
Labels: platform-android,team-infra,P2,triaged-infra

On april 19 (and the morning of april 20) there appeared to have been some kind of outage with the server we use to fetch maven artifacts. Some sample failed builds:

- https://ci.chromium.org/p/flutter/builders/prod/Linux_android%20gradient_dynamic_perf__e2e_summary/5406
- https://ci.chromium.org/p/flutter/builders/prod/Windows_android%20flutter_gallery_win__compile/9638
- https://ci.chromium.org/p/flutter/builders/prod/Windows_android%20flutter_gallery_win__compile/9640
- https://ci.chromium.org/p/flutter/builders/prod/Linux%20Production%20Engine%20Drone/125216?

In the logs I see a lot of logging like:

```
[2023-04-19 17:21:24.817934] [STDOUT] stderr:    > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.31.
[2023-04-19 17:21:24.817934] [STDOUT] stderr:      Required by:
[2023-04-19 17:21:24.817934] [STDOUT] stderr:          project :
[2023-04-19 17:21:24.817934] [STDOUT] stderr:       > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.31.
[2023-04-19 17:21:24.817934] [STDOUT] stderr:          > Could not get resource 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugin/1.5.31/kotlin-gradle-plugin-1.5.31.pom'.
[2023-04-19 17:21:24.817934] [STDOUT] stderr:             > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugin/1.5.31/kotlin-gradle-plugin-1.5.31.pom'.
[2023-04-19 17:21:24.817934] [STDOUT] stderr:                > repo.maven.apache.org
```

Cross referencing with https://status.maven.org, I don't see this particular endpoint covered (and the first row, a CDN, reports 100% uptime in the last 90 days).

![Screenshot from 2023-04-20 11-39-41](https://user-images.githubusercontent.com/7856010/233458003-5dd2064a-325c-494d-a3a6-3851d23fe33d.png)

I'm wondering if our gradle config is pulling from some less reliable mirror? I don't see `repo.maven.apache.org` appear in the framework repo, and I'm guessing the way we are requesting maven is by using `mavenCentral()` in our build.gradle files: https://github.com/flutter/flutter/blob/master/dev/benchmarks/macrobenchmarks/android/build.gradle#L13

I wonder if this is something updating gradle will fix?
Repository: vscode
Issue: Test: standalone color picker:  decorators with hsl values, some don't work, some hsl values do trigger the decorator
Labels: bug,editor-color-picker


Testing https://github.com/microsoft/vscode/issues/180678

@aiday-mar 


Steps to Reproduce:

1. Enable the setting `Editor: Default Color Decorator`.
2. Insert this color value: `hsl(253, 100.00%, 47.10%)` into a ts or jsx file.
3. No color decorator appears for that specific hsl value, but a decorator appears for other hsl values, like `hsl(0, 83.60%, 47.80%)`.

I don't know which hsl values work or don't - some regex issue I assume.

![colorDecorationhslBug](https://user-images.githubusercontent.com/31813701/233460346-ac7d6b65-df1f-4931-a9a4-f1a71a041a8f.gif)



Version: 1.78.0-insider
Commit: 208bbb0d788cce3eb80799e3565ee2204391b86d
Date: 2023-04-20T05:20:21.925Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.78.0-insider Chrome/108.0.5359.215 Electron/22.4.7 Safari/537.36
Repository: flutter
Issue: [flutter_tools] Windows tool_integration_tests_2_6 flakes on timeout
Labels: tool,P2,c: flake,team-tool,triaged-tool

For example: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8783915727124773233/+/u/run_test.dart_for_tool_integration_tests_shard_and_subshard_2_6/test_stdout

```
17:18 +6 ~1 -1: test/integration.shard/break_on_framework_exceptions_test.dart: breaks when EditableText.onChanged throws [E]
  TimeoutException after 0:15:00.000000: Test timed out after 15 minutes.
  dart:isolate  _RawReceivePort._handleMessage
```
Repository: vscode
Issue: Create different visuals on editor for different type of code actions
Labels: feature-request,editor-code-actions

<!-- ⚠️⚠️ 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. -->
On the editor surface code actions surface visuals to indicate one is available (docs: https://code.visualstudio.com/docs/editor/refactoring#_code-actions-quick-fixes-and-refactorings).  In VS Code all code actions types show the same indicator (whether it is a quick fix or a refactoring).  In other editors these are disambiguated so that you know what specific actions are different types:

QuickFix:
![image](https://user-images.githubusercontent.com/4821/233481335-b83f156b-eed8-49fa-b94d-cf68c665fc3f.png)

Refactor:
![image](https://user-images.githubusercontent.com/4821/233481363-bf938a78-a7df-4bf8-bbc9-6e3e5560ea5e.png)

Language providers can surface different 'kinds' in their layer (an example is Roslyn already does this).
Repository: stable-diffusion-webui
Issue: [Bug]: Frequent hardlocks with slow/unstable network connection
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

When trying to use the frontend with bad network, frequently the progress bar will just disappear before any progress is shown an the Generate button will stop working. If that happens the only thing that fixes it is refreshing the page and losing all my settings (since dynamic prompts syntax is still not preserved in params.txt). This makes the webui pretty much unusable unless I'm lucky and the network picks up again

### Steps to reproduce the problem

1. Go to txt2img
2. Press Generate with a bad connection

### What should have happened?

Should have allowed Generate to start a new generation 

### Commit where the problem happens

7201d940

### What platforms do you use to access the UI ?

Android

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

```Shell
N/A
```


### List of extensions

N/A

### Console logs

```Shell
N/A
```


### Additional information

_No response_
Repository: flutter
Issue: Update internal documentation for how to run cocoon projects 
Labels: team-infra,P2,triaged-infra

See https://chat.google.com/room/AAAAQFWU2Go/_kmI1q0wo0o for more context. 

Update
https://g3doc.corp.google.com/company/teams/flutter/infrastructure/cocoon/local_development.md?cl=head#test-with-flutter-dashboard-dev-project

To include how to become eligible for the required groups, That you need to request temporary access, and update the credential storage export to a file that exists with the current gclient config structure.
Repository: flutter
Issue: Improve ability to override the `TargetPlatform` for a subtree.
Labels: c: new feature,framework,f: material design,P3,team-design,triaged-design

## What problem is this solving?

Currently, there is no reliable way to override the expected platform appearance/behavior of a portion of the widget tree. You can set `defaultTargetPlatform` and the app will change fairly reliably to the new platform, but you can also set `ThemeData.platform`, and that isn't nearly so well respected.  In addition, overriding platform really seems like something that should be handled at a lower framework level than the "material" layer. Lastly, there's no enforcement that encourages widgets to use the `ThemeData.platform` instead of the `defaultTargetPlatform` when customizing their behavior/appearance.

## Proposal

It seems the best place to access this would be in the "widgets" layer, on the `MediaQueryData` object.

The problem with the `ThemeData.platform` override is that not all of the places that do customization based on platform look at it: it's easier (and more well known) to get `defaultTargetPlatform`.

But `defaultTargetPlatform` is used in >400 places in the framework alone, so we can't easily deprecate it in favor of a `MediaQueryData` accessor.

So, we could:

  1) Add a `platform` accessor to `MediaQueryData`, defaulting to the `defaultTargetPlatform`,
  2) Make `ThemeData` default to the `MediaQueryData` value, and
  3) Create (hand wave) some way to encourage use of the `MediaQueryData` value over `defaultTargetPlatform` (a lint maybe, and override it where we really need context-less access?)  and then
  4) Deprecate the `ThemeData.platform` accessor in favor of `MediaQueryData.platform`.

It would also be helpful to create a version of `TargetPlatformVariant` that modifies the `ThemeData` (and later `MediaQueryData`) default without modifying the `defaultTargetPlatform`, so it would be easier to test that descendants are using the right platform configuration source.
Repository: electron
Issue: [Feature Request]: Security Documentation: Add Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy
Labels: enhancement :sparkles:,security 🔒

### 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 feature request that matches the one I want to file, without success.

### Problem Description

Electron already has documentation in the security guidelines for the `Content-Security-Policy` header (https://www.electronjs.org/docs/latest/tutorial/security#7-define-a-content-security-policy). 

There are two (kind of new) headers that can help make websites more secure:  `Cross-Origin-Opener-Policy` and `Cross-Origin-Embedder-Policy`.

## Cross Origin Opener Policy

(from MDN): COOP will process-isolate your document and potential attackers can't access your global object if they were to open it in a popup, preventing a set of cross-origin attacks dubbed [XS-Leaks](https://github.com/xsleaks/xsleaks).

## Cross Origin Embedder Policy

(from MDN):  The HTTP Cross-Origin-Embedder-Policy (COEP) response header configures embedding cross-origin resources into the document.

### Proposed Solution

Adding a short information about Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy to the Electron security documentation, explaining the benefits and how those headers can be enabled in electron.


Here is an example of what the code could look like (very similar to configuring a Content-Security-Policy header):

```js
const { session } = require('electron')

session.defaultSession.webRequest.onHeadersReceived((details, callback) => {
  callback({
    responseHeaders: {
      ...details.responseHeaders,
      'Cross-Origin-Opener-Policy': 'same-origin', 
      'Cross-Origin-Embedder-Policy': 'require-corp'
    }
  })
})
```

### Alternatives Considered

none

### Additional Information

Cross Origin Opener Policy (MDN): https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
Cross Origin Embedder Policy (MDN): https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy
Cross Origin Isolation (web.dev): https://web.dev/cross-origin-isolation-guide/#enable-cross-origin-isolation
Repository: pytorch
Issue: `torch.ops.aten.empty` is not discoverable from `dir(torch.ops.aten)` until explicitly calling getattr
Labels: triaged,module: library

### 🐛 Describe the bug

Accidentally discovered this when I was trying to retrieve all `OpOverload`s under `torch.ops.aten`. I noticed that `torch.ops.aten.empty` (may or may not be the only case) is not discoverable from `for op in torch.ops.aten`. 

However, it does appear there is such an op since `torch.ops.aten.empty` returns a valid object. And after retrieving that through `getattr` explicitly, it appears under `dir(torch.ops.aten)`.

I wonder if this is a bug or by design? And if it's not a bug what's the recommended way to loop over all `torch.ops.aten`?

```python
>>> import torch
>>> "empty" in torch.ops.aten
False
>>> torch.ops.aten.empty
<OpOverloadPacket(op='aten.empty')>
>>> "empty" in torch.ops.aten
True
```

### Versions

Main from 5315317b7bbb13d1b8d91a682cec1fb4dace79e4

cc @anjali411
Repository: flutter
Issue: Provide Page adpaters to Flutters PopupRoute's in go_router.
Labels: c: new feature,d: api docs,package,c: proposal,P3,p: go_router,team-go_router,triaged-go_router

## Description 

I've been tinkering recently with navigator 2.0 and realized it uses Pages instead of Routes eg:
With navigator 1.0 we pushed a MaterialPageRoute that extends Route, but with navigator 2.0 we use pages  like MaterialPage instead. 

<img width="4814" alt="Untitled" src="https://user-images.githubusercontent.com/37002358/233514089-cc343af9-273b-4c31-a7d1-6b992b5de315.png">

Flutter already has implemented both MaterialPage and CupertinoPage , but lacks any *Page implementation for any of the PopupRoute, if we wanted to declare Dialogs and BottomSheets while using navigator 2.0. I know I could just imperatively call showDialog and other methods , but I would like to declare the pages as part of my router, when it makes sense. Implementing a new page is trivial and is mostly wrapping the existing Route class and implementing the createRoute method of the Page class eg:

```dart
class DialogPage<T> extends Page<T> {
  final Offset? anchorPoint;
  final Color? barrierColor;
  final bool barrierDismissible;
  final String? barrierLabel;
  final bool useSafeArea;
  final CapturedThemes? themes;
  final WidgetBuilder builder; 
  
  const DialogPage({
    required this.builder,
    this.anchorPoint,
    this.barrierColor = Colors.black54,
    this.barrierDismissible = true,
    this.barrierLabel,
    this.useSafeArea = true,
    this.themes,
    super.key,
    super.name,
    super.arguments,
    super.restorationId,
  });
  
  @override
  Route<T> createRoute(BuildContext context) => DialogRoute<T>(
      context: context,
      settings: this,
      builder: builder,
      anchorPoint: anchorPoint,
      barrierColor: barrierColor,
      barrierDismissible: barrierDismissible,
      barrierLabel: barrierLabel,
      useSafeArea: useSafeArea,
      themes: themes);
}
```
So my question:  is  there a reason why  we don't get Page versions of any  PopupRoute with flutter or go_router?

## Use case

Using PopupRoutes, Dialogs and Modals as part of GoRouter or more broadly any navigator 2.0 package (note how the url changes)

![go_nav_finished](https://user-images.githubusercontent.com/37002358/233514545-d5b88b9b-04ac-46e4-b4ba-7dca8f78bf55.gif)

## Proposal

Either document in the package how to wrap an existing route as I show above, or create the corresponding page counterparts to all of flutters  PopupRoute's, in   go_router or the flutter SDK.

> I only primarily mention to add these to the SDK because it already provides  MaterialPage and CupertinoPage
Repository: terminal
Issue: Graphic artifacts (small gray squares) on the desktop when the window is minimized
Labels: Needs-Repro,Issue-Bug,Product-Terminal,Priority-2,Area-Windowing

### Windows Terminal version

1.16.10262.0

### Windows build number

10.0.22621.1555

### Other Software

_No response_

### Steps to reproduce

I'm not sure exactly when it happens. I use WT without issues, and after a while I notice the glitch; not sure what makes it appear. Once it starts appearing, it stays. 

### Expected Behavior

There should be no graphic artifacts on the desktop when I minimize or restore the window.

### Actual Behavior

Whenever I minimize the window, small gray squares appear just above the taskbar:

![image](https://user-images.githubusercontent.com/1864281/233515606-58c1fbfa-72b8-47ee-ae81-b9b29d481764.png)

The gray squares are only visible on the desktop. If any window masks that part of the desktop, they don't appear (in other words, they appear below all windows, with the lowest z-index).

Their number seems to match the number of open tabs in WT, although it's a bit inconsistent.

When I restore the window, I see just one small gray square in the top left corner of the screen:

![image](https://user-images.githubusercontent.com/1864281/233515748-438ef995-351d-4725-b375-4c5b97e5e3c0.png)

It also appears below all windows except the WT window (i.e. when the WT window is maximized I still see the square in its top-left corner, but any other window masks it).
Repository: go
Issue: runtime/metrics: CPU metrics update at a relatively low rate
Labels: NeedsFix,compiler/runtime

Currently they update every GC cycle. It should be straightforward to make them "continuously" updating, since most (all?) of them are accumulated in real time.
Repository: pytorch
Issue: In torchelastic support running worker rank 0 on agent rank 0 consistently
Labels: oncall: distributed,triaged,module: elastic

### 🚀 The feature, motivation and pitch

Currently, when launching distributed jobs using torchrun, the Rank 0 worker can land on any arbitrary node. This ask is to add a new rendezvous implementation for which worker rank 0 always runs on agent rank 0.

### Additional context

This will improve observability of the distributed job by easily locating logs for the rank0 worker

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @dzhulgakov
Repository: neovim
Issue: download() or fetch() without netrw
Labels: enhancement,compatibility,plugin,complexity:low,netrw,network

### Problem

- No easy way to download a file, though both `curl` and libuv are available in all Nvim targets.
- `:edit <uri>` (example: `:edit https://example.com/foo.txt`) is dependent on netrw for no reason


### Expected behavior

separate PRs:

* [ ] introduce something like `vim.fetch()` (`vim.net.fetch()` ? idk, look at Go, NodeJS, for precedent)
    - could use `curl` or `vim.uv`
* [ ] use it to implement `:edit <uri>` without netrw
* [ ] use it to implement spellfile download. https://github.com/neovim/neovim/issues/7189


### Related

- https://github.com/neovim/neovim/issues/23231
- https://github.com/neovim/neovim/issues/4378

### Use-cases in the wild

- https://github.com/3rd/image.nvim/blob/88e9693e188b8464b1c426aebb4389fd9db2fcbf/lua/image/image.lua#L393