sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Re-enable skipped 3.12 dynamo-wrapped profiler tests
Labels: oncall: profiler,module: python version

This PR (https://github.com/pytorch/pytorch/pull/124124) disabled some profiler tests in the dynamo-wrapped test shard.

Locally, on both eager and `PYTORCH_TEST_WITH_DYNAMO=1`, the test `profiler/test_profiler.py::TestProfiler::test_tensorboard_trace_handler` passes and the rest give the error `RuntimeError: !stack.empty() INTERNAL ASSERT FAILED at "/data/users/williamwen/pytorch/torch/csrc/autograd/profiler_python.cpp":969, please report a bug to PyTorch. Python replay stack is empty.`

cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise
Repository: pytorch
Issue: Initial state of RNNs: h_0 or hx?
Labels: module: nn,module: rnn,triaged

### 📚 The doc issue

Looking at the documentation of the vanilla RNN in  https://pytorch.org/docs/stable/generated/torch.nn.RNN.html#rnn, 
the initial state (second argument of forward) is called h_0, but in the code it is actually hx.

The same "issue" seems to be there for other recurrent nets, e.g. LSTM

### Suggest a potential alternative/fix

A simple renaming would do. I'd go for h0, but perhaps hx was thought to be more general for the case of bidirectional=True.

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: ollama
Issue: Support for HuggingFaceM4/idefics2-8b as a vision model
Labels: model request

### What model would you like?

Can you add support for the various new promising Idefics V2 from huggingface
https://huggingface.co/HuggingFaceM4/idefics2-8b
https://huggingface.co/blog/idefics2
it's a multimodal with OCR and vision (chatty will follow soon)
Repository: flutter
Issue: [google_maps_flutter] Remove `GoogleMapsPrivacy` manifest entries from plugin after future SDK update
Labels: platform-ios,p: maps,package,P2,c: tech-debt,team-ios,triaged-ios

See https://github.com/flutter/packages/pull/6511 for full context.

Because the current release of the Google Maps SDK does not contain a manifest, the [official docs for the Google Maps SDK](https://developers.google.com/maps/documentation/ios-sdk/config#add-apple-privacy-manifest-file) instruct developers to download a separate bundle that has the manifest entries for version 8.4 and add it to their app. For posterity since that page will presumably change once there's a release with its own manifest:

> 1. Download the Privacy Manifest bundle for the Maps SDK for iOS: [GoogleMapsPrivacy](https://dl.google.com/geosdk/PrivacyManifests/GoogleMapsPrivacy.bundle.zip).
> 2. Extract the file to access GoogleMapsPrivacy.bundle.
> 3. Copy GoogleMapsPrivacy.bundle into your Xcode project's top level directory.

Because there's already a lot of confusion around the whole manifest rollout, and because this is not at all standard for how manifests work in SDKs, we have opted to shield package clients from this temporary anomaly by folding the contents of that bundle directly into the plugin. Because the plugin is built statically, it has the effect of automatically putting that manifest into a bundle in the app (just with a different name, but that should be irrelevant).

Long term, we don't want to keep this workaround. Most importantly, once there's a new version of the SDK with its own manifest, the contents of that manifest could change at any time, and then our version would be wrong. So once a new version comes out with a manifest, we should revert to having an empty manifest for the plugin (since the plugin code doesn't do anything requiring manifest entries).

There is one caveat here: it may be that the first version that has a manifest also drops iOS 14 support. If that happens, we will have to decide between:
1. Removing our manifest entries, setting the min SDK version to that version, and dropping iOS 14 support.
2. Removing our manifest entries, not changing the constraints, and documenting in the README that users supporting iOS 14 have to do the `GoogleMapsPrivacy` bundle workaround themselves, manually.
3. Keeping our manifest entries indefinitely (in which case they will be duplicative, and potentially over time include things that aren't actually being done any more by newer SDK versions, although that seem relatively unlikely).
Repository: opencv
Issue: Add CORP header to opencv.js
Labels: category: infrastructure,category: javascript (js)

### Describe the feature and motivation

Currently resources with COEP `require-corp` that attempt to load https://docs.opencv.org/4.x/opencv.js cannot load it because it lacks a CORP header. Can you add the `Cross-Origin-Resource-Policy: cross-origin` header to the resource (and other versions)?

### Additional context

_No response_
Repository: TypeScript
Issue: Assigning a @type to an async function emits an error
Labels: Bug,Help Wanted,Domain: JSDoc

### 🔎 Search Terms

ts1065 jsdoc async return promise

### 🕗 Version & Regression Information

- This changed between versions `5.1.6` and `5.2.2`


### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.2.2&filetype=js#code/PQKhAIAEBcE8AcCmATRAzcBvAFASnALwB84ACgE4D2AtgJYDOiAPAG6W3IkA+4bHAvuACC9WADsAxgDEx4EMABQC0BBgJEWEeOljB8hRMpj60cNVhbJMwuACGoyeDyESmfkA

### 💻 Code

JSDoc version:
```js
/** @typedef {() => Promise<void> | void} AsyncFn */

/** @type {AsyncFn} */
const myAsyncFn = async () => {}
```

TypeScript equivalent:
```ts
type AsyncFn = () => Promise<void> | void;

const myAsyncFn : AsyncFn = async () => {}
```


### 🙁 Actual behavior

JSDoc version emits an error, TypeScript equivalent does not.

### 🙂 Expected behavior

Neither should emit an error.

### Additional information about the issue

I'm fairly sure this is related to a change from a while back where a `new Promise` needs to be explicitly marked as returning `Promise<void>`, which was intentional. But I can't seem to find the related issue anymore so I'm not sure if this is intentional as well.

Either way, the fact that this error is only emitted in JavaScript files seems to suggest that it's a bug.
Repository: godot
Issue: ResourceLoader type hint works with text but not binary resources
Labels: bug,topic:core,topic:gdscript

### Tested versions

- Reproducible in: Godot v4.3.dev4

### System information

Godot v4.3.dev4 - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 970 (NVIDIA; 31.0.15.5152) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)

### Issue description

When loading a custom resource file with a type hint, the loading fails for binary resource files but not text resource files.

### Steps to reproduce

- Create a custom resource class
- Save the resource using ResourceSaver as a binary file
- Load the resource with ResourceLoader and the class name as type_hint

### Minimal reproduction project (MRP)

[TypeHintError.zip](https://github.com/godotengine/godot/files/15001744/TypeHintError.zip)
Repository: go
Issue: x/pkgsite/cmd/pkgsite: Use relative links for `static`, etc.
Labels: NeedsInvestigation,pkgsite

### What is the URL of the page with the issue?

N/A

### What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36

### Screenshot

![CleanShot 2024-04-16 at 12 41 16](https://github.com/golang/go/assets/129629/db166bf1-cc04-4b0c-9629-163339c8fab8)


### What did you do?

When running `pkgsite -open .` locally in a remote Visual Studio Code terminal (via [code-server](https://github.com/coder/code-server)), a proxy will be started.

https://coder.com/docs/code-server/latest/guide#stripping-proxyport-from-the-request-path

This typically means that the main page will be at https://${hostname}/proxy/8080/ and the `static` directories will be under the path `/proxy/8080/static/`. However, it appears that the site always tries to find them under `/static`, and there is no obvious way to change this.

### What did you see happen?

None of the static CSS or images will load.

### What did you expect to see?

All of the static CSS and images load.
Repository: ant-design
Issue: Table - Extra padding below last row caused by setting the scollY
Labels: Inactive,improvement

### Reproduction link

[[https://codepen.io/pen?&editors=001](https://codepen.io/pen?&editors=001)](https://codepen.io/Kevin-Wang-the-selector/pen/NWmLLeW?editors=001)

### Steps to reproduce

Please see the link and scroll to the last row

### What is expected?

The scroll Y should be flush with the last row leaving no additional padding. This is caused by incorrect calculation of Table body element

### What is actually happening?

Extra padding is visible on the last table row

| Environment | Info |
| --- | --- |
| antd | 5.16.2 |
| React | 18.2.0 |
| System | Web |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: [Fancy zones] Please add support for Unity Editor [2023 or newest] windows.
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage,Area-App Compat

### Description of the new feature / enhancement

In Unity 2023, each window in the Editor [like Game view, Scene viev etc.] has its own handler with default Windows frame with minimize, maximize and exit buttons, which is recognized by the Windows function of snapping windows to zones, but unfortunately Fancy Zones does not detect them. It would be great if Fancy Zones could detect these windows, then working with Unity would be even better!

### Scenario when this would be used?

In Game Developing in Unity 2023 and newest

### Supporting information

_No response_
Repository: terminal
Issue: "Restore last closed tab" action always restores tabs as panes 
Labels: Issue-Bug,Area-UserInterface,Product-Terminal

v1.20.11072.0 (bug bash on 4/16)

"Restore last closed tab" action always restores tabs as panes
Repository: go
Issue: x/oauth2: TestExchangeRequest_JSONResponse failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "golang.org/x/oauth2" && test == "TestExchangeRequest_JSONResponse"
```

Issue created automatically to collect these failures.

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

    --- FAIL: TestExchangeRequest_JSONResponse (0.01s)
        oauth2_test.go:191: Unexpected authorization header,  is found.
        oauth2_test.go:202: Unexpected exchange payload, client_id=CLIENT_ID&client_secret=CLIENT_SECRET&code=exchange-code&grant_type=authorization_code&redirect_uri=REDIRECT_URL is found.


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: terminal
Issue: CMD cursor starts placed on wrong line, when pane is opened to 46 columns
Labels: Area-Output,Issue-Bug,Product-Terminal

_PROBABLY_ not 1.20 related, but something else?
Open a terminal that's 97 columns wide, then split a pane with cmd, s.t. the new pane is 46 columns wide. 

![image](https://github.com/microsoft/terminal/assets/18356694/4a6453f0-615d-4eb2-8789-113e15ff217f)

The cursor in the second pane starts on the wrong line?

Note also: the second line of the Microsoft copyright notice at the top wraps onto the third row, and there's no gap between copyright and prompt. 

I observed this on 1.19.10821.0
Repository: pytorch
Issue: Bot to recomment on high pri issues if no activity 
Labels: triaged,module: devx

As in title, create a bot or action that relabels issues with `triage review` if the issue was  high pri but hasn't had activity for 3+ months

This was briefly mentioned during triage review but not written down anywhere I can find

Concerns: there are currently 400 issues with high pri label, most (250+) from 3+ months ago and oldest of which is from 2017 
This should help with a subset of https://github.com/pytorch/pytorch/issues/124016

cc @ZainRizvi @kit1980 @huydhn
Repository: rust
Issue:  `#[link(kind = "static", name = "c")]` segfaults on run
Labels: A-linkage,O-linux,T-compiler,C-bug

While working on https://github.com/rust-lang/rust/pull/123974, I had a failure when running doctests of the unstable book. Rustdoc generates this code:

```rust
#![allow(unused_extern_crates)]
#![allow(internal_features)]
#![feature(test)]
#![feature(rustc_attrs)]
#![feature(coverage_attribute)]
#![feature(link_arg_attribute)]

#![allow(unused)]
extern crate test;
mod __doctest_0 {

fn main()  {
    #[link(kind = "link-arg", name = "--start-group")]
#[link(kind = "static", name = "c")] // Causing the segfault
#[link(kind = "static", name = "gcc")]
#[link(kind = "link-arg", name = "--end-group")]
extern "C" {}
}
#[rustc_test_marker = "/home/imperio/rust/rust/src/doc/unstable-book/src/language-features/link-arg-attribute.md - The_tracking_issue_for_this_feature_is__ (line 11)"]
pub const TEST: test::TestDescAndFn = test::TestDescAndFn {
    desc: test::TestDesc {
        name: test::StaticTestName("/home/imperio/rust/rust/src/doc/unstable-book/src/language-features/link-arg-attribute.md - The_tracking_issue_for_this_feature_is__ (line 11)"),
        ignore: false,
        ignore_message: None,
        source_file: "_home_imperio_rust_rust_src_doc_unstable_book_src_language_features_link_arg_attribute_md",
        start_line: 11,
        start_col: 0,
        end_line: 0,
        end_col: 0,
        compile_fail: false,
        no_run: true,
        should_panic: test::ShouldPanic::No,
        test_type: test::TestType::UnitTest,
    },
    testfn: test::StaticTestFn(
        #[coverage(off)]
        || test::assert_test_result(Ok::<(), String>(())),
    )
};
}

#[rustc_main]
#[coverage(off)]
fn main() {
    test::test_main(&["rustdoctest".to_string(),], vec![__doctest_0::TEST], None);
}
```

If you compile and run this program (on linux x86_64), it'll segfault. Commenting `#[link(kind = "static", name = "c")]` will make it run without problem.
Repository: pytorch
Issue: [DeviceMesh] Current cache for submesh result is not thread save
Labels: oncall: distributed,triaged

### 🐛 Describe the bug

We observe the threaded-based test are failing. 

e.g. https://github.com/pytorch/pytorch/blob/main/test/distributed/_composable/fsdp/test_fully_shard_training.py#L88 

Also, internal reported similar test failure.

### Versions

N/A

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @tianyu-l @wconstab @yf225 @chauhang
Repository: go
Issue: x/tools/gopls/internal/lsprpc: TestClientLogging failures
Labels: NeedsInvestigation,gopls,Tools

```
#!watchflakes
default <- pkg == "golang.org/x/tools/gopls/internal/lsprpc" && test == "TestClientLogging"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/9e2120ebd1483234bd78dee39d478b5051f3aef3)):

    --- FAIL: TestClientLogging (1.04s)
        lsprpc_test.go:84: timeout waiting for client log
    2024/04/16 21:24:33 New server
    	new_server="1"
    	logfile=""
    	debug_address=""
    	gopls_path="/tmp/workdir/tmp/go-build49580624/b552/lsprpc.test"
    	client_id="3"
    2024/04/16 21:24:33 forwarder: exited with error: remote disconnected: failed reading header line: read tcp 127.0.0.1:50483->127.0.0.1:30013: use of closed network connection
    2024/04/16 21:24:44 New server
    	new_server="3"
    	logfile=""
    	debug_address=""
    	gopls_path="/tmp/workdir/tmp/go-build49580624/b552/lsprpc.test"
    	client_id="6"
    2024/04/16 21:24:44 forwarder: exited with error: remote disconnected: failed reading header line: read tcp 127.0.0.1:41672->127.0.0.1:16998: use of closed network connection
    2024/04/16 21:24:44 ping
    2024/04/16 21:24:44 ping


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: react-native
Issue: Blob constructor is not spec compliant
Labels: Needs: Triage :mag:,Needs: Attention,Never gets stale

### Description

The constructor for React Native's [Blob has a comment](https://github.com/facebook/react-native/blob/8c53ac60782d8ccd2ccd7706d41e60cda93e2988/packages/react-native/Libraries/Blob/Blob.js#L57):
> "Currently we only support creating Blobs from other Blobs."

BlobManager [confirms this:](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Blob/BlobManager.js#L71)
> "Creating blobs from 'ArrayBuffer' and 'ArrayBufferView' are not supported"

This API is not spec compliant, since this is what the Blob specification [specifies](https://developer.mozilla.org/en-US/docs/Web/API/Blob/Blob): 

> (Constructed from) "An [iterable](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols#the_iterable_protocol) object such as an [Array](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array), having [ArrayBuffer](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer)s, [TypedArray](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray)s, [DataView](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DataView)s, [Blob](https://developer.mozilla.org/en-US/docs/Web/API/Blob)s, strings, or a mix of any of such elements, that will be put inside the [Blob](https://developer.mozilla.org/en-US/docs/Web/API/Blob). Strings should be well-formed Unicode, and lone surrogates are sanitized using the same algorithm as [String.prototype.toWellFormed()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/toWellFormed)."


### Steps to reproduce

1. Try to call:

```ts
new Blob(new Uint8Array([
    0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
    21, 22, 23,
  ]);
  ```
  
  See that RN doesn't support Blobs composed of anything but Blobs or strings.

### React Native Version

0.73.6

### Affected Platforms

Runtime - Android, Runtime - iOS

### Output of `npx react-native info`

```text
N/A
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

N/A

### Screenshots and Videos

_No response_
Repository: vscode
Issue: getMarkdownHeadersInCell does not handle headers with HTML tags
Labels: bug,notebook-folding,notebook-markdown,notebook-toc-outline

The `notebookOutlineEntryFactory.ts` handles markdown headers with HTML tags, but not other parts (such as collapsing mardown header cells, see `foldingModel.ts`).
```typescript
			const fullContent = cell.getText().substring(0, 10000);
			for (const { depth, text } of getMarkdownHeadersInCell(fullContent)) {
				hasHeader = true;
				entries.push(new OutlineEntry(index++, depth, cell, text, false, false));
			}

			if (!hasHeader) {
				// no markdown syntax headers, try to find html tags
				const match = fullContent.match(/<h([1-6]).*>(.*)<\/h\1>/i);
				if (match) {
					hasHeader = true;
					const level = parseInt(match[1]);
					const text = match[2].trim();
					entries.push(new OutlineEntry(index++, level, cell, text, false, false));
				}
			}
```

Thus, if we have HTML tags for outline headers, then we do not render collapsible regions in markdown for such headers.
Not sure if this is a bug or not, but filing this here, 

Feel free to close this if this is invalid.
Repository: ollama
Issue: Aya by Cohere - mt5-xxl arch
Labels: model request

### What model would you like?

https://huggingface.co/CohereForAI/aya-101

See discussion re t5 and gguf attempts here: https://huggingface.co/CohereForAI/aya-101/discussions/12
trial: https://huggingface.co/kcoopermiller/aya-101-GGUF (using candle)
Repository: flutter
Issue: TextHeightBehaviour should allow more tightly-wrapped text
Labels: c: new feature,engine,a: typography,c: proposal,P3,team-engine,triaged-engine

PROBLEM

It's not currently possible to set the spacing distance between two paragraphs of text in terms of the distance from the alphabetic baseline of the last line of the first paragraph and the top of capital letters in the second, or, equivalently, to control the spacing of a single line of text in a container such that the distance from the top edge of the container to the top of the capital letters in the text equals the distance from the alphabetic baseline to the bottom of the container.

This is, it seems, an increasingly common practice in modern online typography. CSS is intending to add something along these lines (currently under the names `text-box-trim` and `text-box-edge`, which are marked "do not implement"; no indication about whether browser vendors are interested generally; so far only Safari has attempted to implement it in their tech preview).

PROPOSAL

The cleanest way to implement this in a forward-looking fashion is probably to deprecate `TextHeightBehavior.applyHeightToFirstAscent` and `TextHeightBehavior.applyHeightToLastDescent` and to instead introduce enums that describe the top edge and the bottom edge, the top edge being for `TextHeightBehavior.top` and the bottom edge being for `TextHeightBehavior.bottom`, the values being (a subset of):

```dart
enum TextEdge {
  /// the bounding box of the font (ascent/descent of the biggest glyph)
  bounding,

  /// the distance from the baseline to the edge of the box specified by the `height` property
  /// (if `height` is null, same as `leading`)
  height,

  /// the distance from the baseline to the edge of the box specified by the font's leading metrics
  leading,

  /// the distance from the baseline to the edge of the em box
  /// (the ascent for the top edge, the descent for the bottom edge)
  em,

  /// the top of the caps edge of alphabetic characters
  caps,

  /// the top of the x-height of alphabetic characters
  x,

  /// the midpoint line between the top and bottom of the em box
  middle,

  /// the midpoint line between the baseline and the top of the x-height
  halfX,

  /// the alphabetic baseline
  alphabetic,

  /// the ideographic baseline
  ideographic,
}
```

...or some such.

So to solve the problem above one would set `TextHeightBehavior.top` to `TextEdge.caps` and `TextHeightBehavior.bottom` to `TextEdge.alphabetic`.

I don't think we need to support most of those values right away. To support the current boolean, we would need `height` (true) and `em` (false); to add the feature described above we'd need to add `caps` and `alphabetic`.

FUTURE

I think in due course we could take it further and add `TextHeightBehavior` to `TextStyle` to control what `TextStyle.background` paints over.