sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [bug]  Yarn Executable not found by BuildTask.kt on windows, when building Android with Yarn and Svelte
Labels: type: bug,status: needs triage

### Describe the bug

The android build fails with:
A problem occurred starting process 'command 'yarn-1.22.22.cmd''


### Reproduction

Install yarn using corepack:
```powershell
corepack enable
corepack install yarn@1.22.22 # default version if no "packageManager" field is found in package.json
```
Or install yarn using npm 
```
npm install yarn@1.22.22 --global
````

Both methods do not work as expected

Then run cargo create-tauri-app --beta
Then yarn tauri android init
Then yarn tauri android dev

The process will crash 

### Expected behavior

Tauri should set the packageManager field in package.json, then just run `yarn --version` and check if the version constraint was respected.

If not, it should print an error which tells the user to install yarn using corepack, which respects the packageManager field and will even install arbritrary yarn versions based on the field.

If the version check succeeds, it should just run 'yarn ...'  

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 125.0.2535.79
    ✔ MSVC:
        - Visual Studio Build Tools 2019
        - Visual Studio Community 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.13.1
    - yarn: 1.22.22
    - npm: 10.5.2

[-] Packages
    - tauri [RUST]: 2.0.0-beta.22
    - tauri-build [RUST]: 2.0.0-beta.17
    - wry [RUST]: 0.40.1
    - tao [RUST]: 0.28.0
    - tauri-cli [RUST]: 2.0.0-beta.20
    - @tauri-apps/api [NPM]: 2.0.0-beta.13
    - @tauri-apps/cli [NPM]: 2.0.0-beta.20

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../build
    - devUrl: http://localhost:1420/
    - framework: Svelte
    - bundler: Vite
Done in 5.41s.
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: [ShapeInferenceError] Attribute dilations has incorrect size
Labels: module: onnx,triaged,onnx-needs-info

### 🐛 Describe the bug

It is normal for us to infer transfusion network using pth weight, but when I converted the pth weight of transfusion to onnx, an error occurred: Error reported by strict ONNX shape inference: [ShapeInferenceError] Inference error (s): (op_type: MaxPool, node name:/dense_head/MaxPool_1): [ShapeInferenceError] Attribute divisions have incorrect size. We have identified the code location corresponding to the error operator, which is a function of max_pool2d with the dilation set to 1. We have also visualized the onnx and found that the dilation attribute of max_pool2d at the error location is also 1. So why is there an error here: Attribute divisions have incorrect size? Please give me some help.

![_cgi-bin_mmwebwx-bin_webwxgetmsgimg  MsgID=4589743132442832367 skey=@crypt_545ad648_b8b1d6c97415ce1591beaebb838b8224 mmweb_appid=wx_webfilehelper](https://github.com/pytorch/pytorch/assets/33457812/8237d97f-3506-49e2-bc6b-01179a0adee7)


### Versions

Collecting environment information...
PyTorch version: 2.3.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.3) 9.4.0
Clang version: Could not collect
CMake version: version 3.20.5
Libc version: glibc-2.31

Python version: 3.8.19 (default, Mar 20 2024, 19:58:24)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-105-generic-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: 12.5.40
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 4060 Ti
Nvidia driver version: 535.146.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip] numpy==1.24.4
[pip] torch==2.3.0
[pip] torchaudio==2.3.0
[pip] torchvision==0.18.0
[conda] numpy                     1.24.4                   pypi_0    pypi
[conda] torch                     2.3.0                    pypi_0    pypi
[conda] torchaudio                2.3.0                    pypi_0    pypi
[conda] torchvision               0.18.0                   pypi_0    pypi
Repository: angular
Issue: Exception when using null coalescing operator in @for track expression
Labels: state: has PR,area: compiler,bug,compiler: template pipeline

### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

When using the null coalescing operator `??` in the `track` expression using the new `@for` control flow syntax, an error is thrown during template rendering (and the contents of the for-loop aren't rendered).

Example (see reproduction URL):
```html
@for (item of myList; track item.field1 ?? item.field2) {
  <p>{{ $index }}: {{ item.field1 }}, {{ item.field2 }}</p>
}
``` 

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-for-template-bug?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
ERROR ReferenceError: tmp_7_0 is not defined
    at _forTrack0 (main.ts:3:8)
    at createOrAttach (chunk-ZNRRMEEJ.js?v=a3f8c8d7:17941:71)
    at reconcile (chunk-ZNRRMEEJ.js?v=a3f8c8d7:17865:7)
    at Module.ɵɵrepeater (chunk-ZNRRMEEJ.js?v=a3f8c8d7:18181:5)
    at TodosComponent_Template (main.ts:11:5)
    at executeTemplate (chunk-ZNRRMEEJ.js?v=a3f8c8d7:10767:5)
    at refreshView (chunk-ZNRRMEEJ.js?v=a3f8c8d7:11789:7)
    at detectChangesInView (chunk-ZNRRMEEJ.js?v=a3f8c8d7:11955:5)
    at detectChangesInViewIfAttached (chunk-ZNRRMEEJ.js?v=a3f8c8d7:11938:3)
    at detectChangesInComponent (chunk-ZNRRMEEJ.js?v=a3f8c8d7:11932:3)
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 18.0.2
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 18.0.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1800.2
@angular-devkit/build-angular   18.0.2
@angular-devkit/core            18.0.2
@angular-devkit/schematics      18.0.2
@angular/cli                    18.0.2
@schematics/angular             18.0.2
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.6
```


