sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: Router.createUrlTree(...) creates new UrlTree which reuses UrlSegmentGroups from the Router.currentUrlTree
Labels: area: router,P3

### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

No

### Description

Modfying UrlTree created by Router.createUrlTree(...) can modify (because of shared/reused UrlSegmentGroups) the Router.currentUrlTree which can lead to really hard to debug bugs...

Router.createUrlTree(...) should return a completetely new and indepentent UrlTree or the behaviour with warning should be documented.


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 15.2.10
Node: 20.11.1 (Unsupported)
Package Manager: npm 10.4.0
OS: win32 x64

Angular: 15.2.10
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router

Package                          Version
----------------------------------------------------------
@angular-devkit/architect        0.1502.10
@angular-devkit/build-angular    15.2.10
@angular-devkit/core             15.2.10
@angular-devkit/schematics       15.2.10
@angular-devkit/schematics-cli   15.2.10
@angular/cdk                     15.2.9
@angular/google-maps             15.2.9
@schematics/angular              15.2.10
ng-packagr                       15.2.2
rxjs                             7.8.1
typescript                       4.9.5
```


### Anything else?

_No response_
Repository: PowerToys
Issue: Potential Bug Report for PowerToys File Explorer with iCloud
Labels: Issue-Bug,Needs-Repro,Needs-Triage,Area-App Compat

### Microsoft PowerToys version

v0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

File Explorer: Preview Pane, Settings

### Steps to reproduce


Potential Bug Report for PowerToys File Explorer with iCloud
Title: Sync and Download Issues with iCloud Files on Windows after PowerToys Update

Description:

I am reporting a potential bug in PowerToys File Explorer that appears to be affecting folder synchronization and downloads from iCloud on Windows. After a recent PowerToys update, my iCloud files are no longer downloading or syncing properly between Windows and the cloud.

While I cannot confirm with certainty that PowerToys is the direct cause of the issue, I wanted to bring it to your attention in case there might be a connection. It would be helpful if you could investigate this matter further.

### ✔️ Expected Behavior

Files in the iCloud Drive folder on your Windows PC should continue to sync and download seamlessly between your device and the cloud.

### ❌ Actual Behavior

After updating PowerToys, I am encountering the following issues with iCloud files:

Downloads not initiating: Files are not downloading from iCloud to my Windows PC.
Sync status stuck: The status of existing files in the iCloud Drive folder shows as "Syncing" perpetually, but no progress is made.
These issues were not present before the recent PowerToys update.
![Screenshot 2024-02-27 075942](https://github.com/microsoft/PowerToys/assets/161477289/089bf379-7e5a-42f9-877b-56e52f0e179f)


### Other Software

PowerToys Version: 
Windows Version:  Windows 10 Pro 22H 64-bit operating system, x64-based processor
iCloud Version: 15.0.215
Repository: electron
Issue: [Feature Request]: Clear cache when calling setCertificateVerifyProc
Labels: enhancement :sparkles:,component/session,29-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

29.0.1

### What operating system are you using?

Other Linux

### Operating System Version

Arch Linux

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

When I use the "setCertificateVerifyProc" API to implement certificate pinning, I would expect that from the point in time when I set the certificate verify proc, I get a callback for every request, or at least once for every request with a new domain or an unknown certificate.

### Actual Behavior

If any requests were made prior to the "setCertificateVerifyProc" call, then those verifications will be cached, and the "setCertificateVerifyProc" will never be called for this domain.

This behavior is problematic when trying to implement custom certificate pinning at runtime.

Suggestions:

- Whenever "setCertificateVerifyProc" is called, the certificate verification cache should be cleared

Potential enhancements:

- Offer an API to manually clear the cache.
- Offer an API to specify in the certificate verify proc, whether or not the call to `callback(...)` should be cached or not.
- Offer an API to completely disable caching, such that _every_ request is passed to the verifier. This would also enable verification results per-URL.

### Testcase Gist URL

https://gist.github.com/threema-danilo/25aa1b23e4263b82155d380371b581de

### Additional Information

To test this behavior, load the specified testcase Gist URL in Electron Fiddle. By default, it immediately sets the certificate verify proc. Start the application, wait for a few seconds (the renderer process will send a request every second). Close the window again. In the console output in Electron Fiddle, you will see two domains being requested (one by Chromium, one by our application):

    Certificate verifier called for hostname redirector.gvt1.com
    Certificate verifier called for hostname jsonip.com

Now modify the variable `delayMs` in main.js and set it to 5000. Start the application. Wait 10 seconds. The first ~5 requests will use the default verifier, the following requests will use the custom verifier. Close the window again. No requests will be logged by the custom verifier, because all verifications have been cached.
Repository: transformers
Issue: Add Mixtral Model to Flax
Labels: Feature request

### Feature request

I would like to implement the Mixtral model in Flax

### Motivation

I am in the process of learning Flax and I have almost finished the model conversion to FLAX.

### Your contribution

I could submit a PR with the model implementation
Repository: go
Issue: x/tools/gopls: "could not compute pos to range for %v: %v" bug (reported by telemetry)
Labels: NeedsInvestigation,gopls,Tools,gopls/telemetry-wins

```
#!stacks
"bug.Reportf" &&
("cache.typeErrorsToDiagnostics.func1:+50" ||
  "cache.typeErrorsToDiagnostics.func1:+80" ||
  "cache.typeErrorsToDiagnostics.func1:+74" || 
  "cache.typeErrorsToDiagnostics.func1:+93" ||
  "cache.typeErrorsToDiagnostics.func1:+100")
