sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Add support for XTR
Labels: New model

### Model description

XTR (ConteXtualized Token Retriever) is a multi-vector retrieval model that improves efficiency by focusing on retrieving and ranking the most important document tokens. Details are described at https://arxiv.org/abs/2304.01982.

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Implementation for PyTorch: https://github.com/mjeensung/xtr-pytorch
Weight: https://huggingface.co/google/xtr-base-en
Author: @jhyuklee
Repository: flutter
Issue: [palette_generator][web] Reenable web tests.
Labels: platform-web,package,p: palette_generator,e: web_canvaskit,P2,c: tech-debt,team-web,triaged-web

Most of the `package:palette_generator` canvaskit web tests fail in CI, but not locally.

[Errors](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8742855027825842385/+/u/Run_package_tests/Dart_unit_tests_-_web/stdout) seem to point to some sort of wrong decoding of the image colors in CI for some reason (2 colors detected when the image has only one, weird color tones when extracting a palette...)

In order to configure CI to run [web tests using `canvaskit`](https://github.com/flutter/flutter/issues/143543) ([the new default](https://github.com/flutter/flutter/pull/149773) for web applications), and since `package:palette_generator` seems to work normally outside of CI, web tests for `package:palette_generator` were disabled in [this PR](https://github.com/flutter/packages/pull/6879).

This issue is a reminder to:

# Diagnose, and re-enable web platform tests for `palette_generator`.
Repository: pytorch
Issue: Add some way to automatically opt-out of CI features, like TD.
Labels: module: ci,triaged

I've seen three false positives for TD in the past week, which has led to additional hours of work rebasing PRs. If TD isn't completely correct and doesn't have a high accuracy rate, and if a developer is OK with waiting additional time for their tests, then they should be able to opt-out of the feature automatically. 

Today, in order to opt-out of TD, one needs to manually add a `ci-no-td` label to your PR. It's hard for me to remember to add this label to all of my PRs -- could we make this more automatic?

That being said, I'm sympathetic to needing to keep CI costs down and understand that we might not want to add this feature because it makes it easier for developers to opt-out, but please consider the pain from the developer's side.

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: flutter
Issue: `xcresulttool get object` is deprecated in Xcode 16, replace with `xcresulttool get test-results`
Labels: tool,t: xcode,P2,team-ios,triaged-ios

During a verbose Flutter iOS build on Xcode 16 beta 3 I see:
```
/usr/bin/arch -arm64e xcrun xcresulttool get --path /var/folders/fm/wjzsj_z95ydgn4khxqgbtqx000mfq2/T/flutter_tools.PkqAFW/flutter_ios_build_temp_dirFAy4yP/temporary_xcresult_bundle --format json
[ +856 ms] Error: This command is deprecated and will be removed in a future release, --legacy flag is required to use it.
                    Usage: xcresulttool get object [--legacy] --path <path> [--id <id>] [--version <version>] [--format <format>]
                      See 'xcresulttool get object --help' for more information.
```

Introduced in https://github.com/flutter/flutter/pull/92604 to get the Xcode build failure data
https://github.com/flutter/flutter/blob/a99042e10292337e8e40c0009c5796278dd716d3/packages/flutter_tools/lib/src/ios/xcresult.dart#L47-L53

```
$ xcrun xcresulttool get object --help
OVERVIEW: Get Result Bundle Object. This subcommand is deprecated and will be removed in a future release, consider using `xcresulttool get test-report` instead.
```
 `xcresulttool get test-report` doesn't exist, I assume it's a typo for `test-results`:
```
OVERVIEW: Get test results data.

USAGE: xcresulttool get test-results <subcommand>

OPTIONS:
  --version               Show the version.
  -h, --help              Show help information.

SUBCOMMANDS:
  summary                 Get test report summary.
  tests                   Get all tests from test report.
  test-details            Get detailed information about the test.
  activities              Get the activity trees for the specified test. If the test has more than one run, the activity trees for each run will be included.
  insights                Get test report insights.

  See 'xcresulttool help get test-results <subcommand>' for detailed help.
```
Repository: flutter
Issue: Suppress "All plugins found for ios are Swift Packages, but your project still has CocoaPods integration" error for plugin example projects
Labels: tool,P2,team-ios,triaged-ios

I just built `packages/go_router/example` and I see:
```
$ flutter build ios
All plugins found for ios are Swift Packages, but your project still has CocoaPods integration. Your project uses a non-standard Podfile and will need to be migrated to Swift Package Manager manually. Some steps you may need to complete include:
  * In the ios/ directory run "pod deintegrate"
  * Transition any Pod dependencies to Swift Package equivalents. See https://developer.apple.com/documentation/xcode/adding-package-dependencies-to-your-app
  * Transition any custom logic
  * Remove the include to "Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig" in your ios/Flutter/Debug.xcconfig
  * Remove the include to "Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig" in your ios/Flutter/Release.xcconfig

Removing CocoaPods integration will improve the project's build time.
Building com.example.example for device (ios-release)...
```

However, we want plugin authors to continue to support both CocoaPods and SwiftPM for the foreseeable future.  Can we detect the example project is in a plugin directory, and suppress the warning in that case?

/cc @loic-sharma
Repository: flutter
Issue: Investigate APNG straight alpha
Labels: P2,e: impeller,team-engine,triaged-engine

#151210 pop'd up as an issue with unpremultiplied alpha. It turns out APNG is converting frames to and from straight/premultiplied formats.

Maybe: just convert every frame to premultiplied and leave it?
Repository: godot
Issue: Window doesn't resize properly when changing resolution, with "Display Server" set to "Wayland" in Project Settings
Labels: bug,platform:linuxbsd,topic:gui

### Tested versions

- Reproducible in 4.3.rc3, 4.3.rc2, 4.3.rc1, 4.3.beta3, 4.3.beta2 and 4.3.beta1

### System information

Godot v4.3.beta2 - EndeavourOS #1 SMP PREEMPT_DYNAMIC Fri, 05 Jul 2024 22:11:24 +0000 - Wayland - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (nvidia; 555.58.02) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

After changing the "Linux Display Server" in the "Project Settings" to "wayland" (_Project Settings -> Display Server -> Driver.linuxbsd -> wayland_), when changing the project resolution "in-game", in Windowed Mode, the project window doesn't resize and center automatically, contrary to the expected behavior when the "Linux Display Server" is set to "default" or "x11", as demonstrated below.

"Linux Display Server" set to "default":


https://github.com/godotengine/godot/assets/82046471/1a713923-8a78-4511-9473-3cfbec4c82a2



"Linux Display Server" set to "wayland":


https://github.com/godotengine/godot/assets/82046471/a8109c96-d0cd-480d-bce6-a0b0a3e34d78



It does, however, adapt the project window size if changed manually, by dragging the window border.

As this seems to be an issue specifically with Wayland as the compositor, I include here my system information, obtained with _fastfetch_, to better help solve the issue:

![2024-07-10_00-47](https://github.com/godotengine/godot/assets/82046471/7f5575a4-ad17-417a-9927-9435289abd34)


### Steps to reproduce

- Change the "Linux Display Server" in the "Project Settings" to "Wayland" (_Project Settings -> Display Server -> Driver.linuxbsd -> wayland_)
- Change resolution using _get_window().set_size()_
- Repeat but with "Linux Display Server" set to "default" or "x11" (_Project Settings -> Display Server -> Driver.linuxbsd -> default_) to see expected behavior

The MRP included below has a simple option button to set different resolutions for better testing, as well as the background godot icon to help see the issue better.


### Minimal reproduction project (MRP)

[MRPWaylandTesting.zip](https://github.com/user-attachments/files/16152431/MRPWaylandTesting.zip)
Repository: rust
Issue: Tracking issue for CommandExt::show_window
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(windows_process_extensions_show_window)]`

This is a tracking issue for https://github.com/rust-lang/rust/pull/126690.

The idea is to expose STARTUPINFOW.wShowWindow in CommandExt trait to control how a new process' window is displayed on Windows OS (normal, minimized, maximized, etc.)

### Public API

```rust
// std::os::windows::process

#[stable(feature = "windows_process_extensions", since = "1.16.0")]
pub trait CommandExt: Sealed {
  #[unstable(feature = "windows_process_extensions_show_window", issue = "127544")]
  fn show_window(&mut self, cmd_show: u16) -> &mut process::Command;
}
```

### Steps / History

- [x] Implementation: #126690
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: PowerToys
Issue: reenable FancyZone CI
Labels: Issue-Bug,Area-Build,Needs-Triage

### Microsoft PowerToys version

0.82

### Installation method

Other (please specify in "Steps to Reproduce")

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

From https://github.com/microsoft/PowerToys/pull/33746

CI was failing.  

Starting: UI Tests
==============================================================================
Task         : Visual Studio Test
Description  : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test (VsTest) runner. Test frameworks that have a Visual Studio test adapter such as MsTest, xUnit, NUnit, Chutzpah (for JavaScript tests using QUnit, Mocha and Jasmine), etc. can be run. Tests can be distributed on multiple agents using this task (version 2).
Version      : 2.240.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/test/vstest
==============================================================================
Running tests using vstest.console.exe runner.
======================================================
Test selector : Test assemblies
Test filter criteria : undefined
Search folder : D:\a\_work\1\build-x64-Release
Action when minimum tests threshold not met : donothing
Minimum tests expected to be run: 0
vstest.console.exe, specified location : D:\a\_work\_tool\VsTest\17.10.0\x64\tools\net462\Common7\IDE\Extensions\TestPlatform
Run in parallel : false
Run in isolation : false
Path to custom adapters : undefined
Other console options : undefined
Code coverage enabled : false
Diagnostics enabled : false
Rerun failed tests: true
Rerun failed tests threshold: 30
Rerun maximum attempts: 3
Run the tests locally using vstest.console.exe
========================================================
======================================================
##[error]VsTest task failed.
Finishing: UI Tests

### ✔️ Expected Behavior

CI works :)

### ❌ Actual Behavior

CI failing

### Other Software

_No response_
Repository: material-ui
Issue: [material-ui][theme] Lower CSS Specificity for color scheme rules in CSS Vars Theme
Labels: docs,package: material-ui,customization: theme

### Summary

I'm in the process of migrating themes to the new CSS Vars Theme/Provider. I have a light/dark theme which I'm combining per the migration guide into a single theme with dark/light color schemes.

As mentioned in the [docs](https://mui.com/material-ui/experimental-api/css-theme-variables/migration/#4-refactor-custom-styles-to-use-the-attribute-selector), this is causing a pretty big headache with regards to CSS rule specificity (any of the rules I set for the dark theme cannot be overridden in a component's `sx` prop without also specifying the color scheme selector.

I'm wondering if there is a better way that I should approach this or if there's a way that color schemes could be implemented without the extra css specificity.

### Examples

This is a super simple example (not exactly what I'm doing in my theme, but shows the issue):

Let's say we have a rule in the theme for Button to change the background color:

```tsx
styleOverrides: {
    root: ({ theme }) => ({
      backgroundColor: 'primary.main',
      [theme.getColorSchemeSelector('dark')]:{
          backgroundColor: 'primary.light'
      }
    }),
}
```

If I want to override the button background color somewhere in my project:

```tsx
<Button sx={{backgroundColor: 'red'}} />
```

it only works for the light theme (with the old ThemeProvider approach, this would work for both).

To get it to work for the dark theme, I have to add an extra rule, which is a bit clunky:

```tsx
<Button sx={(theme) => ({
    backgroundColor: 'red',
    [theme.getColorSchemeSelector('dark')]:{
        backgroundColor: 'red',
    }
})} />
```

### Motivation

Essentially, I just want it to be easy to override theme styles for a component via sx without having to write a rule for both/all color schemes that I may have.

**Search keywords**: CssVars Theme getColorSchemeSelector specificity override sx
Repository: flutter
Issue: [local_auth] Suggestion for changes in error handling for LocalAuthentication().authenticate()
Labels: platform-ios,platform-mac,p: local_auth,package,c: proposal,P2,team-ios,triaged-ios

### Use case

I'd like to suggest some changes to the error handling for the biometric authentication features provided by the local_auth library.
Currently, there are some differences in how errors are handled on iOS and Android.
I'm particularly focused on one specific situation on iOS: when iOS biometric authentication is voluntarily cancelled by the user.



### Proposal

- For cases when iOS biometric authentication is voluntarily cancelled by the user:  

Currently, when a user voluntarily cancels the iOS biometric authentication, a PlatformException with error `PlatformException(NotAvailable, Authentication canceled., com.apple.LocalAuthentication, null)` is returned on Flutter's end. 

![Simulator Screenshot - iPhone SE (3rd generation) - 2024-07-10 at 11 45 40](https://github.com/flutter/flutter/assets/15142100/1615f91c-3eb7-415a-99a1-3163ad27e7e1)


This PlatformException is indistinguishable from the `PlatformException(NotAvailable, Authentication failure., com.apple.LocalAuthentication, null)`  returned when biometric authentication fails consecutively.
This makes it difficult to properly handle each exception.

However, on Android, when a user voluntarily cancels the authentication, the return value of `LocalAuthentication().authenticate() ` is false.
Therefore, to make it easier to differentiate between the two exceptions, I propose that for voluntarily cancelled iOS biometric authentication, like Android, the return value of `LocalAuthentication().authenticate() ` should be false. 
I believe that this can be achieved by adding [kLAErrorUserCancel](https://developer.apple.com/documentation/localauthentication/klaerrorusercancel?language=objc) to the iOS source code.

I believe that the issue could be resolved by writing a code as follows.
<img width="711" alt="スクリーンショット 2024-07-09 18 57 11" src="https://github.com/flutter/flutter/assets/15142100/ece9a937-f570-40e9-8028-9d5c30f3b4ae">
Repository: rust
Issue: Missed bounds check elimination
Labels: A-LLVM,I-slow,A-codegen,T-compiler,C-bug,C-optimization

On Rust 1.79.0.

```rust
pub const fn missing_bce(v: &[u32]) -> u32 {
    if v.is_empty() {
        return 0;
    }
    let mut sum = 0;
    let mut i = v.len() - 1;
    while i > 0 {
        sum += v[i];
        i -= 1;
    }
    sum
}
```

https://godbolt.org/z/xxjKd5anW

The compiler should be able to elide the bounds check for `v[i]` since `i` is always in [0, v.len()-1].
Repository: puppeteer
Issue: [Bug]: Sticky elements not considered by implicit scroll into view when interacting with an element
Labels: bug,confirmed,P3

### Minimal, reproducible example

```TypeScript
await page.click(".element-which-is-behind-sticky-element");
```


### Error string

no error

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

`page.click` makes sure to scroll the element to click into view.
However, if the element is currently overlapped by a sticky element, puppeteer does not scroll the element into view and therefore clicks on the sticky element.

### Expectation

The element should be scrolled into view and then clicked

### Reality

The sticky element is clicked

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.12.1

### Node version

20.10.0

### Package manager

npm

### Package manager version

10.2.3

### Operating system

Linux
Repository: PowerToys
Issue: Mouse Without Borders is not available
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.82.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

![snipaste_20240710_142944](https://github.com/microsoft/PowerToys/assets/26572584/2ad76fc9-d4ad-495b-b4c8-a7718d57b562)
[PowerToysReport_2024-07-10-14-29-33.zip](https://github.com/user-attachments/files/16156220/PowerToysReport_2024-07-10-14-29-33.zip)


### ✔️ Expected Behavior

The mouse can be slid to another device to perform operations such as copying and pasting.

### ❌ Actual Behavior

The mouse cannot be slid to another device, and operations such as copying and pasting cannot be performed.

### Other Software

_No response_
Repository: go
Issue: proposal: expose time.Location extend string for zone transitions
Labels: Proposal

### Proposal Details

When zoneinfo is needed, it is parsed from the files in the `/usr/share/zoneinfo/` directory.
This implementation works only on Unix systems.
I recently discovered that this value is stored in the `extend` field of the `time.Location` struct.
I use this value to send to other devices.

I propose adding a getter function to retrieve this value:

`func (l *Location) Extend() string`
Repository: next.js
Issue: Next.js Image Component Resizing Issue in Production
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://github.com/darrylmorley/holosun

### To Reproduce

Implement the Next.js Image component in a page using the app router.
Observe the image resizing behaviour in the development environment.
Deploy the application to the production environment.
Observe the image resizing behaviour in the production environment.

### Current vs. Expected behavior

There appears to be an inconsistency with the Next.js Image component when using the app router. Specifically, in the development environment, images are resized appropriately for smaller screens, but this behaviour does not persist in the production environment.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
  Available memory (MB): 15872
  Available CPU cores: 12
Binaries:
  Node: 21.7.3
  npm: 10.8.0
  Yarn: 1.22.22
  pnpm: 9.1.4
Relevant Packages:
  next: 14.2.3 // There is a newer version (14.2.4) available, upgrade recommended!
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: standalone
```


### Which area(s) are affected? (Select all that apply)

Image (next/image)

### Which stage(s) are affected? (Select all that apply)

Other (Deployed)

### Additional context

I am running Nextjs in Docker on a Digital Ocean VPS. Sharp is installed in the project.

![Screenshot 2024-07-09 211901](https://github.com/vercel/next.js/assets/20406137/a4b5bb98-eef7-4005-b60e-ba299e40c8e0)
![Screenshot 2024-07-09 211931](https://github.com/vercel/next.js/assets/20406137/dd7cb9c9-edb0-43a2-9010-21d53cfba19c)
Repository: TypeScript
Issue: Function parameter hover info is inconsistent between contexts
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

“hover”

### 🕗 Version & Regression Information

- This changed between versions 5.4 and 5.5

### ⏯ Playground Link

https://www.typescriptlang.org/play/#code/PTAEFUGcFMCdQCbQGYEsB20Gg5VTQBZAEQA1Q0AbaSAOlAHVpEB7dQTAIAXUAYzc9gtKoTgAtUdAFCcAngAdmABUFzIoALygA3pNB7QkFgFtoylnIBcBgRgDmkgL6TJIUAEl0nOOgCGw0dCUCvCyCrTS8swkpADC-NCeZqoaoElqAGTafEZybAmckAD8VloOTpLIAK7oPJyobERkcZ75ABRyKpAlsNA+CGyUMqAA2gDSOOigANbQMizIjbHxiZ0AulbRzV4r5pBjqw4AlNq6+q76F5egAHqFp3quACoBIpFq86AduzhqHdCcslAAHcApNRCwAG5wOygSFwT6dRzOTbLTguMC3dGgZ7MULMD5fZISUCVWyDYGg0DgqGwGFw+AolqeLExHyTIHMIw+GYicS-HoAoY+NQcyiUQqpHrIOA+ABG5KBqDELEq3AwAhYCEqPBh6rgJgQqB8XipgWCrwUUiAA

### 💻 Code

```ts
// User defined inside MDX files. We don’t control this.
type Props = {
    someProp: string
}

// Internal helper type.
type MDXContentProps = Props & {components?: {}}

function MDXContent(props: {readonly [K in keyof MDXContentProps]: MDXContentProps[K]}) {
    //              ^?
    // The types of props is pretty when hovering over props
}

MDXContent
// ^?
// The type of props is ugly when hovering over MDXContent
// Can we make this pretty as well? Preferably without introducing intermediate helper types.

```


### 🙁 Actual behavior

Hovering over `MDXContent` shows the type of the `props` as written.

![Hover info for `MDXContent` with TypeScript 5.5](https://github.com/microsoft/TypeScript/assets/779047/17cf5021-80a2-41c1-963f-bbf2eb845ecc)



### 🙂 Expected behavior

Hovering over `MDXContent` shows a pretty formatted type of the `props`, just like TypeScript 5.4.

![Hover info for `MDXContent` with TypeScript 5.4](https://github.com/microsoft/TypeScript/assets/779047/3d7fe6d7-65cc-49d9-896d-cf097c13c001)


### Additional information about the issue

I initially [asked for help on Twitter to prettify this](https://x.com/remcohaszing/status/1810664544517120135), not realizing this was a regression in TypeScript 5.5.

Later in the thread I was [asked to report this bug](https://x.com/andhaveaniceday/status/1810677583463506206).
Repository: pytorch
Issue: Extend the device context manager to support existing tensors as well
Labels: feature,triaged,needs research,module: python frontend

### 🚀 The feature, motivation and pitch

Having a context manager that manages the device for all tensors involved within its scope would be a great help, especially in removing device mismatch issues between tensors. 
Moreover, with the current implementation, many developers might at first, think the context manager supports all tensors, until they face a device mismatch error to ultimately find it doesn't, so from a logical and consistency point of view, it makes sense to make this work for all tensors involved.

### Alternatives

Currently, the current device context manager only supports new tensors, and existing tensors need to use .to() method to use the right device. 


### Additional context

_No response_

cc @albanD