sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Expose the Scroll Controller of a scrollable TabBar
Labels: c: new feature,framework,f: material design,f: scrolling,c: proposal,P3,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

Exposing the Scroll Controller of a TabBar with isScrollable: true, will let developers apply custom behavior based on the scroll.
In my case, it was necessary to apply a Gradient Mask (Container with LinearGradient in Stack) over the TabBar to indicate to the user that there are more elements out of screen.
Example:
![image](https://user-images.githubusercontent.com/7419147/229357713-f272635b-92e2-4c94-ad57-87d26bed3c92.png)

There was already an issue about it, but it has been closed (https://github.com/flutter/flutter/issues/64880)

## Proposal

It can be made in many ways, two of them can be:

- As a parameter, we can provide our own ScrollController. If null, we can check the presence of a PrimaryScrollController. If null, fallback to the _TabBarScrollController already provided
- Through a key, access to the State of the TabBar, making _scrollController public
Repository: deno
Issue: deno vendor breaks scopes in vendored import map
Labels: bug,vendor

Suppose the following file structure:

```
- main.ts
- a/
  - a.ts
- b/
  - b.ts
- import_map.json
```
with following contents:

```ts
//main.ts
import { a } from './a/a.ts';
import { b } from './b/b.ts';

a();
b();
```

```ts
//a/a.ts
import { version as libVersion } from 'lib.ts';

export function a()
{
	console.log(`I'm module a using lib ${libVersion}`);
}
```

```ts
//b/b.ts
import { version as libVersion } from 'lib.ts';

export function b()
{
	console.log(`I'm module b using lib ${libVersion}`);
}
```

```jsonc
//import_map.json
{
	"imports":
	{
		"lib.ts": "https://static.jaegerma.de/deno-vendor-scope-bug/lib-a.ts"
	},
	"scopes":
	{
		"./b/":
		{
			"lib.ts": "https://static.jaegerma.de/deno-vendor-scope-bug/lib-b.ts"
		}
	}
}
```

When run normally with `deno run --import-map ./import_map.json ./main.ts`, the result is as expected

```
I'm module a using lib a
I'm module b using lib b
```

However, after vendoring with `deno vendor --import-map ./import_map.json ./main.ts`, the new `vendor/import_map.json` is missing the `./b/` scope and instead, the scoped import mapping of `lib.ts` to `lib-b.ts` seems to have overtaken the unscoped mapping to `lib-a.ts`:

```jsonc
//vendor/import_map.json
{
  "imports": {
    "lib.ts": "./static.jaegerma.de/deno-vendor-scope-bug/lib-b.ts",
    "https://static.jaegerma.de/": "./static.jaegerma.de/"
  }
}
```

And when using this faulty import map with `deno run --import-map vendor/import_map.json ./main.ts`, lib-a obviously isn't used anymore:

```
I'm module a using lib b
I'm module b using lib b
```


Deno version: `deno 1.32.3 (release, x86_64-unknown-linux-gnu)`
Repository: opencv
Issue: PyRotationWarper.warp and PyRotationWarper.warpPoint appear to apply different transforms
Labels: bug,category: stitching

### System Information

OpenCV python version: 4.6.0
Operating System / Platform: Ubuntu 18.04.6 LTS
Python version: 3.7.5

### Detailed description

For the same `PyRotationWarper` object and the same K and R matrices, the `warp` and `warpPoint` methods appear to apply quite different transformations to the input. The projected point for a reasonable rotation is very far from the expected location, not even falling close to the projected image. 
![examp](https://user-images.githubusercontent.com/14206643/229371186-8482ce5b-05b4-45d5-98bc-6cc113f68898.png)


### Steps to reproduce

```python 
import cv2
import matplotlib.pyplot as plt
from matplotlib.patches import Circle
from pathlib import Path
import numpy as np
from skimage import data


img = data.cells3d()[34]
img = (255.0 * img / 2**16).astype(np.uint8)[0]
img = cv2.resize(img, (300, 200))
point = [200, 100]
K = np.array(
    [[863.5509, 0.0, 446.5], [0.0, 863.5509, 336.0], [0.0, 0.0, 1.0]], dtype=np.float32
)

R = np.array(
    [
        [0.02657406, 0.99131364, -0.12880631],
        [-0.9981135, 0.01917798, -0.05832428],
        [-0.05534741, 0.13011324, 0.9899532],
    ],
    dtype=np.float32,
)

scale = 890.0
aspect = 1.0

warper = cv2.PyRotationWarper("plane", scale * aspect)

# warp the image
_, warped_image = warper.warp(
    img,
    K,
    R,
    cv2.INTER_LINEAR,
    cv2.BORDER_REFLECT,
)

# warp the input point
warped_pt = warper.warpPoint(
    point,
    K,
    R,
)

w, h = img.shape[:2][::-1]

# check the maps to see where the transformed pixels came from
_, xmap, ymap = warper.buildMaps(
    (w, h),
    K,
    R,
)

# plot the example
fig, axes = plt.subplots(2, 2, figsize=(10, 8))

axes[0, 0].imshow(img, cmap='gray')
imx = axes[0, 1].imshow(xmap)
imy = axes[1, 0].imshow(ymap)
axes[1, 1].imshow(warped_image, cmap='gray')

axes[0, 0].add_patch(Circle(point, 3, color='red',))
axes[1, 1].add_patch(Circle(warped_pt, 3, color='red'))

axes[0, 0].set(title=f"original image; point: {point}")
axes[0, 1].set(title="xmap")
axes[1, 0].set(title="ymap")
axes[1, 1].set(title=f"warped image: point: [{warped_pt[0]:.2f}, {warped_pt[1]:.2f}]")
cbx = plt.colorbar(imx, ax=axes[0, 1], orientation="vertical")
cby = plt.colorbar(imy, ax=axes[1, 0], orientation="vertical")

plt.tight_layout()

```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: react-native
Issue: Command PhaseScriptExecution failed with a nonzero exit code - Error when Archive on Xcode 14.3
Labels: Platform: iOS,Tool: Xcode,Needs: Triage :mag:

### Description

Hi Guys, I'm trying to perform an archive using 0.71.5 but I'm getting an error.

The error occurs in Build phase "[CP] Embed Pods Frameworks", when he runs the script with:

"${PODS_ROOT}/Target Support Files/Pods-MyApp/Pods-MyApp-frameworks.sh"



### React Native Version

0.71.5

### Output of `npx react-native info`

System:
    OS: macOS 13.3
    CPU: (8) arm64 Apple M1
    Memory: 79.22 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
    Watchman: 2022.11.14.00 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /Users/leonardo.felipe/.rbenv/shims/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
    Android SDK:
      API Levels: 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33
      Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0, 33.0.0
      System Images: android-32 | Google APIs ARM 64 v8a, android-33 | Google APIs ARM 64 v8a
      Android NDK: 22.1.7171670
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8609683
    Xcode: 14.3/14E222b - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.14.1 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0 
    react-native: 0.71.5 => 0.71.5 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

### Steps to reproduce

- Create a project in 0.71.5
- Try to perform an archive
- Archive will fail in build phase "[CP] Embed Pods Frameworks"

### Snack, code example, screenshot, or link to a repository


Investigating the problem I noticed that the problem occurs in the "Symlinked..." of the script Pods-MyApp-frameworks.sh
```
  if [ -L "${source}" ]; then
    echo "Symlinked..."
    source="$(readlink "${source}")"
  fi
```

> Workaround is to update all the generated ...-frameworks.sh files to add the -f flag to the call to readlink. In other words, replace
> source="$(readlink "${source}")"
> with
> source="$(readlink -f "${source}")"
> 

The Workaround above was suggested for the issue below and has now been merged into the cocoapods repository.
I believe we will need an RC with this FIX pointing to the new version of cocoapods as soon as it is released.

https://github.com/CocoaPods/CocoaPods/issues/11808
https://github.com/CocoaPods/CocoaPods/pull/11828
Repository: godot
Issue: Opening built-in script line can fail sometimes
Labels: bug,topic:editor

### Godot version

4.0.2 rc

### System information

Windows 10 x64

### Issue description

#74401 introduced a great feature, but I found a case where it fails in less than a minute of using it 🙃
I didn't investigate why exactly it fails. I attached MRP.

CC @stms

### Steps to reproduce

1. Put the MRP scene into any project
2. Do "Search in Files" for `on_dead`
3. Click the result
4. Wrong script is opened
5. `scene\gui\code_edit.cpp:1586 - Index p_line = -63 is out of bounds (get_line_count() = 10).` is printed

### Minimal reproduction project

[CrystalAccess.tscn.txt](https://github.com/godotengine/godot/files/11133234/CrystalAccess.tscn.txt)
Repository: godot
Issue: Cannot switch Audio input device (AudioServer.input_device)
Labels: bug,platform:windows,confirmed,topic:audio

### Godot version

v4.0.1.stable.official [cacf49999]

### System information

Windows 11, Sound card zoom h2n, Sound card Roland duo capture

### Issue description

 I try to switch the audio input using the AudioServer.set_input_device() method. Unfortunately, the input device is always the same.
![Screenshot 2023-04-02 181322](https://user-images.githubusercontent.com/4235617/229379356-5d8f10c4-1919-47bc-b848-f58f6d2173a4.png)


### Steps to reproduce

1. Be sure your computer has at leas 2 sound cards (motherboard + external at minimum)
2. Try to use the AudioServer.set_input_device() to change the device

### Minimal reproduction project

[AudioInputDeviceList.zip](https://github.com/godotengine/godot/files/11133376/AudioInputDeviceList.zip)
Repository: flutter
Issue: Tool snapshot gets rebuilt on each unrelated Git commit
Labels: team,tool,team-tool

When developing changes, I find it helpful to make frequent small commits in Git.  For example I reach a version that works, commit that, then can freely experiment with refactoring it in the knowledge that I can easily reset to that checkpoint if the refactors don't work out.  Or I add debugging code, and when I understand what's happening I commit the debugging code, write some changes and commit those, use the debugging code to help validate my changes or to debug the next problem, and later easily discard the debugging code because it's in a separate commit from the changes I want to keep.

This works great, and a key part of why it works is that Git is fast — a command like `git commit -am 'wip debugging'` is quick to type, and even quicker to execute.

In the Flutter repo, however, there is a speed bump: the next time I run a `flutter` or `dart` command, it will discard the compiled snapshot of the `flutter` tool and rebuild it from scratch.  On my fast desktop, this takes about 11 seconds.  On other machines I use, it's 18-20 seconds.

Most of the time, I haven't touched anything that's an actual input to that compilation: I've made some change in the framework, say, or in its tests, and I just want to run `flutter test` again to test that change.  So it'd be perfectly valid to keep using the old snapshot; it's just a matter of teaching the `flutter` wrapper scripts to recognize that, while still recompiling if I've made changes to the actual tool.

I have an implementation of this, which I'll send as a PR shortly.

For a concrete example of the effect: I used that draft implementation while developing my fix for #85160.  Because that work involved plenty of experimentation and debugging, and changes that will go into about 7 separate PRs, the branch reached a length of 58 commits; including `git reset` to old versions for experiments, and branch rearrangements to pull changes out into presentable PRs, it's involved changing my HEAD commit something like 150 times.  If each of those cost an extra 10-20 seconds, that would have been a quite substantial drag.
Repository: puppeteer
Issue: [Bug]: Offline mode not working on page instances
Labels: bug,upstream,confirmed

### Bug expectation

I navigate Twitter homepage, waited 3 seconds, and try to set the page offline, before navigating Twitter homepage again.
The offline mode did not work.

I got this error instead: Error: net::ERR_INTERNET_DISCONNECTED at https://twitter.com

Am I missing some command line arguments.

The same issue was also found on Windows (I have not tested a Linux distro so far)

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Minimal, reproducible example

```TypeScript
const puppeteer = require('puppeteer');


(async () => {
    const browser = await puppeteer.launch({
        headless: false
    })
    const page = await browser.newPage();
    await page.goto('https://twitter.com')
    await asyncTimeout(3000);
    await page.setOfflineMode(true);
    //await page.setRequestInterception(true);
    await page.goto('https://twitter.com');
}) ();


// Function provided by ChatGPT :-)
async function asyncTimeout(timeout) {
return new Promise(resolve => {
    setTimeout(() => {
    resolve(`Resolved after ${timeout} milliseconds`);
    }, timeout);
});
}
```


### Error string

Error: net::ERR_INTERNET_DISCONNECTED at https://twitter.com

### Puppeteer configuration

_No response_

### Puppeteer version

19.8.2

### Node version

19.6.0

### Package manager

npm

### Package manager version

9.4.0

### Operating system

macOS
Repository: go
Issue: gccgo: memory profiling is always enabled by default
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

1.18 (ish). I'm using fork of gccgo from `devel/gccgo` built for vxworks/ppc, but the bug isn't specific to the fork.

### Does this issue reproduce with the latest release?

n/a

### What operating system and processor architecture are you using (`go env`)?

vxworks/ppc and also linux/amd64

### What did you do?

Any program that does _not_ reference `runtime.MemProfileRate`.

### What did you expect to see?

The runtime _not_ call `profilealloc`. 

### What did you see instead?

The runtime calls `profilealloc`.

---

I noticed this while working on a fork of gccgo build for vxworks/ppc. This bug really isn't specific to gccgo—I believe it will occur any time the external linker is used since CL 299671 only applies to `cmd/link`. Of course, since we're using a fork we could just disable this and we have. But it means that anybody using gccgo (or an external linker) gets hit with a certain [performance penalty](https://commaok.xyz/post/memprofilerate/) unless they remember to set `runtime.MemProfileRate` to zero. It's a relatively minor 'bug', but little things add up quickly on constrained platforms.

/cc: @elagergren-spideroak
Repository: next.js
Issue: ValidationError if project folder name contains exclamation mark
Labels: bug

### Verify canary release

- [ ] 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 Pro
    Binaries:
      Node: 18.15.0
      npm: N/A
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.2.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.2.4", newest: "13.2.5-canary.27".
```


### 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/vercel/next.js

### To Reproduce

yarn dev or yarn build

### Describe the Bug

ValidationError: Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.

### Expected Behavior

No error

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

_No response_

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

_No response_
Repository: rust
Issue: #[deny(unknown_lints)] doesn't apply to code from macros from external crates
Labels: A-lints,A-macros,T-compiler,L-unknown_lints

Code generated from `proc_macro` (or parts coming from `proc_macro` and incorporated (invoked by) a macro by example) doesn't get checked 
by `#[deny(unknown_lints)]` (and friends). (Update: And the same from `macro_rules` in external crates - see @clubby789's explanation below.) 

Can/should Rust report that? If not, could we document this?

That is even more confusing, because code coming from pure `macro_rules!`-based macros IS checked by `#[deny(unknown_lints)]`. (Update: Only if `macro_rules` is in not in an external crate.)

For an OLDER example, see https://github.com/peter-kehl/nonexisting_lint_from_proc_macro/tree/4f564d464d218bc2f0b211bd6d0e53075a5761b2/proc_mac/src/lib.rs for the proc macro, and https://github.com/peter-kehl/nonexisting_lint_from_proc_macro/tree/4f564d464d218bc2f0b211bd6d0e53075a5761b2/use_cases/src/lib.rs for its "consumer".

(Same on `1.68.2` and `1.70.0-nightly`.)
(Updated; BUT I will provide a smaller example in a separate comment.)
Repository: flutter
Issue: [camera] Camera and microphone is still accessing after dispose. [Safari Mobile]
Labels: platform-web,p: camera,package,has reproducible steps,P2,browser: safari-ios,found in release: 3.7,found in release: 3.9,team-web,triaged-web

## Steps to Reproduce

1.  Run the [sample code](https://pub.dev/packages/camera/example) in Mobile Safari.
2. Set screen 1 as Home, screen 2 as Camera.
3. Enter screen 2 and allow access to camera and microphone
4. Back to Screen 1.

**Expected results:** <!-- what did you want to see? -->
Camera and Microphone shouldn't be accessing anymore.

**Actual results:** <!-- what did you see? -->
Camera and Microphone is still using. 


https://user-images.githubusercontent.com/106730407/229411228-ed0596d8-5fb0-4cc0-8ee6-3e98ec688737.mp4



**Build Version**
Flutter (Channel stable, 3.7.7, on macOS 13.2.1 22D68 darwin-x64, locale en-MY)
Xcode - develop for iOS and macOS (Xcode 14.2)
iOS 16.4

camera : 0.10.3+2
Repository: PowerToys
Issue: Programmable Layers For The Keyboard
Labels: Needs-Triage

### Description of the new feature / enhancement

It would be great to have the ability to program the keyboard with layers so you have many different configurations available rather than just the basic keyboard layout.

Cheers,

### Scenario when this would be used?

When programming for shortcuts etc... most advanced mechanic keyboard support it, but there are some good keyboards which do not, hence this request.

### Supporting information

_No response_
Repository: pytorch
Issue: how can i load seperate pytorch_model.bin?
Labels: module: serialization,triaged

If you have a question or would like help and support, please ask at our
[forums](https://discuss.pytorch.org/).

If you are submitting a feature request, please preface the title with [feature request].
If you are submitting a bug report, please fill in the following details.

## Issue description

Provide a short description.

## Code example

Please try to provide a minimal example to repro the bug.
Error messages and stack traces are also helpful.

## System Info
Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

- PyTorch or Caffe2:
- How you installed PyTorch (conda, pip, source):
- Build command you used (if compiling from source):
- OS:
- PyTorch version: 1.13.1
- Python version: 3.8
- CUDA/cuDNN version:
- GPU models and configuration:
- GCC version (if compiling from source):
- CMake version:
- Versions of any other relevant libraries:

I have a separate binary file (pytorch_model-00001-of-00002.bin, pytorch_model-00002-of-00002.bin, pytorch_model.bin.index.json). 
When I substitute path into torch.load, I get an error.
How can I get this into torch.load? 


cc @mruberry
Repository: PowerToys
Issue: 快捷键映射问题
Labels: Issue-Bug,Product-Keyboard Shortcut Manager

### Microsoft PowerToys version

0.68.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

键盘管理器里，快捷键映射，win+tab快捷键映射至F3键没有反应，映射至别的快捷键也不成功

### ✔️ Expected Behavior

键盘管理器里，快捷键映射，win+tab快捷键映射至F3键没有反应，映射至别的快捷键也不成功

### ❌ Actual Behavior

键盘管理器里，快捷键映射，win+tab快捷键映射至F3键没有反应，映射至别的快捷键也不成功

### Other Software

键盘管理器里，快捷键映射，win+tab快捷键映射至F3键没有反应，映射至别的快捷键也不成功
Repository: rust
Issue: Compilation error when implementing `From` using a concrete associated type from another crate
Labels: A-associated-items,C-bug,T-types,A-coherence

I have the following files from 2 crates:

```rust
// dep/src/lib.rs

pub trait Wrapped {
    type WrappedType;
}

pub struct W3;
pub struct S3;

impl Wrapped for S3 {
    type WrappedType = W3;
}
```

```rust
// main/src/lib.rs

use dep::Wrapped;

struct W;
struct S;

impl Wrapped for S {
    type WrappedType = W;
}

struct W2;
struct S2;

impl Wrapped for S2 {
    type WrappedType = W2;
}

// This works
impl From<<S2 as Wrapped>::WrappedType> for W {
    fn from(value: W2) -> Self {
        todo!()
    }
}

// This doesn't work
impl From<<dep::S3 as Wrapped>::WrappedType> for W {
    fn from(value: dep::W3) -> Self {
        todo!()
    }
}
```

Currently I have the following error:
```
error[E0119]: conflicting implementations of trait `std::convert::From<W>` for type `W`
  --> main/src/lib.rs:23:1
   |
23 | impl From<<dep::S3 as Wrapped>::WrappedType> for W {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `core`:
           - impl<T> std::convert::From<T> for T;
```

I expected that `<dep::S3 as Wrapped>::WrappedType` would be resolved to a single type like `<S2 as Wrapped>::WrappedType>`, and that the code would compile.

### Context

I'm using `dep::S3` and `W` as the inputs of a proc-macro, and I would like to generate `impl From<dep::W3> for W` inside the proc-macro, but without mentioning `dep::W3` explicitely.

### Meta
`rustc --version --verbose`:
```
rustc 1.70.0-nightly (0599b6b93 2023-04-01)
binary: rustc
commit-hash: 0599b6b931816ab46ab79072189075f543931cbd
commit-date: 2023-04-01
host: x86_64-unknown-linux-gnu
release: 1.70.0-nightly
LLVM version: 16.0.0
```
Repository: godot
Issue: [Godot 4.x] Memory leak
Labels: topic:editor,needs testing

### Godot version

Any godot 4.x is affected. I didn't check 3.x

### System information

Debian 11

### Issue description

The Godot editor have memory leak. 
To check it run any project and wait for it (look at its process) 
It grow ~20Mb hour.


### Steps to reproduce

See before.

### Minimal reproduction project

NA