sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Make `PointerInterceptor` part of the Framework
Labels: c: new feature,framework,customer: google,c: proposal,P2,team-framework,triaged-framework

### Use case

Because of how pointer events are handled by Flutter when interacting with platform views, web (and recently iOS) apps need to rely on the `PointerInterceptor` plugin to function as expected:

<p align="center"><img width="573" alt="Screenshot 2024-02-28 at 4 17 38 PM" src="https://github.com/flutter/flutter/assets/1255594/55910203-cecc-4180-a0ca-f9f9a4cff8bc"></p>

* See more in the README: https://pub.dev/packages/pointer_interceptor

Pointer Interceptor helps up to certain points. For apps where there's a big platform view in the background (imagine Google Earth), keeping track of all the elements that might be overlaid on top of it can be costly.

### Proposal

Consider moving the `PointerInterceptor` widget inside the framework, and make use of it in certain critical parts that are hard to control for end users, like the ModalBarrier #93887, ListView, Navigation drawer, so those work as expected even if there's a platform view under them.
Repository: ollama
Issue: Can we have the newest 1-bit model
Labels: model request

The Era of 1-bit LLMs: All Large Language Models are in 1.58 Bits
https://thegenerality.com/agi/
https://arxiv.org/abs/2402.17764
Repository: deno
Issue: VSCode Jupyter integration: ts and deno enabled at the same time?
Labels: bug,lsp

```
❯ deno --version
deno 1.41.0 (release, aarch64-apple-darwin)
v8 12.1.285.27
typescript 5.3.3

❯ code --version
1.87.0
019f4d1419fbc8219a181fab7892ebccf7ee29a2
arm64
```

I created a new Jupyter notebook in VSCode and switched kernel to Deno.

It looks like Deno is working -- but I'm also getting TS errors that I shouldn't be getting with Deno.

Am I doing something wrong?

Sample code:

```typescript
const fileContents = await Deno.readTextFile("");
```

<img width="580" alt="image" src="https://github.com/denoland/deno/assets/1523306/2089222f-ff80-49f9-9f10-7ef0e26dc6f7">


<img width="517" alt="image" src="https://github.com/denoland/deno/assets/1523306/4d37da24-1ce8-4fd2-9adb-a744beb0bf6c">
Repository: go
Issue: all: failures on `darwin/amd64` with `device error`
Labels: OS-Darwin,Builders,NeedsInvestigation

```
#!watchflakes
post <- goos == "darwin" && goarch == "amd64" && log ~ `device error`
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8754905617733969537)):

    === RUN   TestScript/list_symlink_issue35941
    === PAUSE TestScript/list_symlink_issue35941
    === CONT  TestScript/list_symlink_issue35941
        script_test.go:132: 2024-02-27T21:30:04Z
        script_test.go:134: $WORK=/Users/swarming/.swarming/w/ir/x/t/cmd-go-test-4169637290/tmpdir2541861119/list_symlink_issue359413654838424
        script_test.go:156: 
            PATH=/Users/swarming/.swarming/w/ir/x/t/cmd-go-test-4169637290/tmpdir2541861119/testbin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/cache/tools/bin:/Users/swarming/.swarming/w/ir/bbagent_utility_packages:/Users/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/Users/swarming/.swarming/w/ir/cipd_bin_packages:/Users/swarming/.swarming/w/ir/cipd_bin_packages/bin:/Users/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/Users/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/Users/swarming/.swarming/w/ir/cache/cipd_client:/Users/swarming/.swarming/w/ir/cache/cipd_client/bin:/Users/swarming/.swarming/cipd_cache/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
            HOME=/no-home
            CCACHE_DISABLE=1
            GOARCH=amd64
    ...
            [condition not met]
            > env GO111MODULE=off
            # Issue 35941: suppress symlink warnings when running 'go list all'. (6.681s)
            > symlink goproj/css -> $GOPATH/src/css
            > go list all
            [stderr]
            ../../../../../../w/goroot/src/cmd/link/internal/ld/main.go:39:2: read /Users/swarming/.swarming/w/ir/x/w/goroot/src/cmd/link/internal/benchmark/bench_test.go: read /Users/swarming/.swarming/w/ir/x/w/goroot/src/cmd/link/internal/benchmark/bench_test.go: device error
            read /Users/swarming/.swarming/w/ir/x/w/goroot/src/cmd/relnote/relnote_test.go: read /Users/swarming/.swarming/w/ir/x/w/goroot/src/cmd/relnote/relnote_test.go: device error
        script_test.go:156: FAIL: testdata/script/list_symlink_issue35941.txt:7: go list all: exit status 1
    --- FAIL: TestScript/list_symlink_issue35941 (6.69s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: rust
Issue: Error when failing to find macro should suggest `pub(crate)`
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics

### Code

```Rust
mod macros {
    macro_rules! greet {
        () => { println!("Hello, world!"); }
    }

