sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Reduce expandable FAB size to allow floating snack bars
Labels: c: new feature,f: material design,c: proposal,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I use the [Expandable FAB](https://docs.flutter.dev/cookbook/effects/expandable-fab), but when changing my snack bars from fixed to float, now they create an error on routes with the expandable FAB.

https://github.com/flutter/flutter/issues/84263 explores the issue but leaves it as expected. The expandable FAB uses the full screen, basically, and the snack bar is supposed to go above it.

### Proposal

I may be naive when viewing the layout of the ExpandableFab as seen in the screenshot below using Flutter Inspector, but I'm curious if this can be reduced. Obviously it has to work with many screen sizes, but based on inputs to the widget, we know its full reach.

If this change could be made, then floating snack bars and expandable FABs could coexist in harmony again. Is this feasible? Is `SizedBox.expand()` the only way to do this?

![Screenshot 2023-10-31 115034](https://github.com/flutter/flutter/assets/4104925/c6dbfb34-92ea-46e8-8ff0-91861cf1f39a)

# Fix Attempt

I gave it a scrappy try, and it worked. Not sure if this has unintended consequences or how best to calculate exact sizes, but here's a code sample and screenshot. The animation isn't right on expand/close while snack bar present, either.

```dart
// Set from default FAB size
static const double fabSize = 56.0;

@override
Widget build(BuildContext context) {
  final double size = fabSize + (_open ? (widget.distance ?? defaultDistance) : 0);
  return SizedBox(
    width: size,
    height: size,
    child: Stack(
      alignment: Alignment.bottomRight,
      clipBehavior: Clip.none,
      children: [
        _buildTapToCloseFab(),
        ..._buildExpandingActionButtons(),
        _buildTapToOpenFab(),
      ],
    ),
  );
}
```

![Screenshot 2023-10-31 120558](https://github.com/flutter/flutter/assets/4104925/d5d97d0d-94d4-44a7-8111-b0e58b7c320d)
Repository: pytorch
Issue: Add a function to torch.nested to create nested tensors from a buffer and sizes
Labels: module: serialization,triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

There currently exists no function in the `torch.nested` namespace to create nested Tensors from buffers combined with sizes and (optionally I think) strides and storage offsets, but the C++ Code already has functions for this kind of operation: `wrap_buffer` in `aten/src/ATen/native/nested/NestedTensorUtils.h`: https://github.com/pytorch/pytorch/blob/04024926f4d6ee07bfd2368a96d848879c982314/aten/src/ATen/native/nested/NestedTensorUtils.h#L35-L45 I use nested Tensors to accelerate my Dataset storage/loading, as can be observed using the small example below, so this feature would be greatly appreciated. 

I would be willing to open an according PR if that is desired, maybe this feature can also be included for the promotion of nested Tensors to the beta stage (#112398)

```python3
import torch
from time import time

# create a random dataset of variable sequence lengths (10k elements)
sizes = torch.randint(32, 256, size=(10000,))
dataset = {
    'input_ids': [torch.randint(32000, size=(i,)) for i in sizes],
    'labels': [torch.randint(32000, size=(i,)) for i in sizes],
}

def measure(name, func):
    s = time()
    func()
    print(f"{name} took {time() - s} seconds")

# save the dataset
measure("store_dict", lambda: torch.save(dataset, "dataset.pt"))
# load the dataset
measure("load_dict", lambda: torch.load("dataset.pt", weights_only=True))

# convert the dataset to nested tensor
def to_nested_tensor_info(ds: dict):
    return {k: torch.nested.nested_tensor(v) for k, v in ds.items()}

def save_nested_tensor(ds: dict):
    nested_ds = to_nested_tensor_info(ds)
    torch.save({
        k: (
            torch.cat(v, dim=-1),  # one large tensor
            nested_ds[k]._nested_tensor_size(),
            nested_ds[k]._nested_tensor_strides(),
            nested_ds[k]._nested_tensor_storage_offsets(),
        ) for k, v in ds.items()
    }, "nested.pt")

def load_nested_tensor():
    tuple_ds = torch.load("nested.pt", weights_only=True)
    return {
        k: torch._nested_view_from_buffer(*v) for k, v in tuple_ds.items()
    }

# save the dataset
measure("store_nested", lambda: save_nested_tensor(dataset))
# load the dataset
measure("load_nested", lambda: print(load_nested_tensor()['input_ids']))

```

### Alternatives

There exists `_nested_view_from_buffer`, but it is not located in the `torch.nested.` namespace, so I am unsure about the future for the function at hand.

### Additional context

```text
store_dict took 0.5521411895751953 seconds
load_dict took 1.3255178928375244 seconds
store_nested took 0.10043215751647949 seconds
load_nested took 0.009233236312866211 seconds
```

cc @mruberry @mikaylagawarecki @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer
Repository: PowerToys
Issue: Image Resizer isn't respecting an empty height or width field
Labels: Issue-Bug,Idea-Enhancement,Product-Image Resizer,Needs-Triage

### Microsoft PowerToys version

0.75.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Image Resizer

### Steps to reproduce

1. Right click on an image
2. click resize image
3. input desired height or width
4. click the "x" or delete the number in the opposite text box
5. click resize.

### ✔️ Expected Behavior

The output image should be the same aspect ratio of original image, but with the desired width/height that you typed in.

### ❌ Actual Behavior

The Image is of the dimensions of the last thing that was in the text box before it was cleared. So if you had W 16px and H 1080px in the text boxes when the application opens and you cleared the W text box and had a 16:9 image originally, you should end up with a final image that is 1920px x 1080px. However, instead you end up with (depending on whether you have Fit, Fill, or Stretch selected, but assuming you have Fit selected) a 16px by 9px image.

### Other Software

_No response_
Repository: PowerToys
Issue: Remove Restart Requirement
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

I would like the Power Toys update to be able to restart Explorer without needing a system restart.

<img width="318" alt="image" src="https://github.com/microsoft/PowerToys/assets/4219926/43399258-01be-4e00-bc2a-2365fd1c61c4">


### Scenario when this would be used?

After an update.

### Supporting information

We suffer enough restarts already, it would be nice to remove the avoidable ones. There's definitely a way to restart explorer without a full log off and on. And even if restarting the entire user session was required, it certainly _certainly_ doesn't require a full restart. At least suggest the user to sign out of windows and back in.
Repository: go
Issue: net/http: do not decode multipart form parts containing Content-Transfer-Encoding headers
Labels: NeedsFix

A `multipart/form-data` form consists of a series of parts, separated by a boundary. As originally specified in [RFC 2388](https://www.rfc-editor.org/rfc/rfc2388), each part may contain a `Content-Transfer-Encoding` header as defined in [RFC 2045 Section 6](https://www.rfc-editor.org/rfc/rfc2045.html#section-6).

[RFC 7578, Section 4.7](https://www.rfc-editor.org/rfc/rfc7578#section-4.7), which updates and obsoletes RFC 2388, deprecates the use of `Content-Transfer-Encoding` in contexts which support binary data, specifically including HTTP.

[http.Request.ParseMultipartForm](https://pkg.go.dev/net/http#Request.ParseMultipartForm) will parse form parts containing a `Content-Transfer-Encoding` header. To use an example from RFC 7578, `ParseMultipartForm` will parse this form part as containing the body "Joe owes €100.":

```
--AaB03x
content-disposition: form-data; name="field1"
content-type: text/plain;charset=UTF-8
content-transfer-encoding: quoted-printable

Joe owes =E2=82=AC100.
--AaB03x
```

This can act as a content smuggling vector, since other implementations generally do not decode quoted-printable form parts in HTTP `multipart/form-data` responses. As a hardening measure, we should consider not decoding encoded parts in `ParseMultipartForm`. RFC 7578 indicates that implementations that send such bodies are uncommon to nonexistent.
Repository: PowerToys
Issue: [Peek] Word document opens full screen (similar to Web layout in Word), not in standard Word mode
Labels: Idea-Enhancement,Needs-Triage,Product-Peek

### Description of the new feature / enhancement

Word document opens full screen (similar to Web layout in Word), not in normal mode. The current preview mode "stretches" the document sideways a lot and is difficult to read. Peek's screenshot is the size that opens by default.

Peek
![image](https://github.com/microsoft/PowerToys/assets/70388317/1aead3bd-f3c3-4963-a86b-971db44be2fb)

Word
![image](https://github.com/microsoft/PowerToys/assets/70388317/385b47bb-5676-4130-8220-5dad40eb6c80)


### Scenario when this would be used?

When viewing Word text documents 

### Supporting information

PowerToys v0.75.0
Repository: PowerToys
Issue: [Build, CI, Localization, Enterprise] Leverage Microsoft's own admxgen to auto-generate the ADMX & ADML files from JSON & CSV
Labels: Idea-Enhancement,Area-Build


## Description of the new feature / enhancement:

* What it says in the title.

## Scenario when this would be used:

* Less tedious work for @htcfreek & all y'all PowerToys contributors
* Quasi-prerequisite to subsequently make it SLIGHTLY easier to deal with the numerous permutations/combinations of feature enablement/disablement

## Supporting information:

* https://github.com/FSLogix/admxgen (which IS owned by Microsoft, for those not familiar, Microsoft bought FSLogix a couple of years ago, similar to how Microsoft eventually bought DesktopStandard Corporation for their PolicyMaker product, to yield the group policy system we nowadays know.)


### See also, IFF you're the kind of sysadmin who groks why I add this seemingly superfluous see also block here:
* The infamous reg2gpo powershell script, easily found on Google (careful it has VERY minor bugs)
* https://github.com/vcctr/reg2gpp (which ain't the same as the above)
* [MS-GPREG]
* Group Policy ADMX Syntax Reference Guide.doc
* Derek Melber's Windows Group Policy Windows Server 2008 and Windows Vista Resource Kit
* https://github.com/exchange12rocks/PSGPPreferences
Repository: PowerToys
Issue: [Peek] The selection in Table of Contents doesn't work when viewing a pdf file
Labels: Issue-Bug,Status-Reproducible,Product-Peek

### Microsoft PowerToys version

0.75.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Peek

### Steps to reproduce

I open the pdf file click on a page and/or the Table of Contents section.

### ✔️ Expected Behavior

I expect to go to the given page

### ❌ Actual Behavior

Table of Contents closes

### Other Software

_No response_
Repository: storybook
Issue: [Bug]: @storybook/addon-themes@7 doesn't update data-attr with inline: false
Labels: bug,addon: themes

### Describe the bug

I have the following setup for `addon-themes`
```ts
//preview.ts
  decorators: [
    withThemeByDataAttribute({
      themes: {
        light: "light",
        dark: "dark",
        system: "system",
      },
      defaultTheme: "light",
      parentSelector: "html",
      attributeName: "data-theme",
    }),
  ],
```

And it doesn't work well with the `inline: false` param. With other stories it works well.
```ts
const meta: Meta<typeof CBottomSheet> = {
  title: "Components/Bottom Sheet",
  component: CBottomSheet,
  parameters: {
    docs: {
      story: {
        inline: false,
      },
    },
  },
};
```

Check the demo:
![111](https://github.com/storybookjs/storybook/assets/16105726/1b62974c-75a6-43f8-ad1b-15d17491f372)


### To Reproduce

_No response_

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 11.7.8
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 20.6.0 - ~/.nvm/versions/node/v20.6.0/bin/node
    npm: 9.8.1 - ~/.nvm/versions/node/v20.6.0/bin/npm
    pnpm: 8.7.4 - ~/.nvm/versions/node/v20.6.0/bin/pnpm <----- active
  Browsers:
    Chrome: 118.0.5993.117
    Safari: 16.6
  npmPackages:
    @storybook/addon-docs: 7.5.1 => 7.5.1 
    @storybook/addon-essentials: ^7.5.1 => 7.5.1 
    @storybook/addon-interactions: ^7.5.1 => 7.5.1 
    @storybook/addon-links: ^7.5.1 => 7.5.1 
    @storybook/addon-mdx-gfm: ^7.5.1 => 7.5.1 
    @storybook/addon-themes: ^7.5.1 => 7.5.1 
    @storybook/blocks: ^7.5.1 => 7.5.1 
    @storybook/testing-library: ^0.2.2 => 0.2.2 
    @storybook/theming: ^7.5.1 => 7.5.1 
    @storybook/vue3: ^7.5.1 => 7.5.1 
    @storybook/vue3-vite: ^7.5.1 => 7.5.1 
    storybook: ^7.5.1 => 7.5.1
```


### Additional context

_No response_
Repository: TypeScript
Issue: Project References Wildcards
Labels: Suggestion,In Discussion

### 🔍 Search Terms

"project references" "glob" "wildcard" "repetitive" "monorepo"

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Project References currently have to be written out explicitly. It would be super nice if we could use a wildcard/glob like [this](https://github.com/microsoft/TypeScript/issues/25376#issuecomment-402302343), where I could simply have all of my `tsconfig.json` files look like this:

```
{
  "extends": ["../../../tsconfig.base.json"],
  "references": [{"path": "../../libs/*"}]
}
```

Or, even something like this:
```
{
  "extends": ["../../../tsconfig.base.json"],
  "references": [{"path": "../../libs/*/tsconfig.build.json"}]
}
```

We can discuss below whether supporting globstars (`**`) is prudent or not.

### 📃 Motivating Example

I've got a project with 8 libs and 3 apps using project references. It follows this basic structure:
```
tsconfig.base.json
workspaces/
  apps/
    app-1/
      tsconfig.json
    app-2/
      tsconfig.json
    .../
  libs/
    lib-1/
      tsconfig.json
    lib-2/
      tsconfig.json
    .../
```
There's a little more complexity, but that's the basic idea. However, I have a ton of repetition between all my `tsconfig.json` files that basically all look like this:
```json
{
  "extends": ["../../../tsconfig.base.json"],
  "references": [
    {
      "path": "../../libs/lib-1"
    },
    {
      "path": "../../libs/lib-2"
    },
    // ...
  ]
}
```

I can't rely on the `extends` functionality from `tsconfig.base.json` because of things like @RyanCavanaugh's explanation here: https://github.com/microsoft/TypeScript/issues/27098#issuecomment-494161387. 

### 💻 Use Cases

1. What do you want to use this for?
  - A monorepo with a number of shared libraries and apps
2. What shortcomings exist with current approaches?
  - Lots of repetition of lengthy amounts of JSON
3. What workarounds are you using in the meantime?
  - Specifying each lib in the `"references"` portion for every single app/lib that needs to be able to import shared libraries.
Repository: flutter
Issue: [tool_crash] WebDriverException
Labels: c: crash,tool,P2,team-tool,triaged-tool

## Command
```
flutter driver --driver=test_driver/integration_test_driver.dart --target=test/integration_test/auth_test.dart -d chrome --web-port=4444 --browser-name=chrome --screenshot=test_report --profile-memory=profile_memory.json
```

## Steps to Reproduce
1. ...
2. ...
3. ...

## Logs
WebDriverException
```
#0      InferSessionHandler.parseCreateResponse (package:webdriver/src/han
Repository: PowerToys
Issue: [Settings] Focus indicator automatically appears on launch
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.75.1

### Installation method

GitHub, PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Settings

### Steps to reproduce

1. Launch PowerToys (this should open the Dashboard)
2. Observe the focus indicator on the toggle switch for the first enabled module
<img width="299" alt="image" src="https://github.com/microsoft/PowerToys/assets/127593627/6518a9d6-9cf5-43c4-81a2-38f784bec8ab">


### ✔️ Expected Behavior

There shouldn't be a visible focus indicator on launch

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: godot
Issue: Read access violation crash when closing game if a node is no longer a child of the scene tree.
Labels: bug,topic:rendering,crash

### Godot version

v4.1.2.stable.mono.official [399c9dc39], v4.2.beta.mono.custom_build [93cdacbb0]

### System information

Godot v4.1.2.stable.mono - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 31.0.15.3742) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)

### Issue description

When a node is tweened and then removed from its parent, the engine crashes with a read access violation when closing the game. I never call queue_free() on the node in question. I realize this node is dangling, but the engine should not crash on close because of it.

The tween guarantees the issue can be reproduced. When closing the game, an access violation happens here (the singleton must have been deleted in cleanup before reaching this code where it's dereferenced):
https://github.com/godotengine/godot/blob/4363ae34fa3f52223ae78ff2f2c187ab99827e3a/servers/rendering/renderer_canvas_render.h#L154

I've tried it without the tween in different variations, and sometimes I can get a crash in the DEV_ASSERT here:
https://github.com/godotengine/godot/blob/4363ae34fa3f52223ae78ff2f2c187ab99827e3a/core/templates/self_list.h#L165

~~I have not been able to reproduce the issue in GDScript, only C#.~~

### Steps to reproduce

Open repro project, run it, press spacebar, close game, engine crashes on close.

Edit:
It's worth mentioning that you can't really tell the engine is crashing in the minimal repro project (the hang is minimal) if you're only running it from the editor. When it's run from the Visual Studio solution, you can see the actual crash on shutdown.

### Minimal reproduction project

[TweenAccessViolation.zip](https://github.com/godotengine/godot/files/13221230/TweenAccessViolation.zip)
Repository: rust
Issue: `rustdoc` can't handle some links on derive macros
Labels: T-rustdoc,C-bug,A-intra-doc-links,A-proc-macros

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
/// The default value of the setting normally matches the
/// [`Default`] trait. If you want to specify a
#[proc_macro_derive(Gui, attributes(default, heading_level))]
pub fn settings_macro(input: TokenStream) -> TokenStream { ... }
```

When running `cargo doc` I expected to see this happen: 

The `Default` trait is linked.

Instead, this happened:

![image](https://github.com/rust-lang/rust/assets/1451630/b7d7ca09-c339-49e6-841b-3f040ba67359)

The `Default` is not properly linked. There is no warning in the `cargo doc` output.

If I change it to:
```rust
/// The default value of the setting normally matches the
/// [`Default`](core::default::Default) trait. If you want to specify a
/// different default you can specify it like so:
```

It properly gets linked:

![image](https://github.com/rust-lang/rust/assets/1451630/ad3386ce-ef93-4f59-a8ed-9650d923a307)

But now there is a warning:

```
warning: redundant explicit link target
  --> asr-derive\src\lib.rs:46:17
   |
46 | /// [`Default`](core::default::Default) trait. If you want to specify a
   |      ---------  ^^^^^^^^^^^^^^^^^^^^^^ explicit target is redundant
   |      |
   |      because label contains path that resolves to same destination
   |
   = note: when a link's destination is not specified,
           the label is used to resolve intra-doc links
   = note: `#[warn(rustdoc::redundant_explicit_links)]` on by default
help: remove explicit link target
   |
46 | /// [`Default`] trait. If you want to specify a
   |     ~~~~~~~~~~~
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.73.0 (cc66ad468 2023-10-03)
binary: rustc
commit-hash: cc66ad468955717ab92600c770da8c1601a4ff33
commit-date: 2023-10-03
host: x86_64-pc-windows-msvc
release: 1.73.0
LLVM version: 17.0.2
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
```

</p>
</details>
Repository: flutter
Issue: [flutter_tools] flutter update-packages --force-upgrade should roll deps in create template pubspecs
Labels: P2,team-tool,triaged-tool

One way to do this would be for `flutter update-packages --force-upgrade` to read the dependencies & dev_depencencies from all the //packages/flutter_tools/templates/**/pubspec.yaml.tmpl files and add them to its global solve, and then write back the solved versions to the template files.
Repository: kubernetes
Issue: KEP 4216: Follow up on ImageRuntimeHandler field in kuberuntime.Container
Labels: sig/node,kind/feature,sig/windows,priority/important-longterm,triage/accepted

### What would you like to be added?

This issue is open to track https://github.com/kubernetes/kubernetes/pull/121456#discussion_r1378179233 comment in PR https://github.com/kubernetes/kubernetes/pull/121456 . This needs a wider discussion in sig-node community meeting to arrive at a consensus. Hence opening this issue to track that for beta version.

### Why is this needed?

This issue is open to track https://github.com/kubernetes/kubernetes/pull/121456#discussion_r1378179233 comment in PR https://github.com/kubernetes/kubernetes/pull/121456 . This needs a wider discussion in sig-node community meeting to arrive at a consensus. Hence opening this issue to track that for beta version.
Repository: flutter
Issue: [macOS] Refactor FlutterCompositor for testability and add unit tests
Labels: engine,platform-mac,a: desktop,P2,c: tech-debt,team-macos,triaged-macos

The [previous FlutterCompositor unit tests][old_tests] were heavily OCMock-based and in fact only really tested two things:
* that the mock objects we created for the tests do the things we configured them to do.
* that FlutterCompositor's implementation make certain specific calls to objects that aren't part of its public API.

The first of these isn't useful as a test. The second is testing that the implementation is the implementation rather than testing that the compositor has certain behaviour.

FlutterCompositor should be refactored for testability and new tests written that actually exercise the compositor.

[old_tests]: https://github.com/flutter/engine/blob/c3330701d868222bce04d55ab281c278d1eba473/shell/platform/darwin/macos/framework/Source/FlutterCompositorTest.mm#L88-L137