sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: puppeteer
Issue: [Bug]: Element screenshot is off
Labels: bug,screenshot,confirmed,P3

### Bug expectation

I expect the screen is to be of the element area only but it also shows area outside of the element.

Image output is 

![%23rh-hddq4%20%3E%20 rh-carousel-slide-body%20%3E%20 rh-promo--component%5Bdata-eq-pts%3D%22sm-promo%3A%200%2C%20md-promo%3A%20535%22%5D%5Bdata-eq-state%3D%22sm-promo%20md-promo%22%5D%20%3E%20 rh-prom](https://github.com/puppeteer/puppeteer/assets/1344532/2df57175-fb2b-4111-8d4e-c16ab6fa23d0)

But it should be 

![www redhat com_zh_services_certifications](https://github.com/puppeteer/puppeteer/assets/1344532/a0df85e5-ea9a-4fcb-8c9a-eb9dce1bcfbf)

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Minimal, reproducible example

```TypeScript
const config = {
  viewport: { width: 2000, height: 10000 },
  timeout: 50000,
  ua: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36",
};

const selector = `#rh-hddq4 > .rh-carousel-slide-body > .rh-promo--component[data-eq-pts="sm-promo: 0, md-promo: 535"][data-eq-state="sm-promo md-promo"] > .rh-promo-cta > .rh-promo-cta-link[data-analytics-linktype="cta"]`;

async function render(props: { url: string; onRender: (page: Page) => Promise<void> }) {
  const browser = await launch({ headless: true });
  const page = await browser.newPage();
  await page.setBypassCSP(true);
  await page.setViewport(config.viewport);
  await page.setUserAgent(config.ua);
  await page.goto(props.url, { waitUntil: "networkidle2" });
  await props.onRender(page);
  console.log("done");
  await page.close();
  await browser.close();
}

async function main() {
  await render({
    url: "https://www.redhat.com/zh/services/certifications",
    onRender: async page => {
      const element = await page.$(decodeURIComponent(selector));
      if (element) {
        const buffer = <Buffer>await element.screenshot({
          type: "jpeg",
          encoding: "binary",
          quality: 50,
          captureBeyondViewport: true,
        });
        await writeFile(`screenshots/${encodeURIComponent(selector).substring(0, 200)}.jpg`, buffer, "base64");
      }
    },
  });
}

main();
```


### Error string

No error.

### Puppeteer configuration

_No response_

### Puppeteer version

20.2.0

### Node version

18.13.0

### Package manager

yarn

### Package manager version

1.22.19

### Operating system

macOS
Repository: material-ui
Issue: SwipeableDrawer: transition equal to 0 hangs application
Labels: breaking change,component: drawer,component: SwipeableDrawer

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:
[Not working right](https://playcode.io/1471448)

Steps:

1. Click button
2. Close drawer
3. Try to click button again


### Current behavior 😯

At step 3 button is not clickable. App is "hanging"

### Expected behavior 🤔

At step 3 button should be clickable

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: material-ui
Issue: Can't use Box to do one off style overrides of external components when there are props collisions
Labels: package: system,component: Box,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:
https://codesandbox.io/s/resizablebox-prop-collision-cedc3v?file=/src/App.tsx

### Current behavior 😯

using
```jsx
<Box component={MyBox /* MyBox does use the className prop */}
myprop={42 /* myprop is some custom prop of MyBox*/}
sx={ /*using sx to get theme values, or to compose styles, or for consistency.. */
  theme => ({backgroundColor: theme.foo.bar})
}
>
 ...
</Box>
```

works except if myExternalProp happens to be one of the system prop (it gets swallowed). As an exemple, imagine a CountryBox which take the flag and border props. flag works, but border collides with css borders. In the example, it's ResizableBox from 'react-resizable'. The 'resizeHandle' prop works but the 'width' prop doesn't. 

### Expected behavior 🤔

Should be able to use pass any props to the component, because system props should be in sx, not in props of Box

### Context 🔦

I want to use the mui styling system (to have inheritence, composition, theme access, etc) to do a one off customization of a component accepting a className, without adding dom elements and using nested selectors.

One way to do it is to use styled but this requires creating an intermediate component..
```jsx
const MyBoxSx = styled(MyBox)({}); /* MyBox does use the className prop */
<MyBoxSx
myprop={42 /* myprop is some custom prop of MyBox*/}
sx={ /*using sx to get theme values, or to compose styles, or for consistency.. */
  theme => ({backgroundColor: theme.foo.bar})
}
```

### Your environment 🌎

_No response_
Repository: vscode
Issue: Git - "fatal: repository not found" exception even when authenticated as repository owner
Labels: bug,git

- VSCode Version: 1.7.8
- OS: Windows 11

Steps to Reproduce:

1. CTRL + SHIFT + P into "Git: Clone"
2. Click on "Clone from GitHub"
3. Ok to the two windows that ask to open URL and URI
4. Click on a private GitHub project that is owned by the repo owner

It seems a strange behavior to me since cloning this way worked until some weeks ago and the workstation I'm using haven't been used since. Also older repositories that worked this way, now fail with the same error when trying to push to remote.
Git Fork works without issue, so it's a vscode related problem.
I managed to git clone by adding the username in front of the git clone command.

So

`2023-05-07 18:14:40.972 [info] > git clone https://github.com/Ch41r05/StarUMLsvg2png.git c:\Users\Manuel\Desktop\StarUMLsvg2png --progress [865ms]
2023-05-07 18:14:40.972 [info] Cloning into 'c:\Users\Manuel\Desktop\StarUMLsvg2png'...
remote: Repository not found.
fatal: repository 'https://github.com/Ch41r05/StarUMLsvg2png.git/' not found
`

does not work, but

`git clone https://Ch41r05@github.com/Ch41r05/StarUMLsvg2png.git c:\Users\Manuel\Desktop\StarUMLsvg2png --progress
Cloning into 'c:\Users\Manuel\Desktop\StarUMLsvg2png'...
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
Receiving objects: 100% (4/4), done.`

Works as expected.

Also tried to make the repo public and the first command then works as expected.
Seems almost like Github Authentication (v 0.0.2) extension can't forward the username to git.

![image](https://user-images.githubusercontent.com/32594277/236689465-569da91e-484d-49af-a431-aed3431bd63a.png)
Repository: vscode
Issue: Merge editor: Come up with a awareness strategy for when the merge editor resolves a conflict git was unable to
Labels: feature-request,merge-editor
Repository: godot
Issue: Circular dependency causes resources to be missing on export
Labels: bug,confirmed,topic:export

### Godot version

4.0 Stable

### System information

Windows 10

### Issue description

When exporting the project as a Windows executable, the application throws the following error. 

`Make sure resources have been imported by opening the project in the editor at least once.`

### Steps to reproduce

Export project as Windows Desktop (Runnable)
Run the application.

### Minimal reproduction project

N/A
Repository: yt-dlp
Issue: How to download multiple sections of YT video and merge into single file using `--download-sections`
Labels: enhancement

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2023.03.04** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

Can I download multiple sections of a youtube video and merge it into a same file ?
eg. I want to download from 0:00 - 2:18 and 4:40 - 6:01 for this https://www.youtube.com/watch?v=jHbyQ_AQP8c

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: pytorch
Issue: Support fake tensor real inputs in dynamo
Labels: triaged,module: dynamo

### 🐛 Describe the bug

Today, Dynamo assumes that if you have a fake tensor, it was was generated by fakeification in the compiler. But fake tensor is also a user visible concept, and you could for example call a torch.compile'd function with fake tensor inputs. We should be able to handle fake tensor inputs, distinguishing them from internal fake tensor inputs by checking which fake mode they're associated with (torch.compile will always allocate a fresh fake mode).

Some basic functionality works; for example, it works to `FakeTensorMode.from_tensor` a fake tensor (however, if you had a Parameter+fake tensor, the parameter-ness is lost; that needs to be fixed.)

Here are at least some of the spots where we make incorrect assumptions.

```
diff --git a/torch/_dynamo/variables/builder.py b/torch/_dynamo/variables/builder.py
index 1d7c33d50c2..64523f3e610 100644
--- a/torch/_dynamo/variables/builder.py
+++ b/torch/_dynamo/variables/builder.py
@@ -154,8 +154,6 @@ class GraphArg:
             assert isinstance(
                 self.fake_tensor, torch._subclasses.fake_tensor.FakeTensor
             )
-        if isinstance(self.example, torch._subclasses.fake_tensor.FakeTensor):
-            raise AssertionError("Fake Tensor observed in TorchDynamo Fx graph inputs")
 
     def load(self, tx):
         return self.source.reconstruct(tx)
@@ -796,7 +794,7 @@ class VariableBuilder:
             # a later point in time.
             ignore_subclass = True
         else:
-            assert type(value) in (torch.Tensor, torch.nn.Parameter), type(value)
+            assert type(value) in (torch.Tensor, torch.nn.Parameter, FakeTensor), type(value)
             ignore_subclass = False
 
         is_duplicate_tensor = source in self.tx.output.input_source_to_var
@@ -1024,10 +1022,6 @@ def wrap_fx_proxy_cls(
         if example_value is None:
             example_value = get_fake_value(proxy.node, tx)
 
-        # Handle recursive calls here
-        elif isinstance(example_value, FakeTensor):
-            pass
-
         elif isinstance(example_value, torch.Tensor):
             if tx.export:
                 # The legacy behavior for real value cache with subclasses was
@@ -1200,7 +1194,7 @@ class TrackedFake:
 def wrap_to_fake_tensor_and_record(
     e, tx, ignore_subclass=False, *, source: Optional[Source], is_tensor: bool
 ):
-    if type(e) in (torch.Tensor, torch.nn.Parameter) or (
+    if type(e) in (torch.Tensor, torch.nn.Parameter, FakeTensor) or (
         ignore_subclass and isinstance(e, torch.Tensor)
     ):
         assert source is not None
```

cc @voznesenskym @penguinwu @anijain2305 @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @desertfire @thiagocrepaldi 

### Versions

master
Repository: flutter
Issue: Flutter project is not launching from Xcode
Labels: platform-ios,P3,team-ios,triaged-ios

## steps to reproduce
1) start a new project
1) paste in the repo code from https://github.com/flutter/flutter/issues/126620
1) Add in the http dependency (**I think this is key**)
1) launch it from the command-line to an iPhone (notice that it executes fine)
1) Open up ios/Runner/Runner.xcworkspace in Xcode
1) Hit the play button on xcode

I'm unable to reproduce it with just the standard flutter counter app.

## error log
```
2023-05-12 09:32:15.934100-0700 Runner[15751:6468463] Metal API Validation Enabled
2023-05-12 09:32:16.558641-0700 Runner[15751:6468463] [VERBOSE-2:dart_vm_data.cc(20)] VM snapshot invalid and could not be inferred from settings.
2023-05-12 09:32:16.558875-0700 Runner[15751:6468463] [VERBOSE-2:dart_vm.cc(268)] Could not set up VM data to bootstrap the VM from.
2023-05-12 09:32:16.558991-0700 Runner[15751:6468463] [VERBOSE-2:dart_vm_lifecycle.cc(85)] Could not create Dart VM instance.
2023-05-12 09:32:16.559088-0700 Runner[15751:6468463] [VERBOSE-3:shell.cc(139)] Check failed: vm. Must be able to initialize the VM.
dyld4 config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Developer/usr/lib/libBacktraceRecording.dylib:/Developer/usr/lib/libMainThreadChecker.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib
```

## doctor
```
aaclarke-macbookpro3:to_image_data_bug aaclarke$ flutter doctor -v
[✓] Flutter (Channel main, 3.11.0-5.0.pre.22, on macOS 13.3.1 22E772610a darwin-arm64, locale en)
    • Flutter version 3.11.0-5.0.pre.22 on channel main at /Users/aaclarke/dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cab29b2034 (3 days ago), 2023-05-09 18:38:49 +0200
    • Engine revision 824cd09b8c
    • Dart version 3.1.0 (build 3.1.0-87.0.dev)
    • DevTools version 2.23.1
```
Repository: next.js
Issue: React Suspense Component fallback does not render
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #163-Ubuntu SMP Fri Mar 17 18:26:02 UTC 2023
    Binaries:
      Node: 16.15.0
      npm: 9.2.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.4
      eslint-config-next: 13.3.4
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://gist.github.com/NanasArsenal/001de939250d8eab215d707c442e7187

### To Reproduce

Try creating a using the inbuilt react Suspense component, and add a loading component to the fallback prop of the Suspense component.

### Describe the Bug

So the bug here is there is no rendering of the suspense. 

### Expected Behavior

The suspense component is to render before all the data in the actual component are loaded.

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

_No response_

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

vercel
Repository: pytorch
Issue: fused torch.optim.AdamW isn't faster than the unfused version
Labels: module: optimizer,triaged

### 🐛 Describe the bug

When I enabled the fused option of `torch.optim.AdamW` on PyTorch 2.0.1 for my vision model that has a low SM efficiency at the optimizer step, I didn't see any speedup. I profiled the fused version and unfused version, and I could see that although the fused version could improve SM efficiency by fusing multiple small CUDA kernels, the fused `aten::_fused_adamw_` was also launched much later, which actually cancelled out the performance benefit of fused optimizer.

See the attached screenshots of the two trace files:

**1. Original Unfused Version:**
![unfused version](https://github.com/pytorch/pytorch/assets/8884619/8e28e3d1-ff6a-43be-80bf-2b69d4a862c8)

**2. Fused Version in v2.0.1:**
![fused version](https://github.com/pytorch/pytorch/assets/8884619/aef8333a-b0ed-479e-be53-34e03ba5e239)


Will there be any further optimization to handle this issue and deliver more actual speedup?

### Versions

PyTorch 2.0.1

cc @vincentqb @jbschlosser @albanD @janeyx99
Repository: next.js
Issue: Incorrect port when dynamically generating open graph images (port specified during next dev command)
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.3.0: Thu Jan  5 20:48:54 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.14.0
      npm: 9.3.1
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.2
      eslint-config-next: 13.1.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.4
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/pedantic-sound-1cbryd?file=%2Ftsconfig.json%3A1%2C1

### To Reproduce

1. Run `next dev -p 4000`
2. Go to the about page `/about`
3. Verify the open graph image is generated with the default `localhost:3000` and not `localhost:4000`

### Describe the Bug

The open graph and twitter images dynamically generated (by file) are generated with the incorrect port when specifying a port as part of the `next dev` command

### Expected Behavior

Expect that the metadata images are generated with the correct port.

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

_No response_

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

_No response_
Repository: pytorch
Issue: Operations to shared tensors in the forked process could lead to silent crash
Labels: module: multiprocessing,triaged

### 🐛 Describe the bug

I am using `torch.multiprocessing` with the `fork` context, but the forked processes would mysteriously crash, with no exception thrown. I have minimize the scope of the problem into the following example:

```python
import torch
import torch.multiprocessing as torch_mp

def fn(q):
    tensor = q.get()
    print(tensor, tensor.is_shared())
    tensor += 1 # process silently crashes
    print("OK")

def test():
    ctx = torch_mp.get_context('fork')
    q = ctx.Queue()
    tensor = torch.zeros(1024*1024)
    q.put(tensor)
    proc = ctx.Process(target=fn, args=(q,))
    proc.start()
    proc.join()

if __name__ == "__main__":
    torch_mp.set_start_method('fork')
    test()
```

If, however, the tensor is created with `torch.randn` or `torch.empty`, the program wouldn't crash. `torch.ones, torch.arange` lead to crashes. Using the `spawn`/`forkserver` contexts also works.

Is this the expected behavior with `fork`?

### Versions

Tested with pytorch 2.0.1 under linux.

cc @VitalyFedyunin @ejguan
Repository: pytorch
Issue: Docs suggestion `FullyShardedDataParallel.summon_full_params` must be called on all ranks/processes
Labels: triaged,module: fsdp

### 📚 The doc issue

The docs for [summon_full_params](https://pytorch.org/docs/stable/fsdp.html#torch.distributed.fsdp.FullyShardedDataParallel.summon_full_params) don't state that it must be called on all processes. I think I was lead astray by the `rank0_only` argument, thinking that I'd get what I need only calling the context manager on the rank 0 process, but instead things hang (at least with `with_grads=True`).

I am guessing under the hood all_gather is being called, which would explain the hanging. But that's not explicit in the docs.

### Suggest a potential alternative/fix

Add a Note to the docs for summon_full_params that it should be called on all ranks, even if parameters are only being used on one process.

cc @zhaojuanmao @mrshenli @rohan-varma @awgu
Repository: storybook
Issue: [Bug]: storyName cannot be set during instantiation
Labels: bug,question / support,csf3

### Describe the bug

Creating a story, and then defining the storyName works:
```
export const Primary: Story = {
  args: {
    primary: true,
    label: 'Button',
  },
};
Primary.storyName = 'Example';
```

However, defining it during instantiation does not work:
```
export const Primary: Story = {
  args: {
    primary: true,
    label: 'Button',
  },
  storyName: 'Example',
};
```

### To Reproduce
1. Create a storybook 7 with React and TypeScript project
2. Update Button story to contain storyName within the Primary curly braces
3. Run storybook


### System

```shell
Environment Info:

  System:
    OS: macOS 13.3.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 16.18.0 - ~/.nvm/versions/node/v16.18.0/bin/node
    npm: 8.19.2 - ~/.nvm/versions/node/v16.18.0/bin/npm
  Browsers:
    Chrome: 113.0.5672.92
    Edge: 113.0.1774.35
    Safari: 16.4
  npmPackages:
    @storybook/addon-a11y: ^7.0.11 => 7.0.11
    @storybook/addon-essentials: ^7.0.11 => 7.0.11
    @storybook/addon-interactions: ^7.0.11 => 7.0.11
    @storybook/addon-jest: ^7.0.11 => 7.0.11
    @storybook/addon-links: ^7.0.11 => 7.0.11
    @storybook/preset-create-react-app: ^7.0.11 => 7.0.11
    @storybook/react-webpack5: ^7.0.11 => 7.0.11
    @storybook/testing-library: ^0.1.0 => 0.1.0
```


### Additional context

_No response_
Repository: rust
Issue: `char` open ended range isn't bounded by `char::MAX`
Labels: A-Unicode,C-bug,T-libs

I tried this code:

```rust
for _ in '\0'.. {}
```

I expected to see this happen: Runs without error.

Instead, this happened:
```
thread 'main' panicked at 'overflow in `Step::forward`', /rustc/2a8221dbdfd180a2d56d4b0089f4f3952d8c2bcd\library\core\src\iter\range.rs:88:45
```

### 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.71.0-nightly (2a8221dbd 2023-05-11)
binary: rustc
commit-hash: 2a8221dbdfd180a2d56d4b0089f4f3952d8c2bcd
commit-date: 2023-05-11
host: x86_64-pc-windows-msvc
release: 1.71.0-nightly
LLVM version: 16.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>

```
   0: std::panicking::begin_panic_handler
             at /rustc/2a8221dbdfd180a2d56d4b0089f4f3952d8c2bcd/library\std\src\panicking.rs:578
   1: core::panicking::panic_fmt
             at /rustc/2a8221dbdfd180a2d56d4b0089f4f3952d8c2bcd/library\core\src\panicking.rs:67
   2: core::panicking::panic_display
             at /rustc/2a8221dbdfd180a2d56d4b0089f4f3952d8c2bcd/library\core\src\panicking.rs:150
   3: core::panicking::panic_str
             at /rustc/2a8221dbdfd180a2d56d4b0089f4f3952d8c2bcd/library\core\src\panicking.rs:134
   4: core::option::expect_failed
             at /rustc/2a8221dbdfd180a2d56d4b0089f4f3952d8c2bcd/library\core\src\option.rs:1932
   5: core::iter::range::Step::forward
   6: core::iter::range::<impl core::iter::traits::iterator::Iterator for core::ops::range::RangeFrom<A>>::next
   7: core::fmt::Arguments::new_v1
   8: core::ops::function::FnOnce::call_once
```

</p>
</details>