sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Derive macros may cause weird suggestion
Labels: A-diagnostics,T-compiler

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
#[derive(sqlx::FromRow)]
struct Foo {
    bar: _,
}

fn main() {}
```

The current output is:

```
error[E0121]: the placeholder `_` is not allowed within types on item signatures for structs
 --> src\main.rs:3:10
  |
3 |     bar: _,
  |          ^ not allowed in type signatures
  |
help: use type parameters instead
  |
2 ~ struct Foo<T> {
3 ~     bar: T,
  |

error[E0121]: the placeholder `_` is not allowed within types on item signatures for implementations
 --> src\main.rs:3:10
  |
3 |     bar: _,
  |          ^
  |          |
  |          not allowed in type signatures
  |          not allowed in type signatures
  |
help: use type parameters instead
  |
1 ~ #[derive(sqlx::FromRo, Tw)]
2 | struct Foo {
3 ~     bar: TT,
  |

For more information about this error, try `rustc --explain E0121`.
error: could not compile `sandbox` due to 2 previous errors
```
Additionally, here is a screenshot of the capture for coloring to be visible:
![image](https://user-images.githubusercontent.com/16705820/179937503-e519e371-2b03-4830-9864-4129e549abc5.png)


<!-- The following is not always necessary. -->
Ideally the second error should either not provide any suggestion or be skipped altogether as it seems to be related to auto-generated code.
<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

I was only able to reproduce this with an external derive macro. I am not knowledgeable enough to try to create one causing this myself.

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions. The output might also be
different depending on the Edition.
-->
Repository: PowerToys
Issue: Always On Top - Borders for All Windows - Like Windows Used to Be
Labels: Product-Window Manager,Product-Tweak UI Design

### Description of the new feature / enhancement

It would be nice if we could bring back borders for all windows, with the active windows displaying one color while the inactive windows display another color, in addition to the Always On Top window border color.  

### Scenario when this would be used?

The thin Windows 7, 10, and 11 borders have always made it difficult at times for me to discern where one application started and the other ended, especially where one substantially overlaps the other.  One apps menu easily blends in with the other apps menus, making it easy to select something from the wrong menu and requiring the user to backtrack or switch back to the intended app.

### Supporting information

_No response_
Repository: three.js
Issue: Expose rotateLeft & rotateUp in OrbitControls
Labels: Enhancement

**Is your feature request related to a problem? Please describe.**

I have a use case, where I need to rotate the camera when the user's cursor goes near the edge of the screen.
At the moment it is implemented with me rotating the model itself, but this has been causing problems.

**Describe the solution you'd like**

There are these 2 fuctions in OrbitControls.js that would be useful if they were public: 'rotateLeft' and 'rotateUp'. This way I could call them by hand to rotate the camera.

**Describe alternatives you've considered**

1 more thing I tried was to use the 'autoRotate' feature, but this doesn't work because in my use case the rotation only happens when the user's mouse button is held down. (however autoRotate doesn't work when the mouse button is being held down)
This could be another solution if we could control whether the autoRotation should occur even with the mouse button held down.
Repository: next.js
Issue: Router does not use cache hits correctly when the link to ISR page contains query params.
Labels: bug,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.0.0
      npm: 8.6.0
      Yarn: 1.22.18
      pnpm: N/A
    Relevant packages:
      next: 12.2.3-canary.14
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

Irrelevant

### How are you deploying your application? (if relevant)

Irrelevant

### Describe the Bug

When a `<Link />` component contains a query and refers to an ISR page, when you click on that Link, Next makes an additional request before redirecting.

### Expected Behavior

Cache-hits should work the same for ISR pages with and without query params.

### Link to reproduction

https://github.com/ku8ar/next-js-no-cache-with-query

### To Reproduce

1. `yarn build`
2. `yarn start`
3. hover second link
4. click it
5. blue progress bar will appear at the top of the screen indicating an async request, and an additional unnecessary request will appear in devtools.

<img width="600" alt="Zrzut ekranu 2022-07-20 o 11 30 51" src="https://user-images.githubusercontent.com/16975059/179950553-03e7d8f5-a841-415e-830d-3dc426ce59d0.png">
Repository: godot
Issue: Undo reverts to scene editor when script editor is in use if game is run then undo-ed
Labels: bug,topic:editor

### Godot version

3.5.rc6

### System information

Windows 10

### Issue description

If editing a script, running a game, closing it down and then immediately pressing ctrl+z, it will undo the scene editor instead of the script editor.

### Steps to reproduce

1. Bring up script editor
2. Run game
3. Close game down
4. Press ctrl+z

### Minimal reproduction project

_No response_
Repository: create-react-app
Issue: Feature Request: Make it easier to use testing/test-running ability of react-scripts out of CRA apps
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

Almost.
My scenario is that I have a non-CRA React app, with NextJS and custom babel configurations, using ts and tsx, it is inside a monolith, each package in the monolith uses different babel configurations and some of them are CRA. I wanted to write unit tests for this app I'm talking about, but I failed in every single way, it was hard to set up jest to be able to parse and run my tests when it was importing things from other packages. The first thing that hit my mind was to use `react-scripts` for running tests. Ultimately it did the job, but I had to eject, remove every ejected file related to building, watching & dev-server, and remove all unnecessary dependencies from package.json (this part was hard for me as this monolith takes a lot of time to re-install & re-link everything to make sure it is not broken) and probably I'm going to have lots of explanation to do to my colleagues why I did that:
![image](https://user-images.githubusercontent.com/5755214/179977355-471d67dc-a068-4611-bbeb-9b7521f65a0c.png)


### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

The actual problem was that `react-scripts` only looks in the `src` directory, but my app didn't have an `src` directory, I ejected everything just to be able to remove hard-coded src from jest configuration. (in the picture above I've removed it). It could be super cool if we supported `src` in overriding configurations: https://create-react-app.dev/docs/running-tests#configuration

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

configuring jest manually. But it was hard to do.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here if you haven't already.
-->

-
Repository: PowerToys
Issue: Translation of power toys run
Labels: Product-PowerToys Run,Needs-Triage,Needs-Team-Response,Issue-Translation

### Description of the new feature / enhancement

See the search bar in spanish (Start typing ---> Escribe aquí para buscar)

### Scenario when this would be used?

When you starts the function of power toys run

### Supporting information

_No response_
Repository: tauri
Issue: Failed to load resource: The resource could not be loaded because the App Transport Security policy requires the use of a secure connection.
Labels: type: bug,status: needs triage

### Describe the bug

Are HTTP resource requests not allowed?I am an application packaged by macos and found that http images cannot be loaded using,And I configured http
```
"tauri": {
    "allowlist": {
      "all": true,
      "http": {
        "all": true,
        "request": true
      }
    },
```
or
```
"tauri": {
    "allowlist": {
      "all": true,
      "http": {
        "all": true,
        "request": true,
        "scope":["www.xxxx.com/*"]
      }
    },
````
No effect, any resources of http are not allowed to be requested
<img width="1173" alt="image" src="https://user-images.githubusercontent.com/33121872/180002580-84b115bd-2e14-40c0-987c-a8b2a0a2b3a1.png">


### Reproduction

_No response_

### Expected behavior

Hope that the packaged http image can be used

### Platform and versions

```shell
Environment
  › OS: Mac OS 12.4.0 X64
  › Node.js: 16.13.0
  › npm: 8.1.0
  › pnpm: 6.32.4
  › yarn: 1.22.18
  › rustup: 1.24.3
  › rustc: 1.60.0-nightly
  › cargo: 1.60.0-nightly
  › Rust toolchain: nightly-aarch64-apple-darwin

Packages
  › @tauri-apps/cli [NPM]: 1.0.4
  › @tauri-apps/api [NPM]: 1.0.2
  › tauri [RUST]: 1.0.4,
  › tauri-build [RUST]: 1.0.4,
  › tao [RUST]: 0.12.1,
  › wry [RUST]: 0.19.0,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:3000/
  › framework: React

App directory structure
  ├─ dist
  ├─ node_modules
  ├─ src-tauri
  ├─ .git
  ├─ .idea
  └─ src
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: Support CompletionList.isIncomplete=true on empty lists (or at least, clearly document current behaviour)
Labels: suggest,under-discussion

I was surprised to find that `CompletionList.isIncomplete=true` seems to be ignored when the result set is empty. The Dart server has the ability to place a maximum time on completions for not-currently-imported symbols to avoid slowing down all code completion to wait for these results (but typing further characters to narrow things down could include them).

As far as I can tell, VS Code's current behaviour of ignoring `isIncomplete=true` when the list is empty could be simulated by returning `isIncomplete=false` when the list is empty (which makes sense, logically) so this limitation feels overly-restrictive.

Additionally, the comment at https://github.com/microsoft/vscode/issues/13735#issuecomment-253753649 suggests that this is also the case if the _client-filtered_ list is empty. However, this is not what happens in my experience. If I insert a single item with label "FAKE" and then invoke completion with a prefix of "aaa", then `isIncomplete` _is_ still honoured, and further keystrokes result in additional trips to the server.

So this is initially a request to support `isIncomplete=true` for empty lists, but if that's not going to change, I would at least like to see the current behaviour clearly documented (since LSP inherits this behaviour, and it's important LSP clients and servers have a good understanding of each others behaviour).

I suspect there are other people that would like to see this:

- @svenefftinge who originally asked about this in https://github.com/microsoft/vscode/issues/13735
- @ramya-rao-a asked about this at https://github.com/microsoft/vscode/issues/32423 but it's not clear what the resolution was
- @ckant appears to have had to work around this in aws-toolkit at https://github.com/aws/aws-toolkit-vscode/commit/9f85fadab26fad65257559f594e448080262e975 (see the last part of the commit message)
- @puh appears to have worked around this in https://github.com/puuuuh/crates/commit/81077a84e27921f92faef60020b6667a18baf223 in the same way by re-inserting a dummy entry containing the typed prefix

These are just the cases that mentioned the previous issue so they showed up on GitHub, I suspect there are many more.

The problem with the workaround of inserting the prefix is not just that it looks odd to users, but it doesn't work if there is no prefix. If the user hits Ctrl+Space and gets no items, the extension/server is never given any opportunity to provide completions as they type.
Repository: flutter
Issue: Can't move caret within composing region on iOS, though it appears to move
Labels: a: text input,platform-ios,framework,a: internationalization,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,found in release: 3.9,team-design,triaged-design


https://user-images.githubusercontent.com/12570868/180020978-b7f2269e-4c89-4a8d-b301-a3d48facc556.mp4



## Steps to Reproduce
1. Use iOS to input some Chinese，not choose the exact word；
2. long press the space key to move the cursor pos, to the first or the any position of middle;
3. press the backspace to delete char

**Expected results:** 
delete the char before the position of the cursor

**Actual results:** <!-- what did you see? -->
the end char was deleted ,and the cursor position jump to the end

<details>
Demo code:

```dart

import 'package:flutter/material.dart';

class DemoPage extends StatefulWidget {
  const DemoPage({Key? key}) : super(key: key);

  @override
  State<DemoPage> createState() => _DemoPageState();
}

class _DemoPageState extends State<DemoPage> {

  @override
  void initState() {
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      resizeToAvoidBottomInset: false,
      appBar: AppBar(
        title: const Text("Demo Page"),
      ),
      body: Center(
        child: Column(
          children: const [
            TextField(),
          ],
        ),
      ),
    );
  }
}

```

</details>

flutter doctor:
```
Flutter 3.0.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f1875d570e (7 天前) • 2022-07-13 11:24:16 -0700
Engine • revision e85ea0e79c
Tools • Dart 2.17.6 • DevTools 2.12.2

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.5, on macOS 12.4 21F79 darwin-x64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2021.2)
[✓] VS Code (version 1.69.0)
[✓] Connected device (4 available)
[✓] HTTP Host Availability
```
Repository: rust
Issue: Tracking Issue for proc_macro::{tracked_env, tracked_path}
Labels: T-libs-api,C-tracking-issue,A-proc-macros

Feature gate: `#![feature(proc_macro_tracked_env, track_path)]`

This is a tracking issue for `proc_macro::tracked*`, to allow adding files and environment variables to the build system's dependency tracking.

### Public API

```rust
// proc_macro

mod tracked_env {
    pub fn var<K: AsRef<OsStr> + AsRef<str>>(key: K) -> Result<String, VarError>;
}

mod tracked_path {
    pub fn path<P: AsRef<str>>(path: P);
}
```

### Steps / History

- [x] Implementation of `tracked_env::var`: https://github.com/rust-lang/rust/pull/74653
- [x] Implementation of `tracked_path::path`: https://github.com/rust-lang/rust/pull/84029
- [x] Add tracking issue: https://github.com/rust-lang/rust/pull/99516
- [ ] Change `path` to accept `AsRef<Path>` instead of `AsRef<str>`
- [ ] Design the public API
- [ ] Documentation
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- [ ] The full API design.
   - The implementaiton PRs were mostly focussed on the implementation details behind the scenes of `proc_macro`, but there's barely been any discussion on the public interface.
Repository: angular
Issue: Renderer2 lacks security documentation
Labels: security,P3,bug,area: docs

### Description

Angular docs are doing a great job at covering security topics. In particular, API docs warn about methods that could be used in an insecure manner. (Big thank you to the community!)

Unfortunately, `Renderer2` API docs do not say much about security. In particular, nothing regarding XSS. However, the [ElementRef](https://angular.io/api/core/ElementRef#properties) API docs state the following:

> Alternatively you can take a look at [Renderer2](https://angular.io/api/core/Renderer2) which provides API that can safely be used even when direct access to native elements is not supported.

Wouldn't it be helpful to mention this in the Renderer2 API docs? So that potential users know what to expect...

### What is the affected URL?

https://angular.io/api/core/Renderer2

### Please provide the steps to reproduce the issue

1. Read `Renderer2` API docs
2. Read `ElementRef` API docs 

### Please provide the expected behavior vs the actual behavior you encountered

I would _expect_ the the `Renderer2` API docs to document security implications. Specifically regarding XSS. `ElementRef` docs say that `Renderer2` "provides API that can safely be used".
If this is true (and superficial testing seems to support it) I'd _expect_ that the `Renderer2` API docs mention it explicitly.

If there are any exceptions to this general rule, I'd _expect_ the `Renderer2` API docs would show a clear "USE WITH CAUTION" security warning. E.g. if the following method calls lead to XSS, I'd _expect_ a warning in the API docs:
```
renderer2.setAttribute(a, 'href', 'javascript:alert(1)');
renderer2.setAttribute(svg, 'onload', 'alert(1)');
```

Alternatively, if the claims that `ElementRef` docs make about `Renderer2` are inaccurate or misleading, I'd _expect_ them to be adjusted or removed.

The _actual_ situation is that `Renderer2` API docs do not tell me anything about security. And I feel a little lost.

### Please provide a screenshot if possible

Should be trivial to reproduce without screenshots, but I can provide some on demand...

### Please provide the exception or error you saw

```true
None.
```


### Is this a browser-specific issue? If so, please specify the device, browser, and version.

```true
Not browser-specific imho.
```
Repository: vscode
Issue: Upstream find filter and replace improvements into workbench SimpleFindWidget
Labels: feature-request,debt,notebook-find,terminal-find

The notebook find widget is an extension of `SimpleFindWidget`, if we upstream changes into `SimpleFindWidget` it will consolidate logic and make those features available to consumers of `SimpleFindWidget` (terminal, webview)

cc @rebornix
Repository: vscode
Issue: Move SimpleFindWidget into base
Labels: debt,notebook-find,terminal-find

Currently the new list view find box uses FindInput instead of SimpleFindWidget because the list lives in base, not workbench. We should give `SimpleFindWidget` the same treatment as `HoverWidget` to fix this. Ideally we would do this:

- Move SimpleFindWidget into base
- Allow injecting services into SimpleFindWidget for convenience when used in workbench (extending in platform?)
- Have the editor FindWidget extend SimpleFindWidget to reduce code duplication

cc @rebornix @joaomoreno @andreamah
Repository: go
Issue: go/doc/comment: Plurals of linked symbols do not work
Labels: NeedsDecision

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19rc2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/.../.cache/go-build"
GOENV="/home/.../.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/.../go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/.../go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/.../sdk/go1.19rc2"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/.../sdk/go1.19rc2/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19rc2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK="/home/.../workspaces/namespaces/go.work"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4195388595=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Writing a doc comment linking to a type as follows:

```go
// ComposerProject represents a set of either running or paused (but always
// "somehow" alive) [Container]s belonging to a specific Docker
// Compose/Composer project.
```

I'm aware of the go tip documentation about doc comments with the current definition:

> To avoid problems with maps, generics, and array types, doc links must be both preceded and followed by punctuation, spaces, tabs, or the start or end of a line.

### What did you expect to see?

Pluralization, such as the `[Container]s` link to be properly resolved into a hyperlink to the Container type.

### What did you see instead?

`[Container]s`
Repository: flutter
Issue: Investigate pubsub message encoding differences
Labels: team-infra,P3,triaged-infra

In reference to:

https://github.com/flutter/flutter/issues/107961

We had an event due to some pubsub messages had data base64 encoded, whereas others had them unencoded.

This bug is to track investigation of why this occurred, and to put in place changes to avoid these types of issues in the future. Ideally we should revert the changes made to handle both casesL

https://github.com/flutter/cocoon/pull/1991
https://github.com/flutter/cocoon/pull/1992

with a more robust scheme.
Repository: three.js
Issue: Docs: portuguese version
Labels: Documentation

Hello,
I intend to start translating the documentation into Portuguese. starting with the manual section
Repository: pytorch
Issue: Rename DispatchKey Dense/Sparse/etc to DenseFunctionality/SparseFunctionality, use original name for alias
Labels: module: internals,triaged

### 🚀 The feature, motivation and pitch

This means you could register a kernel as "Sparse" and it would apply to all sparse backends, instead of having to register SparseCPU, SparseCUDA one by one as we do today

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh