sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Can't call `emit_signal()` within a Thread in 4.X.
Labels: discussion,topic:core

### Godot version

4.1

### System information

Windows 10

### Issue description

Simple as the title describes, not sure if this is intended now but it sure is annoying that it's no longer possible.

**The Error that is Thrown:**
```
E 0:00:02:0389   Node::emit_signalp: Caller thread can't call this function in this node (/root/Thread Hooking). Use call_deferred() or call_thread_group() instead.
  <C++ Error>    Condition "!is_accessible_from_caller_thread()" is true. Returning: (ERR_INVALID_PARAMETER)
  <C++ Source>   scene\main\node.cpp:3563 @ Node::emit_signalp()
```


### Steps to reproduce

the code which throws said error:

```gdscript
var thread = Thread.new()
signal thread_frame


func thread_process():
	emit_signal("thread_frame")
		

func _ready():
	var c = Callable(self,"thread_process")
	thread.start(c)
```

### Minimal reproduction project

N/A
Repository: youtube-dl
Issue: random_user_agent's Chrome versions are out of date
Labels: request

Just a quick note.  The `random_user_agent()` function in `utils.py` is using a selection of Chrome versions from major versions 74 to 76.  This set of versions hasn't changed since it was first committed in f7a147e3b63a3165c425c56ee19e66f86900128c in 2019.

I have encountered at least one site where the site _now_, as of a few days ago, serves incomplete content, lacking information in JSON parsed by the extractor, to those Chrome versions.  I compared the few hundred lines of JSON that the extractor was seeing, with the several thousand lines of JSON seen in view source in an up-to-date Vivaldi browser.

I updated the random list to Chrome major versions 114 to 116 and that fixed the problem.

[Chrome turned 100 back in 2022](https://developer.chrome.com/blog/force-major-version-to-100/), and it looks like some site operators have recently decided (or maybe accidentally changed things) to only minimally support things claiming to be older.  [Chrome Stable for Desktop is on 116](https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop_29.html) as I write this.  The Vivaldi browser was claiming to be 114.

I'd do you a pull request but I'm not in a position to.  It was basically just a `s/'7/'11/` over the list of `_CHROME_VERSIONS`, though.  You'll probably want to use a list of real 114-116 versions, anyway, not that quick bodge of mine.  &#9786;
Repository: flutter
Issue: Refactor flutter dashboard datastore
Labels: team-infra,P2,triaged-infra

- [ ] Run data analysis process to determine write/read requirements
- [ ] find what is writing to TimeSeries entity and delete the code and then delete the entity
- [ ] Remove GithubTreeStatusOverride entity
- [ ] Copy commit, branch and repo to Task entity
- [ ] Break out the CheckList entity relationship with task and rename it to Commit
- [ ] Collect branch data from Commit and delete Branch entity
- [ ] Add a TTL to GithubBuildStatusUpdate
- [ ] Support multiple Task entries for the same repo, branch, commit, task name
- [ ] Remove dead code
- [ ] Move CocoonConfig out of the data store
Repository: pytorch
Issue: Is there a standard procedure to check the consistency of environment across all nodes in PyTorch DDP training?
Labels: oncall: distributed

### 🚀 The feature, motivation and pitch

In a distributed environment, maintaining consistency across all nodes (e.g., driver versions, NCCL versions) can help reduce some training issues caused by the environment, such as performance or compatibility problems, and make troubleshooting easier. I am wondering if PyTorch provides any standard hooks or other methods to support this kind of check?

In my current setup, I have multiple nodes with different hardware and software configurations, and I want to ensure that the environment is consistent across all nodes before starting the DDP training. Is there any built-in functionality in PyTorch to perform these checks, or do I need to implement a custom solution to compare the environments?

Any suggestions or best practices on how to handle this situation would be greatly appreciated. Thank you in advance for your help!

### Alternatives

_No response_

### Additional context

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu
Repository: axios
Issue: type optimization
Labels: priority::low

### Is your feature request related to a problem? Please describe.

It is hoped that when creating an axios instance, generics can be passed in to define the types of response.data and config

### Describe the solution you'd like

```ts
import axios from 'axios';
import type { AxiosRequestConfig, AxiosResponse } from 'axios';

interface myConfig extends AxiosRequestConfig {
  customeConfigField?: string;
}

interface myResponse {
  code: string;
  data: any;
}

const axiosInstance = axios.create<myResponse, myConfig>({});

axiosInstance.interceptors.response.use(response => {
  return response.data
})

const { code, data } = await axiosInstance.get(...., {
  customeConfigField: ''
})
```

### Describe alternatives you've considered

_No response_

### Additional context/Screenshots

_No response_
Repository: go
Issue: x/tools/gopls: cannot find refs to function type
Labels: FeatureRequest,gopls,Tools

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.7 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
</pre></details>

### What did you do?

I tried to use vscode to "find all references", "find all implementations", "go to definition" of an function type alias embedded in a struct. vscode is unable to find it. vscode uses `gopls` so I believe it is `gopls` that is at fault.



### What did you expect to see?

I expected to be taken to the method that the type alias references.


### What did you see instead?

"go to definition" took me to the method that the function alias was itself part of (where it was being called from).

Load the following program into vscode. right click on the commented function call and try to find what actually would get called.

```go
package main

import (
	"context"
	"fmt"
)

type cmdable func(ctx context.Context, arg string) string

type client struct {
	cmdable
}

func (c *client) init() {
	c.cmdable = c.Process
}

func (c *client) Process(ctx context.Context, arg string) string {
	return arg
}

func (c cmdable) DoIt(ctx context.Context, arg string) string {
	return c(ctx, arg) // really?!?
}

func main() {
	var c client
	c.init()
	fmt.Println(c.DoIt(context.Background(), "wtf"))
}
```
Repository: next.js
Issue: SCSS not updating and Fast Refresh issues after macOS update
Labels: Upstream,bug,Runtime

### 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: arm64
      Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.19.0
      npm: 8.19.3
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.1.6
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime), Operating System (Windows, MacOS, Linux)

