sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: MDX plugins running twice
Labels: bug,Markdown (MDX)

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
➜  workspace git:(master) ✗ yarn next info
yarn run v1.22.19
$ /project/home/pomber/workspace/node_modules/.bin/next info

    Operating System:
      Platform: linux
      Arch: x64
      Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant packages:
      next: 13.0.8-canary.0
      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)

MDX (@next/mdx)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/ancient-feather-mt8pnx?file=%2Fnext.config.js%3A10%2C5

### To Reproduce

I have a remark plugin that logs the name of the mdx file:

```js
// next.config.js
const withMDX = require("@next/mdx")({
  extension: /\.mdx?$/,
  options: { remarkPlugins: [myPlugin] },
});
module.exports = withMDX({ pageExtensions: ["js", "jsx", "mdx"] });

function myPlugin() {
  return function transformer(tree, file) {
    console.log(file.path);
  };
}
```


### Describe the Bug

When I run `next build`, this is the output:

```
➜  workspace git:(master) ✗ yarn build
yarn run v1.22.19
$ next build
info  - Linting and checking validity of types  
/project/home/pomber/workspace/pages/index.mdx
/project/home/pomber/workspace/pages/test.mdx
/project/home/pomber/workspace/pages/index.mdx
/project/home/pomber/workspace/pages/test.mdx
info  - Creating an optimized production build  
info  - Compiled successfully
info  - Collecting page data  
info  - Generating static pages (4/4)
info  - Finalizing page optimization 
```

The plugin runs twice for each page.

Is that expected? is it a bug?

### Expected Behavior

I expect it to run only once for each page.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: TypeScript
Issue: `completionInfo` command ignoring whitespace generating suggestions
Labels: Help Wanted,Possible Improvement

# Bug Report
Found while fixing VSCode suggestions:
https://github.com/microsoft/TypeScript/issues/54627


### 🔎 Search Terms
completion, completionInfo, dot notation
<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

 ### ⏯ Playground Link
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.2.0-dev.20230610#code/FASwdgLgpgTgZgQwMZQAQBUoGcKoN7CpGoDkJAXKQO4AWI0WADslCQDSHElG33bMpUCXBBpocCGBG6UARGAD2uKgpgBrcAHNZHYqVKUSvBgNa7isgOoAJAJLoAogGUACgEEAwg9RIEjLKjgqKJoUGAAJqiyhlg0CgCuADaRKursnEQkYomoiQoU1KrJ6XokMFCaSZIFJApqCACeJRaKxvws0aQNjSTAAL7AwEgKYDjB2BAATJSYYwC8+Bmo-YPDoyITqAt4fUIBsxDADBAAdEcTANpkALqEQA)



### 💻 Code

<!-- Please post the relevant code sample here as well. This code and the Playground code should be the same, do not use separate examples -->

```ts
interface Test {
    '': 'whitespace',
    '  whitespace at the start' : "not working",
    ' ': 'whitespace',
    "WHITESPACE caps in the end ": 'should work'
}
const test = {} as Test
// The dot notation does not suggest empty string properties:
test. // <--
```
<img width="483" alt="Screenshot 2023-06-11 at 00 54 12" src="https://github.com/microsoft/vscode/assets/55909427/dfd5d21d-90cd-4122-b84e-5513bd88d801">


However, suggestions work inside an object:
<img width="480" alt="image" src="https://github.com/microsoft/vscode/assets/55909427/19c76e96-5b30-4e8c-a719-6f9c66eb7274">
### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->

Accessed with dot notation:
<img width="310" alt="image" src="https://github.com/microsoft/vscode/assets/55909427/b50044c2-87c0-46ca-9a7e-b10ff7237e3f">

Accessed inside an object:
<img width="326" alt="Screenshot 2023-06-11 at 01 02 47" src="https://github.com/microsoft/vscode/assets/55909427/79abe71e-36ac-4e72-9bf5-c106b9a5cb80">

`completionInfo` - ts command id 
https://github.com/microsoft/TypeScript/blob/main/src/services/completions.ts

### 🙂 Expected behavior
Responses should be the same

<!-- What you expected to happen instead, and why -->
Repository: neovim
Issue: enabling treesitter from an autocommand may skip BufReadPost
Labels: bug,treesitter

### Problem