    //pub(crate) use greet;
}

fn main() {
    macros::greet!();
}
```


### Current output

```Shell
error[E0433]: failed to resolve: could not find `greet` in `module`
  --> src/main.rs:10:13
   |
10 |     module::greet!();
   |             ^^^^^ could not find `greet` in `module`

warning: unused macro definition: `greet`
 --> src/main.rs:2:18
  |
2 |     macro_rules! greet {
  |                  ^^^^^
  |
  = note: `#[warn(unused_macros)]` on by default
```


### Desired output

```Shell
error[E0603]: macro `greet` is private
  --> src/main.rs:10:13
   |
10 |     module::greet!();
   |             ^^^^^ private macro
   |
note: the macro `greet` is defined here
  --> src/main.rs:2:5
  |
2 |     macro_rules! greet {
  |     ^^^^^^^^^^^^^^^^^^
  = help: consider adding `pub(crate) use greet;` to re-export the macro
```

(This *could* be an actual rustfix suggestion, though it should not have high certainty since they may not have intended to use a private macro.)

### Rationale and extra context

We already give a better error for attempting to call a private function; this applies the same logic to private macros.

### Rust Version

```Shell
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-unknown-linux-gnu
release: 1.76.0
LLVM version: 17.0.6
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":null}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Accessibility reader (Talkback, Voiceover) won't scroll through ListView if unfocusable item occupies the whole space 
Labels: platform-android,platform-ios,framework,a: accessibility,f: scrolling,has reproducible steps,P2,customer: huggsy (g3),team-framework,triaged-framework,found in release: 3.19,found in release: 3.20

## Summary

Should be able to navigate through the contents of a ListView or similar scrollable widget with TalkBack. Insted, focus gets locked out of the scrollable area. See internal bugs b/326396034 and b/326367404 for app-specific context.

## Reproduction 

The customer could reproduce the issue with the following code snippet based on the internal minimal sample app. Run the app on Android, enable TalkBack, and use horizontal swipes to navigate through the UI. Now rotate the device to landscape and repeate the process. After a few swipes, the UI will get locked in a state where the green box occupies the entirety of the scroll area and it is impossible to swipe to the "top" or "bottom" widgets.

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(useMaterial3: false),
      title: 'Flutter Demo',
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title, style: TextStyle(fontFamily: 'ProductSans')),
      ),
      body: ListView(
        children: const [
          Text('Top'),
          AspectRatio(aspectRatio: 1, child: ColoredBox(color: Colors.green)),
          Text('Bottom'),
        ],
      ),
    );
  }
}
```

See repro video: 
https://github.com/flutter/flutter/assets/6869388/f3c721b5-0065-44f1-961c-74bc281c612d

## Priority

This is broken in production for at least one Google app.
Repository: flutter
Issue: [CameraX] Option to choose ResolutionStrategy
Labels: p: camera,package,c: proposal,P3,team-android,triaged-android

### Use case

As per #141766 the Resolution strategy for CameraX is set to ResolutionStrategy.fallbackRuleClosestLowerThenHigher which is (apparently) the default behaviour. 

In some cases this might not be a problem - however, in practice I have found it sometimes has such a large effect that the Camera becomes unusable. 

We have created a barcode scanner using the google ml_kit which then detects the barcode in the image stream, on some devices the resolution fallback is so much lower that the image is completely unusable for image recognition and the barcodes completely fail to read. 

For example on my Google Pixel 7 - the "lower" resolution can still detect barcodes successfully. On my Xiaomi Pad 5 it cannot read barcodes at all with the lower resolution which the CameraX plugin falls back to. 

I do not want to force a higher resolution preset on ALL devices - as this also comes with a performance hit. 

I do not have the same problem with the default camera_android package, however there is java crash which occurs occasionally with that package which is also supposedly solved with CameraX. 

I had filed this as an issue before which was marked as a dupe of the above case, but we need a solution for this as it's something that makes the CameraX unusable in this application at this time. The case has been closed with updated documentation - but that doesn't solve the problem. 

### Proposal

I would propose adding an optional parameter to the CameraController to allow the user to override the resolution strategy default. 

The options should be at least somewhat consistent with the available options within the CameraX specification: https://developer.android.com/reference/androidx/camera/core/resolutionselector/ResolutionStrategy

e.g. 
CameraController(
    CameraDescription description,
    this.resolutionPreset, {
    this.enableAudio = true,
    this.imageFormatGroup,
    **this.resolutionStrategy**
  })
Repository: pytorch
Issue: FSDP: automatic instantiation on GPUs (aka zero.Init)
Labels: triaged,needs research,module: fsdp

### 🚀 The feature, motivation and pitch

moving from [slack discussion](https://pytorch.slack.com/archives/C3PDTEV8E/p1709153741504309) 

How can FSDP shard a model directly to GPUs during model instantiation?

This is critical for instantiating huge models.


### Alternatives

In Deepspeed this exists since day 0 of the framework using [`zero.Init`](https://deepspeed.readthedocs.io/en/latest/zero3.html#constructing-massive-models)

This feature is integrated into HF Transformers' `from_pretrained` that instantiates the model directly on GPUs - [here](https://github.com/huggingface/transformers/blob/2209b7afa04b3a6366350065f541e9248d6663c2/src/transformers/modeling_utils.py#L1301)

There is an emerging need to control when this should be activated and when
not as we now have many situations with multiple concurrent models and this
current setup no longer works well.So I thought that HF Transformers should
gather at least some needs of various frameworks - Deepspeed ZeRO, FSDP and
may be others where `from_pretrained` provides hooks into the model
instantiation stage. The 2 needs are:  

  1. yes/no activate flag
  2. framework provided context to instantiate in - so `zero.Init` would be just one of them

The intention is that the user won't need to do anything special when they
create the model. The framework would register with HF Transformers everything
it needs to do it smoothly and correctly.



### Additional context

on slack Andrew Gu posted:

> If you specify the  `device_id` arg, FSDP should move the unsharded module to GPU before sharding so that the sharding ops are fast (but still requiring CPU init and copy H2D). Otherwise, the only other way to initialize _and_ shard on GPU is to do so-called “manual wrapping”, which was the common approach from Fairscale. I do not think that would work with HF transformers.

> For manual wrapping, you have to call `FullyShardedDataParallel(module, …)` on
`module` immediately after it was constructed to avoid spiking memory. This is
intrusive to the model definition and not acceptable in many cases. I am just
mentioning it since it can be the fastest init supported.  

    
    
    # Example manual wrapping with `enable_wrap`/`wrap`
    # Wrap each transformer block and the root
    from torch.distributed.fsdp import enable_wrap, wrap
    
    class Transformer(nn.Module):
      def __init__(self, ...):
        layers = []
        for layer_id in range(num_layers):
          layer = TransformerBlock(...)
          layer = wrap(layer, ...)
          layers.append(layer)
        self.layers = nn.ModuleList(layers)
        
    with torch.device("cuda"):
      with enable_wrap(wrapper_cls=FullyShardedDataParallel, **fsdp_kwargs):
        model = Transformer(...)
        wrap(model)



cc @zhaojuanmao @mrshenli @rohan-varma @awgu @fegin @penguinwu @kwen2501
Repository: pytorch
Issue: FSDP: unsharded gradients accessor
Labels: triaged,module: fsdp

### 🚀 The feature, motivation and pitch

moving from [slack discussion](https://pytorch.slack.com/archives/C3PDTEV8E/p1709153741504309) 

How do I access full unsharded gradients under FSDP, these are critical for debugging live trainings, especially when things go south.

Andrew Gu replied:

> The support is not great. I added a `with_grads=True` option to `summon_full_params()` specifically  for `use_orig_params=True` for debugging. There might be some rough edges there.


### Alternatives

Deepspeed ZeRO provides accessors for unsharded grads, fp32 params and optim states - the full doc is [here](https://deepspeed.readthedocs.io/en/latest/zero3.html#debugging)

2. deepspeed.utils.safe_get_full_fp32_param(param)
3. deepspeed.utils.safe_get_full_grad(param)
4. deepspeed.utils.safe_get_full_optimizer_state(param, optim_state_key)
5. deepspeed.utils.safe_get_local_fp32_param(param)
6. deepspeed.utils.safe_get_local_grad(param)
7. deepspeed.utils.safe_get_local_optimizer_state(param, optim_state_key)


cc @zhaojuanmao @mrshenli @rohan-varma @awgu @fegin @penguinwu @kwen2501
Repository: go
Issue: cmd/compile/internal/ssa: TestStmtLines failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "cmd/compile/internal/ssa" && test == "TestStmtLines"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/042d76f4d4e1b24227e548c23ce3e53f1d3487b0)):

    --- FAIL: TestStmtLines (29.29s)
        exec.go:193: test timed out while running command: /tmp/buildlet/go/bin/go build -ldflags=-w=0 -o /tmp/buildlet/tmp/TestStmtLines3956147870/001/test.exe cmd/go
        stmtlines_test.go:83: go build: exit status 2
            SIGQUIT: quit
            PC=0x7ff80eb591fe m=0 sigcode=0
    
            goroutine 0 gp=0x84f6900 m=0 mp=0x84f8600 [idle]:
            runtime.pthread_cond_wait(0x84f8c48, 0x84f8c08)
            	runtime/sys_darwin.go:507 +0x2e fp=0x7ff7b9555360 sp=0x7ff7b9555338 pc=0x7a06fee
            runtime.semasleep(0xffffffffffffffff)
    ...
            r11    0x246
            r12    0x16
            r13    0x0
            r14    0x5d0100005e00
            r15    0x3100
            rip    0x7ff80eb591fe
            rflags 0x247
            cs     0x7
            fs     0x0
            gs     0x0


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: godot
Issue: Vehiclebody3D sliding down slope when parked
Labels: bug,topic:physics,topic:3d

### Tested versions

- Tested in 4.2.1 stable

### System information

Windows 10 - Godot 4.2.1 stable - compatibility

### Issue description

A Vehiclebody3D parked sideways on a slope will slide down. Depending on gravity, friction, roll influence and spring settings it will slide more or less but it will never stand still unless the gravity is 0.
It's even possible with the right combination of settings to make the vehicle slide up the slope. This is without any engine force or steering applied!

![slope demo](https://github.com/godotengine/godot/assets/25064539/e460d86e-8386-484f-9902-64ccfbb7fb36)



### Steps to reproduce

Run the demo project

### Minimal reproduction project (MRP)

[VehicleBody Slope.zip](https://github.com/godotengine/godot/files/14443066/VehicleBody.Slope.zip)
Repository: PowerToys
Issue: Crosshairs already built into 24H2 26063.1?
Labels: Issue-Docs,Resolution-Helped User

### Provide a description of requested docs changes

I am just coming across PowerToys Crosshair, a feature which now seems to be built into this build as well, but I would like to know how to turn it off and on again. What is the hotkey to enable and disable this? It seems like a very useful feature which I would most likely use regularly, but I would like to know what is the combination for the built in version as well, as I could not find any resource on the web stating what it is.

Thanks
Repository: vscode
Issue: Add applied changes in diff editor to undo stack
Labels: bug,diff-editor

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Every change applied from one file to another in diff editor should be undoable, currently you can only undo all.
Repository: flutter
Issue: Wrong display on Android with PlatformViewLink
Labels: platform-android,framework,a: platform-views,has reproducible steps,P2,team-android,triaged-android,found in release: 3.19,found in release: 3.20

### Steps to reproduce

1.Put two PlatformViewLink in a Stack.
2.Change the order of the views in Stack.

### Expected results

The green view is at the bottom, it will display on the top after changed the order.

<div style="display: flex; justify-content: center;">
    <img src="https://github.com/flutter/flutter/assets/107314156/50da5959-22f4-4ae9-a8b8-b5c28bc94773" alt="before_change" width="300"/>
    <img src="https://github.com/flutter/flutter/assets/107314156/a7cb72d0-81b8-4349-a512-f4cab5ce679e" alt="expected" width="300"/>
</div>

### Actual results

Actually the green view is still at the bottom.

<div>
    <img src="https://github.com/flutter/flutter/assets/107314156/693fa3ae-e181-4f43-97e1-db76392a9aad" alt="before_change" width="300"/>
</div>


### Code sample

<details open><summary>Code sample</summary>

[project](https://github.com/m8417/flutter-GLTest)

</details>


### Screenshots or Video

_No response_

### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 3.20.0-15.0.pre.20, on Microsoft Windows [版本 10.0.19044.4046], locale zh-CN)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[√] Chrome - develop for the web
[√] Android Studio (version 2022.2)
[√] Connected device (3 available)
[√] Network resources

• No issues found!
```