### Anything else?

The error is similar to this previous issue, also concerning the use of the null coalescing operator in template expressions: #53295

The compiler turns the `@for` `track` expression into this statement, which throws an error because `tmp_7_0` is never defined:
```js
var _forTrack0 = ($index, $item) => (tmp_7_0 = $item.field1) !== null && tmp_7_0 !== void 0 ? tmp_7_0 : $item.field2; 
```
Repository: ui
Issue: [bug]: Data Table headless UI redirect not working
Labels: bug

### Describe the bug

When you click on the `headless UI` link on the Data Table page, it will be redirect to not found page at Tan Stack.
![ss1](https://github.com/shadcn-ui/ui/assets/91488737/eb4a6265-4889-416c-841d-13e6723323cd)

![ss2](https://github.com/shadcn-ui/ui/assets/91488737/4ba25ee1-e8b6-43c1-9b9e-28e48d15ba3c)



### Affected component/components

Data Table Docs

### How to reproduce

1. Go to Data Table Page
2. Click on headless UI link.
3. It will be redirect to not found page.

### Codesandbox/StackBlitz link

https://ui.shadcn.com/docs/components/data-table

### Logs

_No response_

### System Info

```bash
Any
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [bug]: FIX( documentation url): fix url in data-table documentation in mdx file
Labels: bug

### Describe the bug

When i try to test the `Data table`, i just saw the `Docs` button, but when i clicked to it, it seems that the url was broken.

so i decide to create this [PR](https://github.com/shadcn-ui/ui/pull/3915), to fix this problem in the documentation


An example of the case:

https://github.com/shadcn-ui/ui/assets/90482598/c128a3ee-e864-46e4-8160-82cd45462ca3




### Affected component/components

data-table

### How to reproduce

1. Go to [data-table page](https://ui.shadcn.com/docs/components/data-table)
2. At the very top of the page click on `Docs`.
3. It open a broken url

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
System: Linux
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: A propagate_notification call crashes the game
Labels: platform:macos,topic:core,needs testing,crash

### Tested versions

4.2.2.stable

### System information

MacOS Ventura 13.5.2 M2

### Issue description

I have had several random crashes in my game, with this stack trace:

```
USER ERROR: Caller thread can't call this function in this node (/root). Use call_deferred() or call_thread_group() instead.
   at: propagate_notification (scene/main/node.cpp:2249)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.2.stable.official (15073afe3856abd2aa1622492fe50026c7d63dc1)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] 1   libsystem_platform.dylib            0x000000018ea46a24 _sigtramp + 56
[2] 2   Network                             0x0000000194f9e254 nw_resolver_cancel + 704
[3] 3   Network                             0x00000001952af234 -[NWConcrete_nw_endpoint_resolver cancelWithHandler:forced:] + 228
[4] 4   Network                             0x00000001952ba474 nw_endpoint_handler_cancel + 1116
[5] 5   Network                             0x00000001957f5414 -[NWConcrete_nw_endpoint_flow cancelWithHandler:forced:] + 932
[6] 6   Network                             0x00000001952ba474 nw_endpoint_handler_cancel + 1116
[7] 7   Network                             0x00000001952109e4 __nw_connection_cancel_inner_block_invoke + 1248
[8] 8   Network                             0x0000000195210260 nw_connection_cancel_inner + 328
[9] 9   Network                             0x000000019520fe7c nw_connection_cancel + 116
[10] 10  CFNetwork                           0x00000001933bba5c CFURLDownloadCancel + 41484
[11] 11  CFNetwork                           0x00000001932b1418 CFHTTPMessageGetTypeID + 736
[12] 12  CFNetwork                           0x000000019333b9ec CFHTTPMessageCreateResponse + 1592
[13] 13  libdispatch.dylib                   0x000000018e866874 _dispatch_call_block_and_release + 32
[14] 14  libdispatch.dylib                   0x000000018e868400 _dispatch_client_callout + 20
[15] 15  libdispatch.dylib                   0x000000018e86fa88 _dispatch_lane_serial_drain + 668
[16] 16  libdispatch.dylib                   0x000000018e87062c _dispatch_lane_invoke + 436
[17] 17  libdispatch.dylib                   0x000000018e8718e8 _dispatch_workloop_invoke + 1764
[18] 18  libdispatch.dylib                   0x000000018e87b244 _dispatch_workloop_worker_thread + 648
[19] 19  libsystem_pthread.dylib             0x000000018ea14074 _pthread_wqthread + 288
[20] 20  libsystem_pthread.dylib             0x000000018ea12d94 start_wqthread + 8
-- END OF BACKTRACE --
================================================================
```

Edit: I should have precised that I don't have any call to `propagate_notification` in my code, not do I use threads. It is an engine call


### Steps to reproduce

This is hard to reproduce, it seems possible to happen at any time.

### Minimal reproduction project (MRP)

see above
Repository: rust
Issue: rustdoc-json-types: Use different repr for Constant in Item and Type position
Labels: T-rustdoc,A-rustdoc-json

> This is fine for now, but once this lands, I'd like to look into using seperate type for `Item::Constant` and `Term::Constant`/`GenericArgKind::Constant`, so this can be flattened again. But this shoudn't block this PR.

_Originally posted by @aDotInTheVoid in https://github.com/rust-lang/rust/pull/125958#discussion_r1625934878_
Repository: ollama
Issue: Support intel cpu
Labels: feature request

https://github.com/ollama/ollama/pull/3897

It would be good to document how to support intel cpus (using both intel compilers and mkl). My PR demonstrates how to compile with intel but I was told that we should move this to a feature request.

im happy to help if I get some guidance on how this should go.
Repository: PowerToys
Issue: Fancyzone: Can we get more then 240 zones in fancyzones please,
Labels: Needs-Triage

### Description of the new feature / enhancement

To be able to create more then 240 zones in fancyzones for better organisation 

### Scenario when this would be used?

For those of us with larger monitors such as super ultrawide or for those who use large tvs as monitors etc

### Supporting information

_No response_
Repository: ant-design
Issue: Popconfirm 在某些情况下 autoAdjustOverflow 的箭头位置显示错误
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-b9mjyk)

### Steps to reproduce

设置 Popconfirm 的 placement="topRight"，并保证左上角没有足够的显示位置。其它 placement 未详细测试，估计也有此类问题！

### What is expected?

箭头显示在正确位置

![image](https://github.com/ant-design/ant-design/assets/1730277/81eff283-a8ee-465f-8ae5-6d87dd39b372)

### What is actually happening?

箭头显示在错误位置

![image](https://github.com/ant-design/ant-design/assets/1730277/0be5a60b-b848-4594-9f89-d4cdaca97769)

| Environment | Info |
| --- | --- |
| antd | 5.18.0 |
| React | 18 |
| System | WIN11 |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: material-ui
Issue: [docs][pigment-css] Add opt-in migration to Pigment CSS
Labels: docs,package: material-ui,package: pigment-css

- [ ] Document SSR https://github.com/mui/material-ui/issues/38137#issuecomment-2147733578. Maybe we need to have a toggle to change the docs's content based on the style engine used;

<img width="314" alt="SCR-20240605-bjyu" src="https://github.com/mui/material-ui/assets/3165635/cf814c2d-6894-4289-934c-162fb742bf60">

Or maybe, we just need to move https://mui.com/material-ui/guides/server-rendering/ under the Emotion section of Pigment CSS docs. I mean, I see nothing in that page that is about Material UI, it's all Emotion related.

- [ ]
Repository: vscode
Issue: Make sure event subscriptions are stored and disposed
Labels: freeze-slow-crash-leak,debt

The following is a list of code locations at which an event listener is added but the subscription (e.g the disposable that's being returned) is getting lost (garbage collected before disposal). This means the listener is question cannot be removed anymore and therefore it is a leak. 

You can enable these warnings via `src/vs/base/common/event.ts#_enableListenerGCedWarning`

---
- [ ] vs/base/common/event.ts:178:64
- [ ] vs/base/common/event.ts:659 @hediet 
- [ ] vs/platform/instantiation/common/instantiationService.ts:317:36
- [ ] vs/platform/request/node/requestService.ts:193:8
- [ ] vs/platform/theme/common/colorUtils.ts:322:14
- [ ] vs/platform/theme/common/iconRegistry.ts:315:13
- [ ] vs/platform/theme/common/tokenClassificationRegistry.ts:626:28
- [x] vs/platform/update/common/updateIpc.ts:52:46 @joaomoreno
- [ ] vs/workbench/api/common/extHost.api.impl.ts:240:19
- [ ] vs/workbench/api/common/extHost.api.impl.ts:240:20
- [ ] vs/workbench/api/common/extHostWorkspace.ts:728:53
- [x] vs/workbench/contrib/scm/browser/menus.ts:25 @lszomoru 
- [x] vs/workbench/contrib/share/browser/share.contribution.ts:59:28
- [ ] vs/workbench/services/search/node/rawSearchService.ts:344:11
Repository: pytorch
Issue: tensor.size does not accept `dim=None` argument despite documentation because of some confusion with named dimensions
Labels: triaged,release notes: python_frontend

### 🐛 Describe the bug

![image](https://github.com/pytorch/pytorch/assets/1041752/8123c61c-073f-4f35-9403-266d5abf5959)
https://pytorch.org/docs/stable/generated/torch.Tensor.size.html#torch.Tensor.size

Currently `tensor.size(dim=None)` gives `RuntimeError: Please look up dimensions by name, got: name = None.`
```
>>> import torch
>>> a = torch.arange(3)
>>> a.size()
torch.Size([3])
>>> a.size(None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: Please look up dimensions by name, got: name = None.
>>> a.size(dim = None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: Please look up dimensions by name, got: name = None.
>>> a.size(0)
3
```

I think that if there is some default behavior for unpassed arg, it should also always be triggerable with some explicit arg as well. This allows sometimes to pass the arg from some other place and still allow passing down both behaviors: dim=None/dim=int

### Versions

N/A
Repository: react
Issue: [Compiler Bug]: Runtime error with Higher Order Components
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://codesandbox.io/p/devbox/vite-react-forked-w7lfc7?file=%2Fsrc%2FApp.tsx&workspaceId=5309445f-fc83-4685-b2a0-3050725a1482

### Repro steps

We're just going through our codebase and fixing issues that we're getting when enabling the compiler.

Not sure if this is something we are doing wrong, or a compiler issue.

We get 'TypeError: Cannot read properties of null (reading 'useMemoCache')' when running something similar to the following code in NextJS (minimal repro):

Passing in a string as ElementType seems to be something that's fairly commonly recommended (https://www.aleksandrhovhannisyan.com/blog/dynamic-tag-name-props-in-react/ is the first result on Google for me).

```
import React, { ElementType, FC } from "react";

function TagChangingHOC(Tag: ElementType): FC<{text: string}> {
    return function({text}) {
        return <Tag>{text}</Tag>
    }
}

const DivTag = TagChangingHOC('div');
const SpanTag = TagChangingHOC('span');

export default function MyApp() {
    return (<> <DivTag text="foo"/> <SpanTag text="bar"/> </>)
}
```

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHaYGZQ3AFwEsIMACAFQEMBzAYQAsqMaiWAJAeToApqaAlGWCYyZGAgKxyufMVJkewMgQQAPAmQC+QkeTHjJ0sgB5+APmCqNWkwHoLo7Zi2ZMcUmE0ARIgDd+MgBeSlpGZlYObh4AcgATfxiBAG53T00AZQAHZkCQ-nCWNhouXhiwHIwk1KwMdSyIGE04hGwqKAAbTVlCEnIAWQBPAEEsrJ5dJwkpGHIeE3NTXwDaFXUCILQQbAgILbtFk2zc1esNrYAjKhh9w4OBF0wQLSA


I'm very happy to accept an alternative solution if this is too much of an edge case.



### How often does this bug happen?

Every time

### What version of React are you using?

19.0.0-rc.0
Repository: tauri
Issue: [feat] add visionOS support
Labels: type: feature request

### Describe the problem

Add support for Apple Vision Pro

### Describe the solution you'd like

same as iOS 

### Alternatives considered

Working on better support in Tao

### Additional context

Current PRs submitted:

- [ ] https://github.com/tauri-apps/wry/pull/1286
- [ ] https://github.com/SSheldon/rust-objc/pull/123
- [ ] https://github.com/SSheldon/rust-block/pull/20
- [ ] https://github.com/tauri-apps/cargo-mobile2/pull/340
- [x] https://github.com/Brendonovich/swift-rs/pull/63
- [x] https://github.com/oconnor663/os_pipe.rs/pull/32
- [x] https://github.com/Byron/open-rs/pull/99
- [x] https://github.com/rust-lang/socket2/pull/503
- [ ] https://github.com/briansmith/ring/pull/2032
Repository: storybook
Issue: [Bug]: subcomponents get type error
Labels: bug,needs triage

### Describe the bug

See the repro. In short, when using subcomponents, I get this error:
```
src/stories/Header.stories.ts:11:5 - error TS2322: Type '({ primary, size, backgroundColor, label, ...props }: ButtonProps) => JSX.Element' is not assignable
to type 'ComponentType<unknown>'.
  Type '({ primary, size, backgroundColor, label, ...props }: ButtonProps) => JSX.Element' is not assignable to type 'FunctionComponent<unknown>'.
    Types of parameters '__0' and 'props' are incompatible.
      Type 'unknown' is not assignable to type 'ButtonProps'.
```


### Reproduction link

https://github.com/c-vetter/repro_storybook_subcomponents-type-error

### Reproduction steps

1. `npx storybook init`
2. Add a subcomponent to a story
3. Boom! error

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 20.12.2 - ~\scoop\apps\nvm\current\nodejs\nodejs\node.EXE
    Yarn: 1.22.22 - ~\scoop\apps\yarn\current\bin\yarn.CMD
    npm: 10.5.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD <----- active
    pnpm: 8.15.4 - ~\scoop\apps\nvm\current\nodejs\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (123.0.2420.97)
  npmPackages:
    @storybook/addon-essentials: ^8.1.5 => 8.1.5
    @storybook/addon-interactions: ^8.1.5 => 8.1.5
    @storybook/addon-links: ^8.1.5 => 8.1.5
    @storybook/addon-onboarding: ^8.1.5 => 8.1.5
    @storybook/blocks: ^8.1.5 => 8.1.5
    @storybook/react: ^8.1.5 => 8.1.5
    @storybook/react-vite: ^8.1.5 => 8.1.5
    @storybook/test: ^8.1.5 => 8.1.5
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
    storybook: ^8.1.5 => 8.1.5
```


### Additional context

Looking for a solution, I came across #21253

By updating that one's repro, I was able to get it to work: https://github.com/c-vetter/repro_storybook_subcomponents-type-error/tree/alt/21253

I'm unsure as to what is the relevant difference, will update here with any findings.
Repository: flutter
Issue: GridView: support auto size and colspan
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Use case

All cells of a GridView have the same size(width x height). It is not suitable for some use cases. For example,
For displaying an employee info:

```
      Name:             John Tigger
     ------------------------------------------------------
     Address:         123 Hello Street
                             New City, New State 123456
                             New Country
     ------------------------------------------------------
     Show a map for the address (colspan: 2)
     ------------------------------------------------------
     Manager:          Mike Tigger
     ------------------------------------------------------
     Performance:     9/10
     ------------------------------------------------------
```

1). The property name column occupies less space than value column. So cell width should be auto.
2). All cell heights need to be auto.  Auto: fit content.
3). Map occupies a whole row (colspan: 2).      
 
In html, they can be achieved by the following css:

```
.grid {
    display: grid;
    grid-template-columns: auto auto;
}

.map-cell {
   grid-column-end: span 2;
}
```

### Proposal

Add attribute "cellSize" to GridView, and add a new class GridCell that supports colspan attribute.  For example,

```
   GridView.count(
      crossAxisCount: 2,
      cellSize: auto,
      children: [
           Widget1, Widget2
           GridCell(colspan: 2, child: widget),
      ],
    );
```