```

This stack `q8FyvQ` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2024-02-24.json):

Note variants:
- `bug.Reportf("TypeErrorEndPos returned invalid end: %v", err)`
- `bug.Reportf("ReadGo116ErrorData returned invalid end: %v", err)`

```
gopls/bug
golang.org/x/tools/gopls/internal/util/bug.report:+35
golang.org/x/tools/gopls/internal/util/bug.Reportf:+1
golang.org/x/tools/gopls/internal/cache.typeErrorsToDiagnostics.func1:+50
golang.org/x/tools/gopls/internal/cache.typeErrorsToDiagnostics:+119
golang.org/x/tools/gopls/internal/cache.(*typeCheckBatch).checkPackage:+127
golang.org/x/tools/gopls/internal/cache.(*typeCheckBatch).handleSyntaxPackage:+70
golang.org/x/tools/gopls/internal/cache.(*Snapshot).forEachPackageInternal.func2:+1
golang.org/x/sync/errgroup.(*Group).Go.func1:+3
runtime.goexit:+0
```
```
golang.org/x/tools/gopls@v0.15.0-pre.4 go1.21.5 darwin/amd64 vscode (1)
```

Issue created by golang.org/x/tools/gopls/internal/telemetry/cmd/stacks.


Dups: rnoW6w 7zL2qQ pT-4Ug PDXPlA RejVIw
Repository: material-ui
Issue: [docs-infra] API type expander/explorer
Labels: new feature,waiting for 👍,scope: docs-infra

### Summary

We could make it possible to expand the types that we show on the API docs pages. The idea being to expand types until you eventually land on the root docs pages (MDN or React docs).

### Examples

- https://react-spectrum.adobe.com/react-spectrum/ActionGroup.html

https://github.com/mui/material-ui/assets/3165635/ca661a1b-8c1f-4495-a595-4899083c9824




### Motivation

Improve DX. It's a bit similar to #41073 but going above and beyond.

**Search keywords**: API types expander
Repository: material-ui
Issue: [docs-infra] IntelliSense (quick info) on code previews
Labels: new feature,waiting for 👍,scope: docs-infra

### Summary

We could make it possible, like in VS Code, for developers to have access to quick info on our docs editors.

### Examples

Reference points:

1. Ariakit https://twitter.com/diegohaz/status/1681277579725090816

<img width="583" alt="Screenshot 2023-07-19 at 18 53 56" src="https://github.com/mui/material-ui/assets/3165635/5b40d1d6-2c27-4b67-a070-cabf8154cab2">

It can be tested on https://ariakit.org/guide/getting-started.

2. Nuxt, Another one in the same line of thought: https://nuxt.com/docs/getting-started/seo-meta

https://github.com/mui/material-ui/assets/3165635/48fdd88a-d516-41a6-9c64-92d1183ee0ae

But poor execution, it's better UX without it.

3. VS Code, it feels like approaching this like VS Code could be a great UX, e.g.

<img width="699" alt="Screenshot 2023-07-19 at 18 57 35" src="https://github.com/mui/material-ui/assets/3165635/6780d6a5-9a5d-4b9b-a91b-cc7a072088bd">


### Motivation

_No response_

**Search keywords**: IntelliSense quick info
Repository: flutter
Issue: Logs collection on test timeout
Labels: team-infra,P2,triaged-infra

In the run below, a test times out and starts a retry, but the retry runs into the overall job timeout with the result that no logs are collected.

https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20Production%20Engine%20Drone/612193/overview

Would it be possible instead for logs to be collected between test retries?

cc @keyonghan
Repository: godot
Issue: Possible race condition in `Skeleton` handling
Labels: bug,topic:rendering,topic:animation,topic:3d

### Tested versions

4.2.1

### System information

Windows 10/11, Godot 4.2.1, Gles3 compatibility

### Issue description

I have multiple crash dumps from users where the game segfaults somewhere deep in the GPU driver. Most of these are from AMD users but I also got a couple from Nvidia GPUs so this doesn't seem to be vendor related. I am also not 100% sure all of them are using GLES3 but reasonably certain. What I can however see, is that in all crash dumps the godot main thread is currently manipulating `Skeleton3D`, Either in `Skeleton3D::_notification` with `NOTIFICATION_UPDATE_SKELETON` or in `GLES3::MeshStorage::_update_dirty_skeletons`. 

### Steps to reproduce

No idea, I guess trying to rapidly modify Skeleton3D might work but I wasn't able to reproduce this issue so far. I have attached the only model with a skeleton that we are using.

Main thread:
![grafik](https://github.com/godotengine/godot/assets/11277588/e8d100e3-175b-49d3-8c06-e9a2438db0b3)

Crashed thread:
![grafik](https://github.com/godotengine/godot/assets/11277588/c3208ae9-a5f0-4ad2-b9e1-f1fe8b7b551f)

Exception:
![grafik](https://github.com/godotengine/godot/assets/11277588/dae8c926-9e4b-4396-9653-b45424b11210)

Main thread from a different dump (driver call stack was identical):
![grafik](https://github.com/godotengine/godot/assets/11277588/03460943-426c-4782-96e7-34e6f05c5575)


### Minimal reproduction project (MRP)

[robot.zip](https://github.com/godotengine/godot/files/14423031/robot.zip)
Repository: neovim
Issue: Error in inlay hints when enabled not in current window
Labels: bug,lsp

### Problem

When inlay hints are enabled in case target buffer is not in current window, there is the following error:

```
Error in decoration provider vim_lsp_inlayhint.win:
Error executing lua: ...CVKwkT/usr/share/nvim/runtime/lua/vim/lsp/inlay_hint.lua:320: assertion failed!
stack traceback:
        [C]: in function 'assert'
        ...CVKwkT/usr/share/nvim/runtime/lua/vim/lsp/inlay_hint.lua:320: in function <...CVKwkT/usr/share/nvim/runtime/lua/vim/lsp/inlay_hint.lua:311>