</details>
Repository: vscode
Issue: VSCode freezes/blocks at startup
Labels: freeze-slow-crash-leak

Hello,

VSCode is very long to start, juste showing a blank window for up to 10 sec. Sometimes, I also have a popup window proposing to kill/restart or wait.
Also, after VSCode is finally started, after a couple of minutes, it freezes for again few seconds (10-20) before being fully operationnal.
This behavior only concern the 1st open window. If I open a new one, no issue.
Also, if I close all the open windows, and then open again VSCode, the issue is reproduced.

I have tried tu play with different options like `--disable-extensions` and `--disable-gpu`, but without any improvements...
I have also tried to fully remove VSCode and the extensions, and then reinstall, but I still have the same behavior.

My system is:

```
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.4 LTS
Release:	22.04
Codename:	jammy
$ uname -a
Linux LPFR0237 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```

## System Info

* Code: 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2)
* OS: linux(6.5.0-21-generic)
* CPUs: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz(8 x 4075)
* Memory(System): 31.06 GB(27.07GB free)
* Memory(Process): 284.92 MB working set(194.28MB private, 0.97MB shared)
* VM(likelihood): 0%
* Initial Startup: true
* Has 0 other windows
* Screen Reader Active: false
* Empty Workspace: false


## Attached profiling files (with option `--prof-startup`)

