sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Error using SelectionArea with nested routes
Labels: framework,f: routes,a: error message,has reproducible steps,P2,f: selection,found in release: 3.3,found in release: 3.7,team-framework,triaged-framework

## Steps to Reproduce

Wrapping a page with a selection area will not work if it is not the topmost route. Likely not an issue with GoRouter just my router of choice to demonstrate the issue.

**Expected results:** <!-- what did you want to see? -->

I would expect SelectionArea to not cause any issues when wrapping my routes.

**Actual results:** <!-- what did you see? -->

If I was to load the app on the initial/lowest route, then navigate to the nested route, all would work fine.

But if I go straight to the nested route, such as you might on the web, the error occurs.

<details>
<summary>Code sample</summary>

```dart
final router = GoRouter(
  // Default to the nested location
  // Or for a more realistic use-case, navigate to the url /a/b on the web
  initialLocation: '/a/b',
  routes: [
    GoRoute(
      path: '/a',
      builder: (_, __) {
        // With selection area here, error will occur
        return const SelectionArea(child: Text('Page a'));
        // With no selection area here, error will not occur
        // return Text('Page a');
      },
      routes: [
        GoRoute(
          path: 'b',
          builder: (_, __) {
            return const SelectionArea(child: Text('Page b'));
          },
        ),
      ],
    ),
  ],
);
```

</details>

<details>
  <summary>Logs</summary>

```
════════ Exception caught by scheduler library ═════════════════════════════════
The following assertion was thrown during a scheduler callback:
'package:flutter/src/rendering/paragraph.dart': Failed assertion: line 963 pos 12: '!debugNeedsLayout': is not true.
package:flutter/…/rendering/paragraph.dart:963
2

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack
#2      RenderParagraph.getBoxesForSelection
package:flutter/…/rendering/paragraph.dart:963
#3      _SelectableFragment._rect
package:flutter/…/rendering/paragraph.dart:1501
#4      _SelectableFragment.getTransformToParagraph
package:flutter/…/rendering/paragraph.dart:1475
```

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.10, on macOS 12.6 21G115 darwin-arm, locale
    en-AU)
[✓] Android toolchain - develop for Android devices (Android SDK version
    33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.74.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

• No issues found!
```

</details>
Repository: vscode
Issue: VS Code is still adding `/d /c` to task commands
Labels: bug,tasks

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.74.2
- OS Version: Windows 11

Steps to Reproduce (on Windows):

1. Have an `npm` task that starts a script.
2. In the User Preferences, set `"terminal.integrated.automationProfile.windows"` as such:
    ```json
    "terminal.integrated.automationProfile.windows": {
        "path": "nu.exe",
        "args": ["-c"],
    },
    ```
    This is an example; this also works with, e.g. `pwsh.exe` / `["-Command"]`.
3. Run the task.
4. VS Code will run `nu.exe -c /d /c yarn run name` rather than `nu.exe -c "yarn run name"`.

This was marked as fixed in #93437, but it isn't. A [workaround](https://github.com/microsoft/vscode/issues/93437#issuecomment-814330206) is given, but is IMO unacceptable. If I modify my shell in _user_ settings, I shouldn't have to modify a `tasks.json` that many users will use, and whose preferred shells are different. More importantly, a single shell can be specified, so `/bin/sh` won't work for users on Windows, and `cmd.exe` / `pwsh.exe` / whatever won't work for users on Linux. This makes `terminal.integrated.automationProfile.*` essentially useless.

Since `terminal.integrated.automationProfile.*` takes an `args` argument, why add unwanted arguments to it? I understand why defaults may be nice (e.g. set `args` to `["-Command"]` when `path` is `pwsh.exe`), but if preferences are explicitly specified, why append new arguments to them if they only work with a single shell?
Repository: rust
Issue: evaluate: projection obligations are accepted in otherwise coinductive cycles
Labels: A-trait-system,C-bug,T-types,WG-trait-system-refactor

The following compiles but should not
```rust
use std::marker::Unpin;

fn is_unpin<T: Unpin>() {}

trait OtherTrait {
    type Assoc
    where
        Self: Unpin;
}

struct LocalTy;
impl Unpin for LocalTy
where
    Self: OtherTrait<Assoc = LocalTy>,
{}

impl<T> OtherTrait for T {
    type Assoc = T
    where
        Self: Unpin;
}

fn main() {
    is_unpin::<LocalTy>()
}
```
proving `LocalTy: Unpin` results in the following cycle:

- `LocalTy: Unpin`
  - `LocalTy: OtherTrait` (trivially true)
  - `<LocalTy as OtherTrait>::Assoc = LocalTy`
    - `LocalTy: Unpin` (cycle!)

While it's sound for this cycle to be coinductive, with our current rules it should not be. The new solver will also start out with this being inductive. Fulfill correctly detects this as an inductive cycle. **Evaluate does not**.

Note that using that is incredibly fragile as it depends on the following *performance optimization* to avoid fulfill:https://github.com/rust-lang/rust/blob/cce9e72c55994335f8d1dac892cca755b65c8f43/compiler/rustc_trait_selection/src/traits/fulfill.rs#L604-L614

So the following code does result in the expected error :grin: 
```rust
use std::marker::Unpin;

fn is_unpin<T: Unpin>() {}

trait OtherTrait {
    type Assoc
    where
        Self: Unpin;
}

struct LocalTy<'a>(&'a ());
impl<'a> Unpin for LocalTy<'a>
where
    Self: OtherTrait<Assoc = LocalTy<'a>>,
{}