```

### Steps to reproduce

- Create a small rust project. For example:
    - File 'Cargo.toml' with the following content:
        ```toml
        [package]
        name = "inlay-hint-repro"
        version = "0.1.0"
        ```
    - File 'hello-world.rs' with the following content:
        ```rust
        fn main() {
            println!("Hello, world!");
        }
        ```
- Make sure [`rust-analyzer`](https://github.com/rust-lang/rust-analyzer) is installed.
- Create a 'init.lua' with the following setup:
    ```lua
    vim.api.nvim_create_autocmd('FileType', {
      pattern = 'rust',
      callback = function()
        vim.lsp.start({
          name = 'rust-analyzer',
          cmd = 'rust-analyzer', -- Use custom path to 'rust-analyzer' executable
          root_dir = '.',
        })
      end,
    })

    vim.api.nvim_create_autocmd('LspAttach', {
      callback = function(args)
        -- Wait for LSP server to start (just to be sure)
        vim.defer_fn(function() vim.lsp.inlay_hint.enable(args.bufnr, true) end, 1000)
      end,
    })
    ```
- Execute `nvim --clean -u <path/to/init.lua>` from the root of sample rust project.
- `:split`
- `:call win_execute(1000, 'edit hello-world.rs')` and wait for one second.

### Expected behavior

Inlay hints can be automatically started even if target buffer is not current (is not in current window).

### Neovim version (nvim -v)

NVIM v0.10.0-dev-2457+ga4b444252

### Vim (not Nvim) behaves the same?

No (doesn't have this functionality)

### Operating system/version

EndeavourOS Linux x86_64 (6.7.6-arch1-1)

### Terminal name/version

st-0.9

### $TERM environment variable

st-256color

### Installation

appimage
Repository: flutter
Issue: Outdated artifacts in `darwin-x64` not deleted
Labels: P2,team-tool,triaged-tool

### Steps to reproduce

1. Checkout flutter stable 3.19.1
2. Run `flutter precache --macos`
3. Observe in `flutter/bin/cache/artifacts/engine/darwin-x64` that `FlutterMacOS.framework` and `FlutterMacOS.framework.zip` are there.
4. Checkout flutter master
5. Run `flutter precache --macos`
6. Observe in `flutter/bin/cache/artifacts/engine/darwin-x64` that `FlutterMacOS.xcframework`, `FlutterMacOS.framework` and `FlutterMacOS.framework.zip` are there.

### Actual results

Once `FlutterMacOS.xcframework` was added, `FlutterMacOS.framework` and `FlutterMacOS.framework.zip` became outdated and should be removed from cache.

### Logs

<details open>
<summary>Logs</summary>

```console