[prof-uwGrxS2H.renderer.cpuprofile.txt](https://github.com/microsoft/vscode/files/14444635/prof-uwGrxS2H.renderer.cpuprofile.txt)
[prof-uwGrxS2H.main.cpuprofile.txt](https://github.com/microsoft/vscode/files/14444634/prof-uwGrxS2H.main.cpuprofile.txt)

## Attached generated report (with option `--prof-startup`)

[report.md](https://github.com/microsoft/vscode/files/14444720/report.md)
Repository: ollama
Issue: Use cloudflared Tunnels to publish ollama service ports, with clients returning with no messages
Labels: question

The cloudflared Tunnels are used to publish the ollama service port, and the client uses the enchanted-llm app for the dialogue, with no messages returned. But without cloudflared Tunnels, everything works fine. Is ollama using streaming dialogue using websocket?
Repository: pytorch
Issue: [memory profiling] about supporting the C++ Call Stack on the ARM Architecture
Labels: feature,module: cuda,triaged,OSS contribution wanted,oncall: profiler,module: arm

### 🚀 The feature, motivation and pitch

I noticed that PyTorch provides a way to generate memory snapshots that record the state of allocated CUDA memory at any point in time，and this is a really nice feature.
I would also like to implement this in my code, but I found out that getting the c++ call stack is only supported on x86.https://github.com/pytorch/pytorch/blob/14c5ebc8a15419717369038212c61f0c9e0638a2/torch/csrc/profiler/unwind/unwind.cpp#L10
This greatly limits my use case, so I'm wondering if it's possible to do the same on arm. Or is there a simple solution to replace it? such as using  execinfo.h's backward.
I look forward to your reply. Thank you.

### Alternatives

_No response_

### Additional context

_No response_

cc @ptrblck @msaroufim @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise @malfet @snadampal @nbcsm @gaoteng-git @tiffzhaofb