sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: codec_test.dart emits error output but still passes
Labels: a: tests,engine,P3,c: tech-debt,team-engine,triaged-engine

See some comments at https://skia-review.googlesource.com/c/skia/+/790318?tab=comments

A successful test run includes error output:

```
[ERROR:flutter/lib/ui/painting/image_generator.cc(31)] Failed to get pixels for image.
[ERROR:flutter/lib/ui/painting/image_generator.cc(31)] Failed to get pixels for image.
[ERROR:flutter/lib/ui/painting/image_decoder_skia.cc(290)] Could not decompress image.
[ERROR:flutter/lib/ui/painting/image_decoder_skia.cc(290)] Could not decompress image.
```

(There's two because two tests are being run in parallel).

This is coming from  "Animated apng background color restore" test in [flutter/testing/dart/codec_test.dart](https://github.com/flutter/engine/tree/1e90180a92b627caf602c71a9387dc55a6d6b5db/testing/dart/codec_test.dart#L233)

It's not clear to me why this is happening - we should either fix the test so that it fails if this is a problem, or not log the error if it isn't actually an actionable error.
Repository: next.js
Issue: `generateMetadata()` in root `layout.tsx` is called on every navigation
Labels: bug

### Link to the code that reproduces this issue

https://github.com/kevinmitch14/reproduction-app

### To Reproduce

Go to page /1 and continue to navigate through pages via Link (1, 2, 3, 4...)

### Current vs. Expected behavior

**Behaviour:**
When using `fetch`, results in `generateMetadata()` are the same on every refresh/navigation.
When not using `fetch()` or adding a an artificial delay, the computation is done on every page navigation. 

**Expectations:**
`generateMetadata()` in layout.tsx is not called on every navigation. Similar to how layout.tsx does not re-render/re-fetch on navigation.


Context: I want to display a metadata icon based on the route. I need to fetch the image from a remote DB. This image does not change, it only needs to be fetched in root layout. I am not using `fetch`

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 8.15.1
Relevant Packages:
  next: 14.1.1-canary.57 // Latest available version is detected (14.1.1-canary.57).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata (metadata, generateMetadata, next/head)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

I also have another issue filed at #62162. Would be good to clarify if `cache()` is relevant to `generateMetadata()`. It seems it is from the docs, but it is not clear if generateMetadata() has access to the cache context.
Repository: deno
Issue: Tooling for generating a browser compatible import map for JSR specifiers
Labels: suggestion,jsr

It would be nice to develop some tooling for generating an import map for JSR specifiers that could then be used in the browser. Probably this could be an external tool that's a package on jsr that looks at the `deno info --json` output then creates an import map.
Repository: pytorch
Issue: [memory profiler] keep consistent MB/MiB between y-axis and CUDACachingAllocator size
Labels: triaged

### 🐛 Describe the bug

https://zdevito.github.io/assets/viz/

see snapshot Y-axis use 524MB and CUDACachingAllocator size use 500MiB. Ideally we should stay with one unit. otherwise I have to do the MB -> MiB converstion mannually every time 

<img width="184" alt="Screenshot 2024-02-16 at 11 52 24 AM" src="https://github.com/pytorch/pytorch/assets/134637289/1c8c712f-9554-400e-bef7-99665292e175">


### Versions

skip
Repository: pytorch
Issue: Weird Artifact name: 'not_implemented' not registered being raised
Labels: module: logging,triaged,module: fakeTensor

### 🐛 Describe the bug

@atalman is aware of this issue that only repros on Meta's internal tests
This currently blocks https://github.com/pytorch/pytorch/pull/108186, so a workaround is being created and this issue should track it

References:
* https://github.com/pytorch/pytorch/pull/108186#issuecomment-1929816055
* https://github.com/pytorch/pytorch/pull/108186#issuecomment-1930352099
* https://github.com/pytorch/pytorch/pull/119990#discussion_r1491581071

### Versions

main

cc @eellison
Repository: pytorch
Issue: [feature request] keep gradcheck numerical jacobian from being depeciated
Labels: feature,module: autograd,triaged,needs research

## Issue description

Computing Jacobians for large/complex calculations can produce computational graphs too large to fit in memory, however a finite difference Jacobian does not need to store the graph in memory and so can be used on larger models. 

In my case I am using PyTorch to solve parametric models on Astronomical images using Levenberg-Marquardt. I have been using the autograd jacobian, however I apply several tricks to ensure the Jacobian never gets too large in memory. I just found the numerical Jacobian in the API and now I learn it is being depreciated! It would be great if it could be kept, even in its current mostly private form that would be useful to me.

Here is the line which says the numerical Jacobian will be depreciated: https://github.com/pytorch/pytorch/blob/4319735ace2fe00ce720db00119e08d56d6c344c/torch/autograd/gradcheck.py#L328

Also, in some cases a numerical Jacobian is actually faster than autograd and so would provide some acceleration.

## Code example

Here is my Repo where I use PyTorch for astronomical images: https://github.com/Autostronomy/AstroPhot

If you run it on a large enough image it will crash, though I have several features in the code which break up images until they are small enough to run without crashing it would be great to not need these. 


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: godot
Issue: CharacterBody2D slide breaks on uneven-scaled StaticBody2D
Labels: documentation,topic:physics

### Tested versions

- Reproducible in 4.2.1 stable [b09f793f5]

### System information

Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 Laptop GPU (NVIDIA; 31.0.15.4617) - 12th Gen Intel(R) Core(TM) i5-12500H (16 Threads)

### Issue description

#### Issue:
If a CharacterBody2D tries to slide on a StaticBody2D that has a collision shape with uneven-scaling (X scale doesn't match Y scale) and hits an edge not axis-aligned (so, at an angle), it appear to quickly slide (sometimes instantly) to one vertex of the shape.
#### Expected:
The CharacterBody2D slide velocity is independent of the object's scale.

#### Demo: 
https://github.com/godotengine/godot/assets/74799857/51d85a52-b824-4250-a8a5-459fdaefc8eb



#### Details:
The difference between the scales will magnify the process. A scale of (0.5, 0.52) will have the CharacterBody slide quicker than usual, while a scale of (0.5, 0.2) will have it move instantly. 
Increasing the scale difference drastically has the object teleport while not even close to the shape.
This happens if either the StaticBody object, the CollisionShape object, or a parent of the StaticBody object have uneven-scale.

An even scale like (0.5, 0.5)  does not present this behavior.
Scaling the CharacterBody does not influence this in any way.

#### Context
I found this bug when one of the designers on my team wanted to make one of the levels slimmer so we scaled down the parent scene, and this affected all objects, and we couldn't replicate the bug in other scenes. I later found this bug when trying to make ellipsis colliders for props in a level.

The fact wild differences in scale have the character teleport while not even touching the shape has me think that the engine is using either the unscaled shape or only one of the scale coordinates to some of the calculations.

I suppose you're not intended to scale StaticBodies this way, but this not only limits what you can do with them (say, no Ellipsis shapes), but I also think it doesn't match expected behavior: if you scale a CharacterBody in a similar way, it slides as usual with no problems.

### Steps to reproduce

- Create a CharacterBody2D node (any motion mode)
- Make boilerplate movement code using ``move_and_slide()``
- Create a StaticBody2D with any CollisionShape with sides not aligned to the xy axis (like a rotated Rectangle, or Sphere)
- Scale either the StaticBody2D or the CollisionShape such that the X scale is not equal to the Y scale (click on Unlock Component Ratio)
- Run scene, try to walk over to the static body, the character should quickly slide to one particular edge and get stuck.

### Minimal reproduction project (MRP)

[CharacterBody2DSlideBug4.2.1.zip](https://github.com/godotengine/godot/files/14315343/CharacterBody2DSlideBug4.2.1.zip)
Repository: flutter
Issue: Android `scenario_app` does not have a consistent background color (on CI?)
Labels: platform-android,P3,team-engine,triaged-engine,e: scenario-app

_🚫 Blocking https://github.com/flutter/flutter/issues/143471_.

In https://github.com/flutter/engine/pull/50722, which should have no effect on goldens, I get a (flaky) diff:

![image](https://github.com/flutter/flutter/assets/168174/46147232-3b35-4e43-abed-b89338a4aad5)

Let me 🔍  in:

![image](https://github.com/flutter/flutter/assets/168174/e06ad55a-d7b1-4c99-bc8c-4bdf8d788412)

Location | Left Pixel | Right Pixel
|--------|--------- | -----------
0x0        | `#373737` | `#000000`
1x0         | `#090909` | `#000000`

In other words, sometimes the screen is entirely pure black (`#000000`), and sometimes the top has a dark grey 1-pixel border that is `#373737`, with the remaining screen being _almost_ black (`#090909`). I don't see any of those colors referenced _directly_ in the app.

Some other thoughts:

- Flutter is not full screen (per @jonahwilliams it would be "clear to transparent black")
- It's likely the non "pure-black" screen is some sort of inherited "Dark Mode" color scheme
- We are not explicitly setting the theme anywhere, maybe some CI configurations are different?

For onlookers, the app is here: https://github.com/flutter/engine/tree/main/testing/scenario_app/android.

/cc @reidbaker @johnmccutchan if anything stands out to you.
Repository: flutter
Issue: Flutter-Web-Wasm Only Loads JS and No Wasm in Firefox
Labels: platform-web,browser: firefox,P2,e: wasm,e: web_skwasm,team-web,triaged-web

It seems like the loader doesn't recognize wasm support in firefox .

### Steps to reproduce

Open [https://flutterweb-wasm.web.app](https://flutterweb-wasm.web.app/) in Firefox Version 120 or later.
Open the Network Console


### Expected results

In Chrome you can see the main.dart.wasm and main.dart.mjs loaded. This should also happen in Firefox and happened in previous versions.

### Actual results

It loads the main.dart.js as it seems that the loader decided that firefox was not supported for wasm.

### Code sample

/

### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

Not running this locally. Using the latest https://flutterweb-wasm.web.app
Repository: flutter
Issue: Sub-directories in `FLUTTER_LOGS_DIRS` result in broken links
Labels: team-infra,P3,triaged-infra

### Type of Request

bug

### Infrastructure Environment

LUCI

### What is happening?

Clicking on screenshot `png` files in the logs output of https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Engine%20Drone/2003164/overview result in broken links:

```xml
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Details>No such object: flutter_logs/flutter/a714f95f-b6ab-45e8-8257-2cae60a7ed55/Android Scenario App Integration Tests (Skia)/a714f95f-b6ab-45e8-8257-2cae60a7ed55/ExternalTextureTests_testCanvasSurface.png</Details>
</Error>
```

### Steps to reproduce

In https://github.com/flutter/engine/pull/50722, I'm writing the following to `FLUTTER_LOGS_DIR`:

```txt
FLUTTER_LOGS_DIR/
  logcat.txt
  screenshots/
    a.png
    b.png
    ...
```

The files do show up (https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Engine%20Drone/2003164/overview):

![image](https://github.com/flutter/flutter/assets/168174/27cd143f-0654-4dee-ac06-f16cfa90930d)

... but you'll notice, they all appear "flat" (no mention of the `screenshots/` directory).

### Expected results

I expected to see the image, and/or a build failure or message if I'm doing something prohibited.

I'll work around it for now.
Repository: flutter
Issue: Android plugin SDK version warning sounds severe even in cases where it is likely harmless
Labels: platform-android,tool,a: build,P2,a: plugins,team-android,triaged-android

As recommended when using endorsed packages, our app depends only on `local_auth`, which depends on local_auth_android by itself, with a ^1.0.0 clause.

`local_auth_android` updated the compileSdk from 33 to 34 on a **patch version** (1.0.36 to 1.0.37), so when we ran a fresh build on our CI  the new version was automatically installed by flutter pub and the project started demanding a new compileSdk version even though we did not change any dependencies on **pubspec.yaml**.

Shouldn't an update this relevant be made only on a major (or at least a minor) version? Specially on an endorsed package, which repos should not have to worry too much about. We were about to release a new version to the app stores when we were surprised by this warning and it disrupted our entire evening.

I know bumping the compileSdk version of the app is good and necessary from time to time, but this is a change on the code that demands many testings on the app... It is something we would like to do when planned and not rushed out because of a patch update of an endorsed package.

Should we expect more updates like this from the official packages? Should I lock the versions of **all** the endorsed packages to make sure my codebase stay stable?

---

### What package does this bug report belong to?

local_auth

### What target platforms are you seeing this bug on?

Android

### Have you already upgraded your packages?

Yes

### Dependency versions

<details><summary>pubspec.lock</summary>

```lock
local_auth:
    dependency: transitive
    description:
      name: local_auth
      sha256: "27679ed8e0d7daab2357db6bb7076359e083a56b295c0c59723845301da6aed9"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.8"
  local_auth_android:
    dependency: transitive
    description:
      name: local_auth_android
      sha256: "3bcd732dda7c75fcb7ddaef12e131230f53dcc8c00790d0d6efb3aa0fbbeda57"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.37"
  local_auth_ios:
    dependency: transitive
    description:
      name: local_auth_ios
      sha256: "6dde47dc852bc0c8343cb58e66a46efb16b62eddf389ce103d4dacb0c6c40c71"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.7"
```
</details>
Repository: pytorch
Issue: Use Incremental Fake Tensor Updater more uniformly across torch.compile compilation
Labels: triaged,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

We currently have a number of passes that modify the graph, such as those in post_grad or pre_grad. However, we don't have any uniform way to ensure that those passes preserve correct metadata after they're complete.

We have a incremental FakeTensorUpdater class that incrementally updates the faketensor after a graph modification, but it's not currently uniformly used across our passes: https://github.com/pytorch/pytorch/blob/main/torch/_inductor/fx_utils.py#L46 We should standardize and use this across all our passes to prevent hard to debug issues.



### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @amjames
Repository: transformers
Issue: Add Support for Dataclasses to Trainer
Labels: trainer,Feature request

### Feature request

Update Trainer._prepare_input to natively support python dataclasses for support of more structured objects.

### Motivation

_prepare_input will seamlessly transfer the tensors contained in many datatypes (list, tuple, dict, etc.) to the appropriate device. However, it will not do so for dataclass objects.

Python dataclasses often provide better ergonomics than TypedDict, which is likely the closest supported alternative. Adding support appears to be a small change to the codebase with nice benefits to the user.

### Your contribution

If the PR is as simple as it initially appears, I would be willing to submit a PR.
Repository: next.js
Issue: Images not loading in NextJS 14 Headless WordPress demo fresh install
Labels: examples

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.57 // Latest available version is detected (14.1.1-canary.57).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

cms-wordpress

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

Chrome 121.0.6167.185

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

Vercel, local

### Describe the Bug

I tried to deploy "cms-wordpress" template on vercel.com and when you access the project website the images are not displaying.

I followed the steps exactly as shown here: [ISR Blog with Next.js and WordPress](https://vercel.com/templates/next.js/isr-blog-nextjs-wordpress)

I did set the env variables when i deployed on Vercel and all of the data loads fine but the images are not working.

When run locally i get the following error :
Error: Invalid src prop <url> on `next/image`, hostname <hostname> is not configured under images in your `next.config.js`
![image](https://github.com/vercel/next.js/assets/58997519/68b961c8-d035-4659-bcd5-3bbda58b59d6)

See also this discussion: [Images not loading in NextJS 14 Headless WordPress demo fresh install #62163](https://github.com/vercel/next.js/discussions/62163)

### Expected Behavior

The expected behavior is that the images works out-of-the-box, below is how i fixed it:

1. The provided next.config.js is this:
![image](https://github.com/vercel/next.js/assets/58997519/d62fb59b-c697-4c9f-a3d4-6ef01032d976)
it doesn't work!

2. It should be changed to this:
[next.config.js](https://gist.github.com/LunatikDev/d070e41eb8a34a21c1d831f1750380a5)
![image](https://github.com/vercel/next.js/assets/58997519/cb75929c-2f4c-4b71-9790-76500c72688e)
Without the parameters:

swcMinify: true,
optimizeFonts: true,
minimumCacheTTL: 15000000

It will not work!

Also the hostname "secure.gravatar.com" should be added because profile avatars on latest wordpress are handled by gravatar !

### To Reproduce

1. Follow tutorial [ISR Blog with Next.js and WordPress](https://vercel.com/templates/next.js/isr-blog-nextjs-wordpress)
2. Try to deploy to Vercel.com, you will see that images are not showing.
3. Try to run localy with npm run dev,
4. Try to access website, an error will be thrown:

Error: Invalid src prop <url> on `next/image`, hostname <hostname> is not configured under images in your `next.config.js`
![image](https://github.com/vercel/next.js/assets/58997519/22fc9429-1551-487f-a558-c2cf643af506)
Repository: pytorch
Issue: Tracking issue for PT2 dashboard training passrate
Labels: triaged,oncall: pt2

This issue tracks the PT2 dashboard training pass rate (excluding dynamic shape). The pass rate is already pretty high so the issue just list the failed models and track the progress of fixing them.

# TB

- [x] yolov3: fail with eager_two_runs_differ in cudagraphs setting. The error is transient. It passes for the last 7 days. We should keep watching it for a bit longer (2024 Feb22).
- [ ] vision_maskrcnn: fail with 'fail_accuracy' in default/cudagraphs setttings; fail with 'fail_to_run' in maxautotune setting.
- [x] torchrec_dlrm: fail with 'fail_accuracy' in maxautotune setting. https://github.com/pytorch/pytorch/pull/122012
- [ ] hf_Whisper: fail with 'fail_accuracy' in maxautotune setting. This one is flaky [link](https://hud.pytorch.org/benchmark/torchbench/inductor_max_autotune?startTime=Fri,%2001%20Mar%202024%2022:39:21%20GMT&stopTime=Fri,%2015%20Mar%202024%2021:39:21%20GMT&granularity=hour&mode=training&model=hf_Whisper&dtype=amp&lBranch=main&lCommit=660ec3d38d9d1c8567471ae7fe5b40ae7c6d7438&rBranch=main&rCommit=f351a71dbb68fa4a595e23e8c4be41e32a317742). Can not repro locally
- [x] tts_angular: pass accuracy test but fail performance run in cudagraphs/maxautotune settings. https://github.com/pytorch/pytorch/issues/120474

# HF

- [ ] DebertaForQuestionAnswering: fail with 'fail_accuracy' in maxautotune setting. Fail quite consistently on the dashboard [link](https://hud.pytorch.org/benchmark/huggingface/inductor_max_autotune?startTime=Sat,%2016%20Dec%202023%2022:57:37%20GMT&stopTime=Fri,%2015%20Mar%202024%2021:57:37%20GMT&granularity=day&mode=training&model=DebertaForQuestionAnswering&dtype=amp&lBranch=main&lCommit=b7f25226929e70187a9f36c393665abad0b25190&rBranch=main&rCommit=622947afa86b1c9c3db37466f43984c73db77677), but can not repro locally.

# TIMM

- [ ] mobilenetv2_100: fail with 'fail_accuracy' in maxautotune setting. Fail quite consistently on the dashboard [link](https://hud.pytorch.org/benchmark/timm_models/inductor_max_autotune?startTime=Sat,%2016%20Dec%202023%2023:16:38%20GMT&stopTime=Fri,%2015%20Mar%202024%2022:16:38%20GMT&granularity=day&mode=training&model=mobilenetv2_100&dtype=amp&lBranch=main&lCommit=b7f25226929e70187a9f36c393665abad0b25190&rBranch=main&rCommit=622947afa86b1c9c3db37466f43984c73db77677), but can not repro locally

# Tracking regressions
- [ ] DebertaForQuestionAnswering and nanogpt regression. https://github.com/pytorch/pytorch/issues/122987







cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @penguinwu @eellison
Repository: flutter
Issue: [Impeller] Unskip disabled tests for flutter Test --enable impeller.
Labels: P2,e: impeller,team-engine,triaged-engine

We'd like to get additional test coverage via framework tests and goldens. Before we can do this, we need to skip some subset of tests that don't work and find a way to deal with golden diffs on a roll.

Edit: the singular issue causing trouble across the repo is that rotated text goldens are unstable, which is a problem given the propensity to include the debug banner in goldens. Where this is a problem I'll be disabling it, we can handle fixes and investigations as a follow up.
Repository: rust
Issue: cannot use mem::offset_of! with unions due to ManuallyDrop interfering
Labels: T-compiler,C-bug,T-libs,F-offset_of_nested

When a union contains a non-`Copy` variant, the compiler forces the user to wrap it in `ManuallyDrop`. `ManuallyDrop` is guaranteed to have the same layout as the underlying type, but it is opaque to offset_of! because the `value` field is private.

here is an example that fails to compile

```rs
#![feature(offset_of_nested)]
use core::mem;
struct X { foo: usize }
union N { X: mem::ManuallyDrop<X> }
const o: usize = mem::offset_of!(N, X.value.foo);
```

playground link: (https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=84fadd9f1808d5ff7b52de9e1f0ab6b4)