sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: RPC checksum fails when custom MultiplayerAPI is set on SceneTree via set_multiplayer 
Labels: discussion,documentation,topic:multiplayer

### Godot version

v4.1.1.stable

### System information

Godot v4.1.1.stable - Windows 10.0.19045 - Vulkan (Compatibility) - NVIDIA GeForce GTX 750 Ti (NVIDIA; 31.0.15.3623) - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

When setting a custom MultiplayerAPI via the scenetree, the checksum fails unless the other peers have a custom API set as well.
The behavior I expected is that since they are both SceneMultiplayer, have the same RPC methods, same nodepaths, that it would work even though the MultiplayerAPI is set to a different one.

### Steps to reproduce

I've set up a simple test project with a few variables.
![image](https://github.com/godotengine/godot/assets/40964335/40f2b99a-4200-48e9-925e-62e8ae9ed642)
![image](https://github.com/godotengine/godot/assets/40964335/7f4c6894-7b0e-4b24-a233-c9fc43b33d91)

Setting the Custom Multiplayer export variable will create a custom multiplayerApi and set it, as the title of this post says:
![image](https://github.com/godotengine/godot/assets/40964335/4584eba4-0006-4ab1-9706-a2ec04e0ae92)

Leaving it unchecked won't create the MultiplayerAPI.

Checking server just makes it the server, not a client.
![image](https://github.com/godotengine/godot/assets/40964335/e86e6c62-a005-44d2-9d62-0d44d4005ff1)


I exported this project 3 times, with these options selected each time:

Export 1: Server
![image](https://github.com/godotengine/godot/assets/40964335/bb31d74c-721d-4a57-b542-88e8f94ce48d)
Export 2: Client
![image](https://github.com/godotengine/godot/assets/40964335/8c1ff817-955d-40ae-8335-8d37780fa2d5)
Export 3: Client, Custom MultiplayerAPI
![image](https://github.com/godotengine/godot/assets/40964335/eea02061-6f4b-4a95-9d27-e83865d57132)

I feel its easier to explain as a gif:
![AtiqQ8Zybz](https://github.com/godotengine/godot/assets/40964335/c67d6fd6-3e59-4ae6-963b-22f5ef843b3c)

Despite the nodepaths being the exact same, it spits out errors about invalid paths in the console. 


### Minimal reproduction project

[RPCChecksum.zip](https://github.com/godotengine/godot/files/12332015/RPCChecksum.zip)
Repository: next.js
Issue: build error message formatting missing newline
Labels: bug,Webpack

### 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.5.1
      npm: 9.8.0
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.14-canary.4
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/SimonSiefke/nextjs-error-bug

### To Reproduce

1. Create a component that contains an error 

```js
let someVariable: any = 2;

export const SomeComponent = () => {
  someVariable.doesNotExist();
  return <div></div>;
};
```

2. Run `next build`

### Describe the Bug

The formatting of the error message is a bit odd, there is no new line between the "Generating static pages" message and the error message

```
[=   ] - info Generating static pages (1/4)TypeError: someVariable.doesNotExist is not a function
```

### Expected Behavior

There is a new line between the "Generating static pages" message and the error

```
[=   ] - info Generating static pages (1/4)

TypeError: someVariable.doesNotExist is not a function
    at SomeComponent (/home/simon/.cache/repos/nextjs-error-bug/.next/server/app/page.js:335:18)
    at S (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6167:13)
    at eb (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6282:21)
    at Object.toJSON (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6086:20)
    at stringify (<anonymous>)
    at pb (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6493:9)
    at mb (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6392:29)
    at Timeout._onTimeout (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6217:16)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7)
```

### Related issues

https://github.com/vercel/next.js/issues/53978

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: next.js
Issue: build error message doesn't show where the error came from
Labels: bug,Webpack

### 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.5.1
      npm: 9.8.0
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.14-canary.4
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```



### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/SimonSiefke/nextjs-error-bug

### To Reproduce

1. Create a component that contains an error

```js
let someVariable: any = 2;

export const SomeComponent = () => {
  someVariable.doesNotExist();
  return <div></div>;
};
```

2. Run `npx next build`

### Describe the Bug

The stack trace of the error doesn't show where the error came from 

```
TypeError: someVariable.doesNotExist is not a function
    at SomeComponent (/home/simon/.cache/repos/nextjs-error-bug/.next/server/app/page.js:335:18)
    at S (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6167:13)
    at eb (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6282:21)
    at Object.toJSON (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6086:20)
    at stringify (<anonymous>)
    at pb (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6493:9)
    at mb (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6392:29)
    at Timeout._onTimeout (/home/simon/.cache/repos/nextjs-error-bug/.next/server/chunks/968.js:6217:16)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7)
```

### Expected Behavior

The stack trace of the error shows exactly where the error came from

```
TypeError: someVariable.doesNotExist is not a function
    at SomeComponent (./app/some-component.tsx:10:18)
    at stringify (<anonymous>)
```


#### Even better error display with code frame (optional)

```
TypeError: someVariable.doesNotExist is not a function

  2 | 
  3 | export const SomeComponent = () => {
> 4 |   someVariable.doesNotExist();
    |               ^
  5 |   return <div></div>;
  6 | };
  7 | 

    at SomeComponent (./app/some-component.tsx:10:18)
```

### Related issues
https://github.com/vercel/next.js/issues/53978, https://github.com/vercel/next.js/issues/53979

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: tensorflow
Issue: Protobuf 4.24.0 break tensorflow and causes segfault with TF 2.12
Labels: stat:awaiting tensorflower,type:build/install,subtype: ubuntu/linux,TF 2.12

### Issue type

Build/Install

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

TF 2.12

### Custom code

No

### OS platform and distribution

Linux,Ubuntu

### Mobile device

_No response_

### Python version

3.8

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

With source build as well as pip install TF execution models fails with segfaults and the root cause seems to be because of protobuf version 4.24.0. It works fine till protobuf 4.23.4. adding a constraint in setup.py can be an immediate fix.

### Standalone code to reproduce the issue

```shell
Any CNN model execution causes the workflow to fail.
```


### Relevant log output

```shell
2023-08-14 08:01:56.274633: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:353] MLIR V1 optimization pass is not enabled
WARNING:tensorflow:From /home/anaconda3/envs/test/lib/python3.8/site-packages/tensorflow/python/tools/strip_unused_lib.py:84: extract_sub_graph (from tensorflow.python.framework.graph_util_impl) is deprecated and will be removed in a future version.
Instructions for updating:
This API was designed for TensorFlow v1. See https://www.tensorflow.org/guide/migrate for instructions on how to migrate your code to TensorFlow v2.
scripts/benchmark_CNN.sh: line 243: 1488387 Segmentation fault
```
Repository: vscode
Issue: Support search in notebook diff editor
Labels: feature-request,notebook-diff

<!-- ⚠️⚠️ 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. -->

Would be great to support search in notebook diff editor:



![Image](https://github.com/microsoft/vscode/assets/16353531/02d8b778-d5c9-453f-960f-d22f80c6e00d)
Repository: TypeScript
Issue: Explicitly annotated unique symbols are widened in return positions
Labels: Possible Improvement

### 🔎 Search Terms

widening return unique symbol

### 🕗 Version & Regression Information

- This is the behavior in every version I tried



### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.3.0-dev.20230814&ssl=6&ssc=2&pln=1&pc=1#code/KYDwDg9gTgLgBAYwgOwM7xsdcC8cDKAngLYBGEANgBQCUAUHaJLHAGYCuyCMAlim8lpwA3nTjjEKbAEMKPaagBccGITDAIrFVnh5M6ANxiJUYDHZRkcWfNR0AvkA

### 💻 Code

```ts
export const test = Symbol()

export function fn() {
    const alias: typeof test = test;
    return alias
}
```


### 🙁 Actual behavior

this declaration file is emitted:
```ts
export declare const test: unique symbol;
export declare function fn(): symbol;
```

### 🙂 Expected behavior

this declaration file to be emitted:
```ts
export declare const test: unique symbol;
export declare function fn(): typeof test;
```

### Additional information

`getWidenedLiteralLikeTypeForContextualReturnTypeIfNeeded` calls `getWidenedLiteralLikeTypeForContextualType` and that calls `getWidenedUniqueESSymbolType` when there is no contextual type provided.

some issues that are (partially~) related:
https://github.com/microsoft/TypeScript/issues/32242
https://github.com/microsoft/TypeScript/issues/35896#issuecomment-569466046
https://github.com/microsoft/TypeScript/issues/36876
Repository: opencv
Issue: The fisheye module does not contain a solvePnP() function
Labels: feature,category: documentation,category: calib3d

### System Information

---

### Detailed description

A method for `rvec` and `tvec` estimation exists inside the `fisheye` calibration module. However, there is no public method to access this functionality, and there is no description of how this approach works in mathematical terms.

### Steps to reproduce

---

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: axios
Issue: axios.postForm is not useable with .NET API
Labels: priority::low

### Describe the bug

In the documentation is stated:
![image](https://github.com/axios/axios/assets/66643584/123e6056-b572-46c5-9d3b-c2496ad3dcdd)
https://axios-http.com/docs/multipart

Is that somehow changeable? (without the square brackets '[]')
Because maybe I rely on to many syntax features, but I cannot use the axios.postForm() method when my C# API-endpoint has to look like this (what is pretty much illegal in C#):
![image](https://github.com/axios/axios/assets/66643584/3f86516b-28b5-4714-a05b-1e2d6985b1c6)

I don't know if it is more practicable, with other tools but in this case it don't seem to work, so i have to switch back to the old way:
```typescript
const conf = {
  headers: {
    'Content-Type': 'multipart/form-data',
  },
};
const files = (<HTMLInputElement>e.target).files;
const formData = new FormData();

if (!files?.length) return;
for (let file of files) formData.append('slide', file);

axios.post('.../slide', formData, conf);
```

I appreciate your work and I'm using axios every day.
Thanks for creating axios!

### To Reproduce

_No response_

### Code snippet

_No response_

### Expected behavior

_No response_

### Axios Version

1.4.0

### Adapter Version

multipart/form-data

### Browser

_No response_

### Browser Version

_No response_

### Node.js Version

_No response_

### OS

_No response_

### Additional Library Versions

_No response_

### Additional context/Screenshots

_No response_
Repository: next.js
Issue: in Page Router, If throw errors in suspended component at server on purpose, Error Popup shows
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.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: 8.6.6
    Relevant packages:
      next: 13.3.4
      eslint-config-next: 13.4.1
      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 or a replay of the bug

-

### To Reproduce

1. create a suspended component
2. `throw new Error('this component only works on client');`


### Describe the Bug

https://react.dev/reference/react/Suspense#providing-a-fallback-for-server-errors-and-client-only-content

I wanted to have the fallbacks rendered on the server side as described in the article above, so I threw an Error, but I get an error popup and this is throwing me off. Is there any way to have the fallback be drawn on the server if I don't want it to work server-side?

### Expected Behavior

There should be any solution to render fallback in Server.

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

_No response_

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

_No response_
Repository: next.js
Issue: i18n: Wrong locale on getServerSideProps when using next.config.js rewrite
Labels: bug,Navigation,Pages Router

### 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 Sun Aug  6 20:05:33 UTC 2023
    Binaries:
      Node: 18.14.2
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.14-canary.5
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
    Next.js Config:
      output: N/A
```


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

Data fetching (gS(S)P, getInitialProps), Internationalization (i18n), Routing (next/router, next/navigation, next/link)

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

https://codesandbox.io/p/sandbox/routing-i18n-bug-gfc94t?file=%2Fnext.config.js%3A1%2C1

### To Reproduce

If you click on _"Link to Page1 [PT](https://gfc94t-3000.csb.app/pt/page1/)"_ you will see that both `props` and `router` will output the correct locale, `pt`. 

However, if you click on _"Link to Pagina1 (Redirect to Page1) [PT](https://gfc94t-3000.csb.app/pt/pagina1/)"_, `props` will be the `defaultLocale` (which is `en`), whereas `router` be the expected locale, `pt`.

The only difference between both links is that the second one works via a `next.config.js` `rewrite` property.

### Describe the Bug

`getServerSideProps` is not getting the correct `locale` if the route was using a `next.config.js` `rewrite`.

This was **working** as expected up until and including version `13.2.5-canary.16`. On version `13.2.5-canary.17` it has **stopped working** and has not being fixed yet (example on [CodeSandbox](https://codesandbox.io/p/sandbox/routing-i18n-bug-gfc94t?file=%2Fnext.config.js%3A1%2C1) is using the latest version `13.4.14-canary.5`).

### Expected Behavior

`getServerSideProps` should have the correct `locale` value regardless of the routing strategy.

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

_No response_

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

_No response_
Repository: next.js
Issue: Failed to fetch Fonts from Google
Labels: bug,Font (next/font)

### 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: 19.2.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.13
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A

Actually, I'm on Windows 11 and using pnpm v.8.6.10
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

This cannot be reproduced in a CodeSandbox example, because it's a NETWORK PROBLEM

### To Reproduce

Usage with App Router and next/font.

Run pnpm run dev or pnpm run build. Compiling the page fails fetching the fonts (it doesn't matter which ones) from Google.

### Describe the Bug

I manage a project both in my house and in my office. At my house, nothing weird happens, but at the office, fetching the fonts fails with the following error:

```shell
request to https://fonts.googleapis.com/css2?family=Roboto+Slab:wght@400&display=swap failed, reason: getaddrinfo ENOTFOUND 8080
```

I'm able to access that link without any problems via Chrome, but not via cmd.

This cannot be reproduced in a CodeSandbox example, because it's a network problem. Several more had happened like this in the past, e.g. with Github Copilot or Prisma, but opening a ticket got this resolved.

I'm not behind any configuration that could affect this behavior, other than the routing my infra team does with our requests.

### Expected Behavior

Error not showing and fonts being fetched.

### Which browser are you using? (if relevant)

Chrome 115.0.5790.171

### How are you deploying your application? (if relevant)

_No response_
Repository: godot
Issue: The offset of adding frames from the sprite table cannot be negative
Labels: feature proposal,discussion,topic:editor,topic:2d

### Godot version

v4.1.1.stable.arch_linux

### System information

Godot v4.1.1.stable unknown - Manjaro Linux #1 SMP PREEMPT_DYNAMIC Wed Aug  9 09:02:26 UTC 2023 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Laptop GPU () - AMD Ryzen 9 5900HX with Radeon Graphics (16 Threads)

### Issue description

When I use AnimatedSprite2D. I found animation have some offset to right. I try to fix it, nut I found the offset of adding frames from the sprite table cannot be negative, if it can be. This problem will be solved very well, the bad thing is that he can't

### Steps to reproduce

Create a Scene
Add a Node2d
Add an AnimatedSpirte2D
Add an Animation
Click :
![image](https://github.com/godotengine/godot/assets/94843786/fe81f4c7-8b4d-42f2-882d-db2eda9cd3b6)
Select a picture
![image](https://github.com/godotengine/godot/assets/94843786/10aafa14-cf33-4b7a-a3b5-ffbf4e1f3deb)
not to be negative

### Minimal reproduction project

N/A
Repository: pytorch
Issue: [docs] Document dtype conversions dtype.to_complex() dtype.to_real()
Labels: module: docs,triaged

Edit by @colesbury 

We have helpful conversions between real and complex dtypes:

```
torch.float32.to_complex() -> torch.complex64
torch.complex64.to_real() -> torch.float32
```

But these conversions are not documented. We should document them!

### Original request below:

### 🚀 The feature, motivation and pitch

Builtin helpers would be nice for dtype-polymorphic code of the type:
```python
def f(x : torch.Tensor):
  assert x.is_floating_point()
  return torch.zeros_like(x, dtype = x.dtype.complex()) # or some other bikeshedding
```

Same for conversion of complex dtype to real dtype of the corresponding width


cc @svekars @carljparker
Repository: node
Issue: `require.cache` is `undefined` in SEA
Labels: single-executable

### Version

v20.4.0 v20.5.1 v20.3.0

### Platform

Linux 5.15.90.1-microsoft-standard-WSL2

### Subsystem

_No response_

### What steps will reproduce the bug?

```bash
echo 'console.log(typeof require.cache)' > main.js
node main.js
echo '{ "main": "hello.js", "output": "sea-prep.blob" }' > sea-config.json
node --experimental-sea-config sea-config.json
cp $(command -v node) hello
npx postject hello NODE_SEA_BLOB sea-prep.blob --sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2
./hello
```

### How often does it reproduce? Is there a required condition?

Always reproducible

### What is the expected behavior? Why is that the expected behavior?

`require.cache` should be an object as of https://nodejs.org/api/modules.html#requirecache


### What do you see instead?

`require.cache` is undefined. Trying to index it or enumerate it with `Object.entries` will result in TypeError

### Additional information

This is relevant for Fastify which uses cache to provide a printable name for a plugin (based on its file path). See https://github.com/fastify/fastify/blob/c235d2dc136a67c51095f188742c743d8cb32839/lib/pluginUtils.js#L27
Repository: material-ui
Issue: [docs-infra] Custom font styles breaks the custom tailwind config
Labels: scope: docs-infra

I noticed that when the custom font family is added in sandbox it breaks the custom tailwind config, however, it works perfectly fine in the docs (broken sandbox - https://codesandbox.io/s/ymys9l?file=/public/index.html:1549-1575 fonts are not working, but also none of the custom tailwind config). It's likely related to the whole sandbox + create react app + CDN tailwind CSS setup. I am removing it for now, but it may be interesting to consider moving the sandbox and stackblitz demos to use vite instead of create-react-app. cc @mui/docs-infra

_Originally posted by @mnajdova in https://github.com/mui/material-ui/issues/38464#issuecomment-1677115622_