When launching treesitter from an autocommand and then, later in the config file, enabling syntax and filetype plugin/indent, the BufReadPost and BufRead events will not be triggered for files that:
1. Also launch treesitter.
2. Are loaded in as CLI options.

For whatever reason, this only happens if the file does `syntax enable` before it does `filetype plugin indent on`

If `syntax enable` or the treesitter autocommand are removed, the BufReadPost event triggers as expected.

Example configuration that has this issue:
```lua
local augroup = vim.api.nvim_create_augroup
local autocmd = vim.api.nvim_create_autocmd

augroup('VimrcAutoCommands', { clear = true })

autocmd('FileType', {
    group = 'VimrcAutoCommands',
    pattern = 'c,vim,vimdoc,lua,query',
    callback = function(args) vim.treesitter.start(args.buf, args.match) end
})

autocmd('BufReadPost', { group = 'VimrcAutoCommands', pattern = '*',
    callback = function(args)  vim.opt.number = true end
})

vim.cmd([[
    syntax enable
    filetype plugin indent on
]])
```
When using the above configuration with a supported file type, line numbers are not displayed.

### Steps to reproduce

nvim ~/.config/nvim/init.lua

### Expected behavior

Using the provided configuration file, line numbers should be enabled when viewing init.lua.

### Neovim version (nvim -v)

0.9.1

### Vim (not Nvim) behaves the same?

No (Vim does not have treesitter)

### Operating system/version

Ubuntu 22.04 (WSL)

### Terminal name/version

ST 0.9 + Tmux 3.2

### $TERM environment variable

screen-256color

### Installation

Appimage
Repository: PowerToys
Issue: Text Shortcut
Labels: Needs-Triage

### Description of the new feature / enhancement

Ok, if I can explain this in intelligent terms.

I want to program a series of a couple of Hotkeys to generate a preset text. I use certain text content regularly. I want to press a couple of keys to generate that text in any program I am in. Some might be entire emails, some might just be a header or footer to another content producer.

I operate an online newspaper. www;thelainsider.com. I use footer text to give credit to sources. I would like to have a simple way to generate that text.

I send pre-written emails to businesses or chambers of commerce. I would like to press a couple of keys to have that text generated into my email program.

I hope I have given you enough examples. If you already do this in PoerToys, maybe you can direct me on how to set it up. If it is not something you are capable of doing now, maybe it would be a good thing to consider.

Thank you for your time.

### Scenario when this would be used?

I explained in original message

### Supporting information

_No response_
Repository: godot
Issue: on_delta_receive: Ignoring delta for non-authority or invalid synchronizer
Labels: needs testing,topic:network

### Godot version

4.1.beta1

### System information

Linux Mint 21.1; Kernel: 5.15.0-73; CPU: AMD Ryzen 9 3900X; GPU: AMD 5700XT, Vulkan

### Issue description

When attempting to create a 3 player chat program. I am getting an error and I can not trace how or why it is happening. I believe it is something that is mis-configured but given the documentation and examples I do not directly see anything wrong with the code. I think it might be helpful if the error could perhaps provide additional debugging such as node that is causing the problem:  https://github.com/godotengine/godot/blob/37d1dfef9d81aade27ab0c56fc6b6f12f6a08045/modules/multiplayer/scene_replication_interface.cpp#LL771C9-L771C13

```
E 0:00:28:0433   on_delta_receive: Ignoring delta for non-authority or invalid synchronizer.
  <C++ Error>    Condition "true" is true. Continuing.
  <C++ Source>   modules/multiplayer/scene_replication_interface.cpp:774 @ on_delta_receive()
```

### Steps to reproduce

I created a 3 player game with two synchronizers one for the host and one for the client. I then use the MultiplayerSpawner to instance the scene and set_multiplayer_authority() on both the client and the host side. But any time a message is sent to the server by either the second client of the third client the opposite (2nd or 3rd) client will generate this error. I also believe that as a result of the error the message does not get sent to the clients but only makes it to the host. But I could be wrong in trying to understand how this all works.

The key for reproduction is to start 3 instances, 1 as a host the the other 2 can just join and the error will start happening.

### Minimal reproduction project