impl<T> OtherTrait for T {
    type Assoc = T
    where
        Self: Unpin;
}

fn main() {
    is_unpin::<LocalTy<'static>>()
}
```
```
error[E0275]: overflow evaluating the requirement `LocalTy<'_>: OtherTrait`
  --> src/main.rs:12:10
   |
12 | impl<'a> Unpin for LocalTy<'a>
   |          ^^^^^
   |
   = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`test1`)
note: required for `LocalTy<'_>` to implement `Unpin`
  --> src/main.rs:12:10
   |
12 | impl<'a> Unpin for LocalTy<'a>
   |          ^^^^^     ^^^^^^^^^^^
note: required by a bound in `OtherTrait::Assoc`
  --> src/main.rs:8:15
   |
6  |     type Assoc
   |          ----- required by a bound in this
7  |     where
8  |         Self: Unpin;
   |               ^^^^^ required by this bound in `OtherTrait::Assoc`
```
Repository: tauri
Issue: [feat] macOS .app.tar.gz and .app.tar.gz.sig should include app version number 
Labels: type: feature request,platform: macOS,status: backlog,type: breaking change

### Describe the problem

I always have to rename macOS bundles when releasing my app. On windows and linux, all bundles start with `AppName_Version_***`, while in macOS it's just `AppName_***`

And this naming is required if you're pushing assets to S3 for the auto-uploader to pick up, as you need distinct names for each version.

### Describe the solution you'd like

Name macOS bundles just like the other platforms.

### Alternatives considered

I can rename it myself, manually or scripted, which is what I do today, but this would be that nice extra DX touch if Tauri would do it automatically :) 

### Additional context

_No response_
Repository: godot
Issue: Root Node size incorrect in release build.
Labels: bug,topic:core,confirmed,topic:dotnet

### Godot version

4 beta 9

### System information

Linux Debian

### Issue description

Im trying to make a programm that runs in window-mode and being resize able. 
When grapping information about the window-size using the get property "size" on the root node.

Building the project in debug, the property "size" returns a e.g. tuple (1920, 1080), using the release build, this same function returns e.g. (1920, 0), meaning that the second value is always 0. 

### Steps to reproduce

Vector2 res = ((Node)GetTree().Get("root")).Get("size").
GD.Print("RES: " + res);

Use this code snipped in a C# Script.
Build the project  as DEBUG and RELEASE.
Watch the output

Debug: 
RES: (1920, **1080**)

RELEASE: 
RES: (1920, **0**)

### Minimal reproduction project

Sorry, no time.
Repository: flutter
Issue: All newish flutter web apps work with keyboard but not mouse on US government computers
Labels: platform-web,a: mouse,browser: edge,P3,team-web,triaged-web

Update: See comments below - I've started to really narrow down the issue. It seems to be with CanvasKit. The app isn't frozen, but mouse interaction isn't functioning. Keyboard interaction works fine, but obviously that isn't a reasonable way to interact.

When opening any new flutter web app on any US government computer (Windows 10 enterprise), the app loads whatever the first screen is and then rapidly freezes so nothing can be interacted with. If you get your mouse over something interactable as it's loading, you can get whatever action would be expected for a brief moment before the freeze (i.e. ink splash hover effect or hover help text). Resizing the screen still moves things around responsively.

Unfortunately, view source and the inspector are now disabled on government computers, so I cannot see if there are any errors.

Notably, this does NOT happen when using Firefox - the apps work normally. It just happens on edge, chrome, and explorer. 

Of course, things work completely fine on non-network computers (i.e. home computer or mobile device using cellular data).

At first I thought this was something about the new app I was building because an old one (build 2 years ago) works fine. However, I tried starting a new web app and used the starting example code, and the same thing happened. I tried flutter upgrade and flutter clean. Flutter doctor gives the checkbox for everything but android and iOS, but this is just for a web app.

I thought maybe this could be related to the index.html service_worker, but I stuck some alerts throughout it and that part works fine.

I thought it could be due to CanvasKit calling an outside domain, but I tried using the HTML option to build and it still didn't work (and converted the plus icon to a square on the demo app).

So, I'm left thinking there's some call to an outside server that the government firewall doesn't like, but even that explanation isn't perfect since it works on Firefox.

I'm sort of at a loss for how to debug this further, since I can't check for errors in the inspector/console. However, I know this is a systemic issue and not just an issue with my code since it happens with a newly built web demo.

I'm open to any other suggestions. I also recognize that there probably isn't anyone here who can help me test, given that it only happens on US government computers.

Thank you for any ideas.
Repository: next.js
Issue: [appDir] Next.js appDir can not resolve virtual CSS files injected by `webpack-virtual-modules`
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.2.0: Tue Nov  8 21:14:46 PST 2022; root:xnu-8792.60.55.131.1~1/RELEASE_X86_64
    Binaries:
      Node: 18.12.1
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: 7.18.1
    Relevant packages:
      next: 13.0.8-canary.4
      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)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://github.com/SukkaW/nextjs-issue-virtual-css

### To Reproduce

```sh
git clone https://github.com/SukkaW/nextjs-issue-virtual-css
cd nextjs-issue-virtual-css
npm run dev
```

Open `https://localhost:3001`