### Link to the code that reproduces this issue or a replay of the bug

none

### To Reproduce

1. Update macOS to Ventura 13.5.1
2. Run next dev in my Next.js project.
3. Make changes to SCSS files.
4. Observe that changes are not reflected immediately and Fast Refresh performs a full reload.

### Describe the Bug

After updating my macOS, I've been experiencing issues with SCSS not updating immediately and Fast Refresh having to perform a full reload. Everything was working perfectly before the update.

### Expected Behavior

SCSS should update immediately and Fast Refresh should work without performing a full reload.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: next.js
Issue: Unable to upload images (using uploadthing api) in production website (live site in vercel)
Labels: bug,Navigation

### 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: #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023
    Binaries:
      Node: 20.3.1
      npm: 9.6.7
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.19
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A
```


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

Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/captain-Akshay/nextNation

### To Reproduce

next.config file
```
const nextConfig = {
  images: {
    domains: [
      "uploadthing.com",
      "lh3.googleusercontent.com",
      "avatars.githubusercontent.com",
      "images.unsplash.com",
      "icon-library.com",
    ],
  },
  experimental: {
    appDir: true,
  },
  env: {
    RAPID_API_KEY:""
  },
};
module.exports = nextConfig;
```
uploadthing core.ts
```
import { getToken } from 'next-auth/jwt'
import { createUploadthing, type FileRouter } from 'uploadthing/next'

const f = createUploadthing()

export const ourFileRouter = {
  imageUploader: f({ image: { maxFileSize: '16MB' } })
    .middleware(async (req) => {
      const user = await getToken({ req })

      if (!user) throw new Error('Unauthorized')

      return { userId: user.id }
    })
    .onUploadComplete(async ({ metadata, file }) => {}),
} satisfies FileRouter

export type OurFileRouter = typeof ourFileRouter

```
route.ts
```
import { createNextRouteHandler } from 'uploadthing/next'

import { ourFileRouter } from './core'

// Export routes for Next App Router
export const { GET, POST } = createNextRouteHandler({
  router: ourFileRouter,
})
```
on the localhost npm its running completely fine images are getting upload and shown properly but in production service.
error 
```
Error: Failed to get presigned URLs
    i NextJS