<!-- Paste your logs here -->

```

</details>


### Flutter Doctor output

<details open>
<summary>Doctor output</summary>

```console
[!] Flutter (Channel master, 3.20.0-13.0.pre.50, on macOS 13.6.4 22G513 darwin-arm64, locale en)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.86.1)
[✓] Connected device (4 available)
[✓] Network resources

```

</details>
Repository: storybook
Issue: [BUG] NextJS addon does not get environment variables by default 
Labels: bug,help wanted,nextjs,sev:S3

### Describe the bug

We use the environment variables to set up among others, API url, base url, etc. But when launching the storybook it is unable to find the setup environment variables!


### To Reproduce

Just setup and NextJS project with storybook, define any page or function to use with environment variables, create its story and run it.

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 6.1 Manjaro Linux
    CPU: (16) x64 AMD Ryzen 9 5900HX with Radeon Graphics
    Shell: 5.2.26 - /bin/bash
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    Yarn: 1.22.21 - /usr/bin/yarn
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
    pnpm: 8.15.4 - /usr/bin/pnpm <----- active
  npmPackages:
    @storybook/addon-a11y: 7.6.17 => 7.6.17 
    @storybook/addon-essentials: 7.6.17 => 7.6.17 
    @storybook/addon-interactions: 7.6.17 => 7.6.17 
    @storybook/addon-links: 7.6.17 => 7.6.17 
    @storybook/addon-onboarding: 1.0.11 => 1.0.11 
    @storybook/addon-storysource: 7.6.17 => 7.6.17 
    @storybook/addon-themes: 7.6.17 => 7.6.17 
    @storybook/blocks: 7.6.17 => 7.6.17 
    @storybook/nextjs: 7.6.17 => 7.6.17 
    @storybook/react: 7.6.17 => 7.6.17 
    @storybook/test: 8.0.0-alpha.16 => 8.0.0-alpha.16 
    @storybook/theming: 7.6.17 => 7.6.17 
    eslint-plugin-storybook: 0.8.0 => 0.8.0 
    msw-storybook-addon: 2.0.0-beta.1 => 2.0.0-beta.1 
    storybook: 7.6.17 => 7.6.17 
    storybook-addon-pseudo-states: 2.1.2 => 2.1.2 
    storybook-addon-rtl: 1.0.0 => 1.0.0
```


### Additional context

We are using Storybook as a workaround to test the pages with MSW, using the respective addon.

It could be fixed by [applying this](https://www.rmkennedy.com/posts/storybook-env-vars) on the addon.
Repository: go
Issue: x/tools/gopls: redundant diagnostics due to quick fixes
Labels: NeedsInvestigation,gopls,Tools,Refactoring

The following code causes three "too many returns" diagnostics in gopls. Notably, the present but empty result list is required, so this is probably a low priority bug.

```go
func _() () {
  return 0
}
```

It looks like somehow the "fillreturns" and "noresultvalues" analyzers are colliding, and causing duplication. This may manifest in other ways as we add more quick fixes.
Repository: tauri
Issue: cargo tauri dev errors out when capability is incorrect (but tauri.conf.json does not) [bug] 
Labels: type: bug,status: needs triage

### Describe the bug

When editing tauri.conf.json with tauri dev mode running it gives error messages when you get it wrong, but carries on running. When doing the same for capability files it bombs out. See trace below

### Reproduction

Run `cargo tauri dev`
* Edit capability file to make it invalid, it will bomb out

Run `cargo tauri dev` again
* Edit conf json, it will give error messages but keep watching the files
* Fix it and it will rebuild

### Expected behavior

Editing capability files to make them invalid should not stop `cargo tauri dev`, but should give schema error messages (like config does).

### Full `tauri info` output

```text
yarn run v1.22.21
$ tauri info

[✔] Environment
    - OS: Mac OS 14.3.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 21.6.2
    - pnpm: 8.15.4
    - yarn: 1.22.21
    - npm: 10.2.4

[-] Packages
    - tauri [RUST]: 2.0.0-beta.7
    - tauri-build [RUST]: 2.0.0-beta.5
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.0
    - tauri-cli [RUST]: 1.5.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.3
    - @tauri-apps/cli [NPM]: 2.0.0-beta.6

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
✨  Done in 11.16s.
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: `contextualTitle` not showing on view container
Labels: bug,workbench-views

Type: <b>Bug</b>

Create an extension that contributes the following:

```
  "contributes": {
    "viewsContainers": {
      "panel": [
        {
          "id": "my-panel",
          "title": "Panel Title",
          "icon": "images/my-icon.svg"
        }
      ]
    },
    "views": {
      "my-panel": [
        {
          "id": "foo.bar.myPanel",
          "name": "My View Name",
          "type": "webview",
          "contextualTitle": "Contextual Title",
          "visibility": "visible",
          "retainContextWhenHidden": true
        }
      ]
    }
}
```
When shown in the horizontal Panel, only the Panel Title is seen. When the view is moved to the primary sidebar, the view name is seen. In older versions of VSCode, the view name was displayed.

VS Code version: Code 1.86.2 (Universal) (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:42:13.651Z)
OS version: Darwin x64 23.3.0
Modes:


<!-- generated by issue reporter -->

View in Panel:
<img width="940" alt="image" src="https://github.com/microsoft/vscode/assets/3698180/795c0636-2a79-40bd-8efe-69927ff07ae5">

View in Primary Sidebar:
<img width="495" alt="image" src="https://github.com/microsoft/vscode/assets/3698180/f8f4e7a8-d64f-438c-96c1-b137729abc67">
Repository: flutter
Issue: Feasibility to control subbuild exec_timeout from .ci.yaml
Labels: team-infra,P2,triaged-infra

For targets running subbuilds from an orchestrator, .ci.yaml allows control the orchestrator builder's execution timeout with field `timeout`.

There is no way to control the timeout of the subbuild. The subbuild drone builder is shared across all targets, and is pre-defined from infra/config side:
https://flutter.googlesource.com/infra/+/refs/heads/main/config/engine_config.star#95
which uses the default [`timeout.MEDIUM`](https://flutter.googlesource.com/infra/+/refs/heads/main/config/lib/common.star#275) (60min).

One concern with subbuild timeout change is: it will affect all subbuilds though we may be only interested to control one subbuild of one target.
Repository: vscode
Issue: Menubar disappears, wrong fullscreen detection
Labels: bug,titlebar,menus,web,confirmation-pending,multi-monitor

<!-- ⚠️⚠️ 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.86.2
- OS Version: Ubuntu 22.04

Steps to Reproduce:

1. Go to https://vscode.dev
2. set the `window.menuBarVisibility` setting to `classic`
3. Move the window on a secondary screen without any taskbar
4. The menubar disappears, as if it was in fullscreen mode

![image](https://github.com/microsoft/vscode/assets/23257479/630a216a-8679-4ae3-b963-c3b35b14d1f4)