### Describe the Bug

Next.js' fails to collect CSS injected by `webpack-virtual-modules` from `appDir`, resulting in a `Module not found` error:

<img width="979" alt="image" src="https://user-images.githubusercontent.com/40715044/209153007-ea0faf4f-c338-4b14-a279-24ed19d63c25.png">

https://github.com/SukkaW/nextjs-issue-virtual-css/blob/a191e1cc9a0afcae2331b691dd6b11066940679a/next.config.js

----

I am porting a CSS-in-JS Next.js plugin to Next.js appDir (https://github.com/johanholmerin/style9/pull/83). And it is common for CSS-in-JS to utilize `webpack-virtual-modules` to emit virtual CSS files (E.g. [WindiCSS](https://www.npmjs.com/package/windicss-webpack-plugin)).

However, Next.js 13 can not collect virtual CSS from `appDir`. Which would break all existing AoT CSS-in-JS plugins. And I have created a minimal re-production above.

cc @shuding 

### Expected Behavior

The emitted virtual CSS files should be collected and resolved, just like the `pages` dir.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: material-ui
Issue: [Masonry] Add a callback input that receives order of item  
Labels: new feature,package: lab,component: masonry

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Masonry creates items with different order than the index of a loop. Currently, it doesn't seem possible to know the current order of an item without having to hack through it with refs and get the value of order style.

The order is needed for example when I want to display a larger box (a zoomed in image for example) when user hovers over an image items inside Masonry. Depending on current breakpoint and order of item, I need to know if the items is at first column, last column, or somewhere in between in order to correctly position the larger image without causing on overflow.

A callback that receives an `id` and `order` and fires after order is assigned to an item would be very helpful.

### Examples 🌈

_No response_

### Motivation 🔦

_No response_
Repository: pytorch
Issue: Profiler is not properly recording seq number when any key above autograd is used
Labels: oncall: profiler

This is because we don't record function on redispatch. Meaning that the profiler is ONLY seeing the top key.
Anything changing the top key (dispatch subclass, dispatch mode, functorch, etc) will break the assignment.
https://github.com/pytorch/pytorch/blob/55749b9c41857050d4e875d4613c9ba7cddeae02/aten/src/ATen/core/dispatch/Dispatcher.h#L645

cc @robieta @chaekit @aaronenyeshi @ngimel @nbcsm @guotuofeng @guyang3532 @gaoteng-git @tiffzhaofb
Repository: stable-diffusion-webui
Issue: Documentation translation
Labels: documentation

### Is there an existing issue for this?

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

### What would your feature do ?

It would greatly decrease entry threshold for non-native English speakers.

### Proposed workflow

I already started translating docs on my wiki. Mediawiki has powerful [translation module](https://www.mediawiki.org/wiki/Extension:Translate) which lets end users translate portions of pages in small batches without too much technical knowledge. Basically, as long as main page is prepared, it can be translated in other languages, and it can be later edited to keep the versions in different languages consistent. An example of page translated into Russian: https://ai-art-wiki.com/wiki/Stable_Diffusion_webui/Extensions/ru

Should there be a certain style for documentation, or is it just "dump whatever into the pile"? For example, are illustrations supposed to take up entire screen?

Is it ok if it will be written in mediawiki markup instead of md? Translation extension doesn't seem to like markdown too much.

### Additional information

_No response_
Repository: kubernetes
Issue: Unable to Set External Store in client-go
Labels: sig/api-machinery,kind/feature,sig/usability,triage/accepted

### What would you like to be added?

In shared_informer.go, when the resources are fetched from API Server, they are always cached in Memory and there is no mechanism to control that store. 

```
func NewSharedIndexInformer(lw ListerWatcher, exampleObject runtime.Object, defaultEventHandlerResyncPeriod time.Duration, indexers Indexers) SharedIndexInformer {
	realClock := &clock.RealClock{}
	sharedIndexInformer := &sharedIndexInformer{
		processor:                       &sharedProcessor{clock: realClock},
		indexer:                         NewIndexer(DeletionHandlingMetaNamespaceKeyFunc, indexers),
		listerWatcher:                   lw,
		objectType:                      exampleObject,
		resyncCheckPeriod:               defaultEventHandlerResyncPeriod,
		defaultEventHandlerResyncPeriod: defaultEventHandlerResyncPeriod,
		cacheMutationDetector:           NewCacheMutationDetector(fmt.Sprintf("%T", exampleObject)),
		clock:                           realClock,
	}
	return sharedIndexInformer
}
```
It is better to have a provision to supply the store as well something like below.
I would like to write the resource information to disk instead of memory to reduce the memory usage.

```
func (s *sharedIndexInformer) SetStore(store ThreadSafeStore) error {
	s.startedLock.Lock()
	defer s.startedLock.Unlock()

	if s.started {
		return fmt.Errorf("informer has already started")
	}
	s.indexer = NewIndexerWithStore(DeletionHandlingMetaNamespaceKeyFunc, store)
	return nil
}
```




### Why is this needed?

If we use a client-go informer to query Kubernetes resources, the memory utilization is very high for larger clusters.
This would make informers unusable for watching Kubernetes resources.
Repository: go
Issue: runtime: openbsd fork-exec calls exit instead of _exit in failed child
Labels: OS-OpenBSD,NeedsInvestigation,compiler/runtime

As part of work on [CL 459176](https://go.dev/cl/459176) I noticed that the libc ports are calling exit(3) instead of _exit(2). I fixed Darwin in that CL but did not want to touch OpenBSD so close to the release if it wasn't obviously broken. Probably a bad atexit handler could foul up the fork child, and _exit should be used instead. Needs investigation and probably a fix.
Repository: tauri
Issue: [bug] assetScope is inconsistent between absolute and relative paths
Labels: type: bug,priority: 1 high,status: needs more info

### Describe the bug

(Report after discussion on [Discord](https://discord.com/channels/616186924390023171/1055209631921733673) with @FabianLars and @lucasfernog)

When using relative paths with assets protocol in the current tauri version, you need to explicitly specify paths to have files whitelisted.
Indeed, when using absolute path, you use glob patterns:
```
/home/myUser/myapp/* => Works for every file in this folder
/home/myUser/myapp/myimage.png => Works for this specific file
```

But when using a relative to binary path, glob doesn't work
```
mySubfolder/* => 403 for every file in this folder
mySubfolder/myimage.png => Works for this specific file
```

There are possible workaround e.g.:
- Specifiying every file manually inside assetScope array
- Adding the folder at runtime

### Reproduction

1. Create an empty app
2. Enable asset protocol
3. Specify CSP to allow asset URL
4. Put the picture inside the subfolder (in debug CLI, this folder will be relative to src-tauri/, in release mode relative to .exe file)
5. Add this picture to html body (using convertFileSrc to get `asset.localhost` or `asset://` url)
6. Reproduce both scope configuration to notice the bug

### Expected behavior

_No response_

### Platform and versions

Environment
  › OS: Windows 10.0.22621 X64
  › Webview2: 108.0.1462.54
  › MSVC:
      - Visual Studio Build Tools�2019
  › Node.js: 16.17.1
  › npm: 8.15.0
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.24.3
  › rustc: 1.63.0
  › cargo: 1.63.0
  › Rust toolchain: stable-x86_64-pc-windows-msvc

Packages
  › @tauri-apps/cli [NPM]: 1.2.2
  › @tauri-apps/api [NPM]: 1.2.0
  › tauri [RUST]: 1.2.2,
  › tauri-build [RUST]: 1.2.1,
  › tao [RUST]: 0.15.8,
  › wry [RUST]: 0.23.4,

App
  › build-type: build
  › CSP: default-src 'self'; img-src 'self' asset: https://asset.localhost
  › distDir: ../dist
  › devPath: http://localhost:1420/
  › framework: React
  › bundler: Vite

App directory structure
  ├─ .git
  ├─ .github
  ├─ dist
  ├─ node_modules
  ├─ public
  ├─ src
  └─ src-tauri

### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: When zoomed out in PWA mode, the title bar gets smaller than WCO
Labels: bug,titlebar,web

Steps to Reproduce:

1. use vscode.dev 
2. install as pwa
3. enable WCO
4. zoom out

🐛 the titlebar is shorter than the WCO which is a fixed height

This is due to counter-zoom not working in web as we don't know the zoom level from the browser