[page-ad9751b90f626cef.js:1:6023](https://next-nation.vercel.app/_next/static/chunks/app/p/create/page-ad9751b90f626cef.js)
```

### Describe the Bug

here the error is sometimes 404 or 400 presigned URL error.
when i upload image in the production live site.

### Expected Behavior

it was supposed to same in the local mode as in the production mode .
uploading images should be upload the image.


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

firefox

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

Vercel
Repository: vscode
Issue: Listening music in VS Code: "Chromium" in the volume app
Labels: bug,upstream,linux,electron,upstream-issue-linked

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

**yne** did an awesome contribution to VS Code extensions: his "[DZR: the command line deezer.com player](https://github.com/yne/dzr/)" is now an VS Code extension too.

Sadly, the audio playing VS Code shows up as "Chromium" in the volume mixer, exactly like as in the SO question: [How to edit Electron instance's process name etc](https://stackoverflow.com/questions/73093092/how-to-edit-electron-instances-process-name-etc).

Pictures from that SO question:
> ![image](https://github.com/microsoft/vscode/assets/568751/970802ed-620f-4405-94b0-11f5eb2fd5c0)
> ![image](https://github.com/microsoft/vscode/assets/568751/28636600-b1a1-4445-98ec-6b77fbbb22c6)

My VS Code About info:
```
Version: 1.81.1
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:18:39.991Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 5.15.0-1037-intel-iotg
```


It would be nice to see VS Code related title in the volume application instead "Chromium".
Repository: transformers
Issue: POET
Labels: New model

## Train BERT and other large models on smartphones

### Model description

`POET` enables the training of state-of-the-art memory-hungry ML models on smartphones and other edge devices. POET (Private Optimal Energy Training) exploits the twin techniques of integrated tensor rematerialization, and paging-in/out of secondary storage (as detailed in our paper at ICML 2022) to optimize models for training with limited memory. POET's Mixed Integer Linear Formulation (MILP) ensures the solutions are provably optimal! approach enables training significantly larger models on embedded devices while reducing energy consumption while not modifying mathematical correctness of backpropagation. We demonstrate that it is possible to fine-tune both `ResNet-18` and `BERT` within the memory constraints of a Cortex-M class embedded device while outperforming current edge training methods in energy efficiency.



### Open source status

- [X] The model implementation is available
- [ ] The model weights are available

### Provide useful links for the implementation

[Implementation](https://github.com/ShishirPatil/poet)
[Paper](https://arxiv.org/abs/2207.07697)
[Author's Website](https://shishirpatil.github.io/poet/)
Repository: next.js
Issue: Jest cannot test form actions
Labels: bug,Testing

### 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: #1 SMP PREEMPT_DYNAMIC Thu Jul 27 20:01:18 UTC 2023
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10
      eslint-config-next: 13.4.10
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: standalone
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Jest (next/jest)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/Dinika/nextjs-serveractions-jest

### To Reproduce

```bash
git clone https://github.com/Dinika/nextjs-serveractions-jest.git
cd nextjs-serveractions-jest
yarn
yarn test
````

### Describe the Bug

While I am able to test component that call server actions (by using the `action` prop on `form` element), I am not able to test that a given server action was called or that the form was submitted. I get the following error:

```
  console.error
    Warning: Invalid value for prop `action` on <form> tag. Either remove it from the element, or pass a string or number value to keep it in the DOM. For details, see https://reactjs.org/link/attribute-behavior 
        at form
        at Home

 FAIL  app/Home.test.tsx
  Home
    ✓ WORKS - Tests that do not submit form work (62 ms)
    ✕ DOES NOT WORK - Tests that check server action is called dont work (15 ms)

  ● Home › DOES NOT WORK - Tests that check server action is called dont work

    expect(jest.fn()).toHaveBeenCalled()

    Expected number of calls: >= 1
    Received number of calls:    0

      26 |         const formEl = container.querySelector('form');
      27 |         formEl.dispatchEvent(new Event('submit'));
    > 28 |         expect(spy).toHaveBeenCalled();
         |                     ^
      29 |     });
      30 |
      31 | });

      at Object.toHaveBeenCalled (app/Home.test.tsx:28:21)
```

### Expected Behavior

It should be possible to test that the form was submitted.

### Which browser are you using? (if relevant)

firefox

### How are you deploying your application? (if relevant)

_No response_
Repository: vscode
Issue: JSON sorting: Have a way to differentiate between section comments and property comments
Labels: json,polish,json-sorting

Originally posted by @brettcannon 

_One thing that surprised me is when there's no way to have a section comment, e.g.:_

```
{
    // Big block comment

    "b": false, // more B stuff
    "C": 42, // C stuff
    // stuff
    "A": true
    // B stuff
}
```

_will sort // Big block comment with "b" instead of leaving it in-place._
Repository: next.js
Issue: renderToStaticMarkup html output is incorrect only in Next.js (React 18.2.0, Next 13.4.19)
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: arm64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.12
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: export
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/vibrant-einstein-l82mgr

### To Reproduce

I am using the Route Handler with App Router as per documented here: https://nextjs.org/docs/app/building-your-application/routing/route-handlers

Im trying to use `ReactDOMServer.renderToStaticMarkup` to return a complete html template for an email builder application, for previewing emails built with React Server Components. (I tried using page, but Next.js seems to inject its own tags and modified the output, therefore I'm looking into using Route Handler to just render the React component to a string on server side and return as is). 

### Describe the Bug

The string produced by `ReactDOMServer.renderToStaticMarkup` seem to move `<meta>`and` <title>` elements out of the `<head>` element. `<style>` elements, on the other hand, still remain inside `<head>` as expected. 

I've verified that this function behave in the expected manner when used in a vanilla react typescript project. Somehow only in a Next.js project am I seeing this behavior.

The codesandbox.io link attached is a reproduction of this behavior, in a barebone Next.js app using the latest version of Next.js and React

### Expected Behavior

`ReactDOMServer.renderToStaticMarkup` should function as expected, and return the string unmodified. 

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: pytorch
Issue: [docs] F.interpolate(uint8_input, mode = 'bicubic', ...) overshoot behavior: adjust the note in docs to explain that for uint8 saturating store is done and no manual clamp is needed or mention that bicubic is not supported for uint8 inputs
Labels: module: docs,module: nn,triaged,actionable

### 🐛 Describe the bug

The https://pytorch.org/docs/stable/generated/torch.nn.functional.interpolate.html say that for avoiding overshoot the user must manually do `.clamp(0, 255)`. 
<img width="459" alt="image" src="https://github.com/pytorch/pytorch/assets/1041752/5add9591-f605-4fb4-8275-050518727012">

For me, this makes sense if the input is float32 (or `int32` when it gets supported https://github.com/pytorch/pytorch/issues/5580). But if the input/output is uint8 (which is now finally supported), the overshoot would simply overflow and clamp would not help.

I would propose that for uint8 inputs / outputs F.interpolate should do saturating/clamping cast/store (so that negative values are clamped to 0 and >255 values are clamped to 255)

### Versions

N/A

cc @svekars @carljparker @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: rust
Issue: multiple spurious errors when `T: 'static` is required in async fn
Labels: A-diagnostics,A-borrow-checker,T-compiler,C-bug,D-verbose

Given this code:
```rust
async fn test<T>(_: &u8) {
    let _: &'static T;
    //~^ ERROR the parameter type `T` may not live long enough
    //~| ERROR the parameter type `T` may not live long enough
}
```

Two errors are emitted: one requires `T: 'static`, as expected, and the other requires `T: 'a` where `'a` is the anonymous lifetime.

This affects lifetime constraints that originate in async fn, async blocks, and closures. 

An error is emitted for each lifetime that appears in the function because `'static` is an upper bound for all lifetimes.

```rust
error[E0310]: the parameter type `T` may not live long enough
 --> src/lib.rs:2:12
  |
2 |     let _: &'static T;
  |            ^^^^^^^^^^ ...so that the type `T` will meet its required lifetime bounds
  |
help: consider adding an explicit lifetime bound...
  |
1 | async fn test<T: 'static>(_: &u8) {
  |                +++++++++

error[E0311]: the parameter type `T` may not live long enough
 --> src/lib.rs:2:12
  |
2 |     let _: &'static T;
  |            ^^^^^^^^^^
  |
note: the parameter type `T` must be valid for the anonymous lifetime defined here...
 --> src/lib.rs:1:21
  |
1 | async fn test<T>(_: &u8) {
  |                     ^^^
note: ...so that the type `T` will meet its required lifetime bounds
 --> src/lib.rs:2:12
  |
2 |     let _: &'static T;
  |            ^^^^^^^^^^
help: consider adding an explicit lifetime bound...
  |
1 | async fn test<'a, T: 'a>(_: &'a u8) {
  |               +++  ++++      ++
```