[ChitChatv0.1.zip](https://github.com/godotengine/godot/files/11713399/ChitChatv0.1.zip)
Repository: TypeScript
Issue: Unexpected ASI after `declare` (regression since version 4.4)
Labels: Bug,Rescheduled

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
declare asi semicolon

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This changed between [version 4.3.5](https://www.typescriptlang.org/play?ts=4.3.5#code/CYUwxgNghgTiAEEQBd6krEAueUB2AngFDrRyIrwBmA9jTvsaZtXUUA) (where it doesn't happen) and [version 4.4.4](https://www.typescriptlang.org/play?ts=4.4.4#code/CYUwxgNghgTiAEEQBd6krEAueUB2AngFDrRyIrwBmA9jTvsaZtXUUA) (where it starts happening)

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior.
  This should have the same code as the code snippet below, and use whichever settings are relevant to your report.

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link for version 4.3.5](https://www.typescriptlang.org/play?ts=4.3.5#code/CYUwxgNghgTiAEEQBd6krEAueUB2AngFDrRyIrwBmA9jTvsaZtXUUA) (fine)
[Playground link for version 4.4.4](https://www.typescriptlang.org/play?ts=4.4.4#code/CYUwxgNghgTiAEEQBd6krEAueUB2AngFDrRyIrwBmA9jTvsaZtXUUA) (problematic)

### 💻 Code

<!-- Please post the relevant code sample here as well. This code and the Playground code should be the same, do not use separate examples -->
Some random examples that TS 5.1 considers valid syntax (not exhaustive): 

```ts
declare let declare: any, foo: any
declare foo
```

```ts
declare let declare: any, foo: any
declare foo()
```

```ts
declare let declare: any, foo: any
declare {foo}
```

### 🙁 Actual behavior

TypeScript silently does automatic semicolon insertion after `declare` in all of these cases without generating any syntax errors.

### 🙂 Expected behavior

I expected these to be syntax errors. I did not expect TypeScript to silently be doing automatic semicolon insertion after `declare` here as if this is valid syntax.
Repository: node
Issue: Support for zstd
Labels: feature request,never-stale

### What is the problem this feature will solve?

[zstd][1] and the `application/zstd` media type were standardized in 2018 in [RFC8478][2] (and refined in [RFC8878][3]). In the context of the web, support is becoming more widespread:

**Browsers**
- Chrome
	- [Issue 1246971: Implement zstd content-encoding][4]
	- Expected to land in 117
- Firefox
	- [Bug 1301878: Implement support for Zstandard (zstd)][5]
	- Still under discussion

**Web servers**
- Caddy
	- [Available in v2][6]
- Nginx
	- [Available as a module][7]

**Tools**
- cUrl
	- [Available in 7.72.0][8]
- wget2
	- [Available in 1.99.2][9]

[1]: https://github.com/facebook/zstd
[2]: https://datatracker.ietf.org/doc/html/rfc8478
[3]: https://datatracker.ietf.org/doc/html/rfc8878
[4]: https://bugs.chromium.org/p/chromium/issues/detail?id=1246971
[5]: https://bugzilla.mozilla.org/show_bug.cgi?id=zstd
[6]: https://twitter.com/mholt6/status/1137176475784732673
[7]: https://github.com/tokers/zstd-nginx-module
[8]: https://github.com/curl/curl/commit/e13357b14b7de013043d704dc9c80697e62616c6
[9]: https://github.com/rockdaboot/wget2/commit/c9796a174d04099d07dd7dc70da47ea92d3ba3a6

### What is the feature you are proposing to solve the problem?

Add support for zstd compression in Node's zlib module.

### What alternatives have you considered?

_No response_
Repository: pytorch
Issue: Inplace binary ops on tensor subclasses can cause mypy error
Labels: module: typing,triaged

### 🐛 Describe the bug

Using inplace binary ops on a subclass of `Tensor` will cause mypy error (e.g. `*=` shown below, same for other ops `+=` etc.)
```python
import torch
a = torch.nn.Parameter(torch.Tensor())
a *= 2
```
run `mypy`:
```
a.py:3: error: Result type of * incompatible in assignment
```
This is because of pyi definition `def __imul__(self, other: Any) -> Tensor: ...`, which means it always returns `Tensor` but not the subclass.

---

Although mypy does not give any error with `a.mul_(2)` instead of `a*=2`, they should be the same, and inplace methods like `mul_` should return `Self` instead of `Tensor`.
```python
import torch
a = torch.nn.Parameter(torch.Tensor())
print(a.mul_(2).__class__)
```
The result is indeed `torch.nn.parameter.Parameter`.

### Versions

master

cc @ezyang @malfet @rgommers @xuzhao9 @gramster
Repository: godot
Issue: Editor: PinJoint2D does not remove warning
Labels: bug,topic:editor,topic:physics,needs testing,topic:2d

### Godot version

v4.0.2.stable.official [7a0977ce2]

### System information

Windows 10, compatibility renderer

### Issue description

PinJoint2D still shows warning triangle even when nodes are assigned, must switch to different scene tab to remove triangle

### Steps to reproduce

Make scene with rigidbody, add rigidbody child, add pinJoint2D, assign nodes to pinJoint2D

### Minimal reproduction project

N/A
Repository: flutter
Issue: Documentation: `SliverPersistentHeader` needs more documentation
Labels: c: new feature,framework,f: scrolling,d: api docs,c: proposal,P2,team-framework,triaged-framework

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I am trying to figure out how to put some controls below a `SliverAppBar`. As far as I can tell, `SliverPersistentHeader` is the right way to do this. But there is almost no documentation about how to write this:

https://api.flutter.dev/flutter/widgets/SliverPersistentHeader-class.html

The documentation for the required `SliverPersistentHeaderDelegate` is almost nonexistent:

https://api.flutter.dev/flutter/widgets/SliverPersistentHeaderDelegate-class.html

I found some 3rd-party documentation about how to use `SliverAppBar`, and it's much better than Flutter's own documentation, but it gives no clues about how to write the delegate:

https://blog.logrocket.com/how-to-add-sliverappbar-to-your-flutter-app/

### Proposal

Please fully document `SliverAppBar` and related classes. Thanks!
Repository: create-react-app
Issue: WebpackDevServerUtils function prepareUrls regex error
Labels: needs triage,issue: bug report

Just found the workaround for this using DANGEROUSLY_DISABLE_HOST_CHECK by reading a comment in the code somewhere other than where the error is generated. This took me the better part of three days to find.

Anyone who uses a VPN will fail with this solution.  It should be clearly spelled out as a failure at that point rather than the second discovery of an array that is undefined.  If you are not going to allow VPN IP addresses at least trap the error and tell the user that they need to add DANGEROUSLY_DISABLE_HOST_CHECK  to their .env file. And if it is a DANGER then this should never have been the solution. 

In  main/packages/react-dev-utils/WebpackDevServerUtils.js 

Line 50 tests a regex

```
 if (
          /^10[.]|^172[.](1[6-9]|2[0-9]|3[0-1])[.]|^192[.]168[.]/.test(
            lanUrlForConfig
          )
```
 Which will only return true for 

Addresses starting with 

10.x.x.x  such as 10.0.0.0 - 10.255.255.255
172.1x.x.x such as 172.16.0.0  - 172.19..255.255
172.2x.x.x such as 172.20.0.0  - 172.29..255.255
172.3x.x.x such as 172.30.0.0  - 172.31..255.255
192.168.x.x  such as 192.168.0.0 - 192.168.255.255

This set of IP addresses is at best parochial and at worst an oversight in test related to FB acceptable local IP addresses.

VPNs that start with say 62 will fail every time.

The solution is to change the regex so that it accepts all local and VPN IP addresses or remove the test altogether.

Either way, the fix should be only one or two lines  such as

```
 if (/^(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$/.test(lanUrlForConfig))
 
```
 This is for the most recent release and can be seen on main here 

https://github.com/facebook/create-react-app/blob/main/packages/react-dev-utils/WebpackDevServerUtils.js
Repository: create-react-app
Issue: Question About 6 high severity vulnerabilities
Labels: needs triage

I am getting this as message in my terminal that the package contains 6 high severity vulnerabilities. Is it safe to go with this package these days.

I am new with this type of project. I am unable to understand all things mentioned about this topic on internet.  Can anyone help to understand, Is it really be  a problem which can lead to data loss or backend tracking.

<img width="1440" alt="Screenshot 2023-06-11 004953" src="https://github.com/facebook/create-react-app/assets/127131889/b4eac515-a052-4c8f-9518-0c2a5db70a61">
Repository: godot
Issue: Crash when opening fbx file with missing bone map reference
Labels: bug,topic:editor,topic:import,crash,topic:3d

### Godot version

4.0.3.stable.mono.official.5222a99f5

### System information

Windows 11, GeForce RTX 3060, Ryzen 5 5600X

### Issue description

Program crashes if I try to open an fbx file in the editor, if that fbx file contains a Skeleton3D which I have set a bone map for, saved that bone map, but then deleted the bone map. In other words the editor is looking for a missing bone map and cannot find it. 

The program should not crash outright, it should just warn the user and reset the reference.

The console output during the crash is as follows: 

```
ERROR: Cannot open file 'res://new_bone_map.tres'.
   at: (scene/resources/resource_format_text.cpp:1659)
ERROR: Failed loading resource: res://new_bone_map.tres. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:222)
ERROR: ConfigFile parse error at res://Bear.fbx.import:33: Can't load resource at path: 'res://new_bone_map.tres'..
   at: _parse (core/io/config_file.cpp:304)
ERROR: Cannot open file 'res://new_bone_map.tres'.
   at: (scene/resources/resource_format_text.cpp:1659)
ERROR: Failed loading resource: res://new_bone_map.tres. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:222)
ERROR: ConfigFile parse error at res://Bear.fbx.import:33: Can't load resource at path: 'res://new_bone_map.tres'..
   at: _parse (core/io/config_file.cpp:304)
ERROR: Cannot open file 'res://new_bone_map.tres'.
   at: (scene/resources/resource_format_text.cpp:1659)
ERROR: Failed loading resource: res://new_bone_map.tres. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:222)
ERROR: ConfigFile parse error at res://Bear.fbx.import:33: Can't load resource at path: 'res://new_bone_map.tres'..
   at: _parse (core/io/config_file.cpp:304)
ERROR: FATAL: Condition "!exists" is true.
   at: operator[] (./core/templates/hash_map.h:504)
```

Notably, the program no longer crashes in this situation if I delete the ".godot" cache folder. Therefore I have included this folder in the sample project, contrary to directions.

### Steps to reproduce

1. Open the included sample project.
2. Try to open Bear.fbx
3. Observe crash

To recreate the crash condition from scratch:
1. Import Bear.fbx, or probably any fbx file with a skeleton.
2. In the skeleton node of the fbx in the import properties, add a bone map, and save the bone map as a resource file.
3. Close the import properties window.
4. Delete the bone map resource you saved. 
5. Try to open the fbx file
6. Observe crash

### Minimal reproduction project

[removed because it contains copyrighted assets. You can probably use any fbx file with a skeleton]
Repository: rust
Issue: Source of `'static` lifetimes in types don't show up in diagnostics
Labels: A-diagnostics,A-lifetimes,T-compiler,D-terse

### Code

```Rust
struct Foo<'a> {
    s1: &'a str,
    s2: &'static str
}

fn make_foo<'a>(s: &'a str) -> Foo<'a> {
    Foo {
        s1: s,
        s2: s
    }
}
```


### Current output

```
error: lifetime may not live long enough
 --> src/lib.rs:9:13
  |
6 | fn make_foo<'a>(s: &'a str) -> Foo<'a> {
  |             -- lifetime `'a` defined here
...
9 |         s2: s
  |             ^ this usage requires that `'a` must outlive `'static`

error: could not compile `playground` (lib) due to previous error
```


### Desired output

Something that indicates where the static lifetime comes from

```
error: lifetime may not live long enough
 --> src/lib.rs:9:13
  |
6 | fn make_foo<'a>(s: &'a str) -> Foo<'a> {
  |             -- lifetime `'a` defined here
...
9 |         s2: s
  |             ^ this usage requires that `'a` must outlive `'static`
--
3 |     s2: &'static str
  |         ^ `'static` lifetime specified here
```


### Rationale and extra context

There's nothing in the function body or in the diagnostic to indicate why something must be `'static` if that information is associated with a type, so giving a hint would be helpful.

By comparison, it's much easier to figure out non-static things since the named lifetime `'a` clearly has a relationship with the type `Foo`.

```
5 |   fn make_foo<'a, 'b>(s: &'b str) -> Foo<'a> {
  |               --  -- lifetime `'b` defined here
  |               |
  |               lifetime `'a` defined here
6 | /     Foo {
7 | |         s1: s,
8 | |     }
  | |_____^ function was supposed to return data with lifetime `'a` but it is returning data with lifetime `'b`
```

### Other cases

_No response_

### Anything else?

_No response_