sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: FormItemInputContext is always an empty object in a customized form control
Labels: Inactive,improvement

### Reproduction link

[https://stackblitz.com/edit/react-vhhuml?file=src%2Findex.js,src%2FApp.js](https://stackblitz.com/edit/react-vhhuml?file=src%2Findex.js,src%2FApp.js)

### Steps to reproduce

1. Type anything in input
2. Watch the changes in the console

### What is expected?

I'm writing a customized form control. I found that we are using the `FormItemInputContext` to share the context from the `Form.Item` to the children, so I want to use the `FormItemInputContext` to get the `contextStatus`, `hasFeedback`, `feedbackIcon`,... but it's always an empty object. So how to use it in a customized form control?

### What is actually happening?

The context is always an empty object

| Environment | Info |
| --- | --- |
| antd | 4.21.0 |
| React | 17.0.2 |
| System | Windows |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: testSerializationInterop in test/cpp/jit/torch_python_test.cpp has not run in over two years
Labels: oncall: jit

### 🐛 Describe the bug

This was moved into the file in https://github.com/pytorch/pytorch/pull/44795 but wasn't called even then. Please delete the code or fix it and reenable it.

### Versions

head
Repository: godot
Issue: Add a property to make BaseMaterial3D Deep Parallax more aggressive (at the cost of artifacts)
Labels: enhancement,discussion,topic:rendering,topic:3d

### Godot version

4.0dev

### System information

Not specific

### Issue description

The default behaviour of the shader when height and parallax are enabled is to remap coordinates with
`vec2 P = view_dir.xy * heightmap_scale;`
in place of 
`vec2 P = view_dir.xy / view_dir.z * heightmap_scale;`
The first option does create visible artifacts for view-vectors close to the tangent, which is not always acceptable.
I would suggest to let the user specify which variant of the shader to generate depending on which artifacts are worse for the specific application.

### Steps to reproduce

Generate the shader code from any StandardMaterial3D with height and deep parallax enabled to verify.

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Expose the hostname (server name on which VSCode is running on)
Labels: feature-request,api,extension-host

Hello,

When VSCode is connected to any remote server, we have the information on the green icon 
![image](https://user-images.githubusercontent.com/1360459/173089213-bb14e328-3a8a-4f1b-8817-c6eb2a3c59cf.png)
, or in the remote view.

If VSCode / remote-ssh exposes this hostname all extensions could use this information to build proper view with data depending on it. 
In our case we are building an extension that displays a list of mount point / container running on the several hosts. If VSCode is connected on a specific container thanks to the hostname exposed we could easily adapt the view / the action allowed to the user and call an internal API with the hostname as filter.


Thanks in advance.
Best regards
Repository: flutter
Issue: Web renderer html of RangeSlider is faded while it is ok using canvaskit
Labels: engine,a: fidelity,platform-web,c: rendering,e: web_html,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-web,triaged-web

![--web-renderer html](https://user-images.githubusercontent.com/107267709/173105260-830a1a93-7147-43e4-8273-8ebd734992fb.png)
![--web-renderer canvaskit](https://user-images.githubusercontent.com/107267709/173105267-2cada4f5-2056-4d5b-8651-74cdd0e2af64.png)
Repository: vscode
Issue: when hovers are not sticky, alt/opt key should make them temporarily sticky
Labels: feature-request,editor-hover,workbench-hover

Version 1.68 introduced the feature of holding the ALT (OPT on Mac) key down in order to make hover texted locked so that you can move the text over it, and then magnify, select text, etc. from the hover. But then this:

> Note that this feature only applies outside of the editor because editor hovers can always be moused over unless specified otherwise via the editor.hover.sticky setting

Setting 'editor.hover.sticky' to false is very good at preventing accidental clicks on a popup hover text, when you really mean to click on the line above the thing causing the hover (sometimes the hover text shows up at exactly the wrong time, and then you end up going to MDN or Can I Use, etc.). I would like it if I could keep 'editor.hover.sticky' as false, but press the ALT or option key down during a hover for when I actually do want to click on the link in the hover text, or when I do want to zoom in on it or copy something from it.
Repository: opencv
Issue: imgcodecs: default values of imread / imreadmulti flags are not aligned
Labels: bug,category: imgcodecs,RFC

`IMREAD_COLOR` vs `IMREAD_ANYCOLOR`

```
Mat imread( const String& filename, int flags = IMREAD_COLOR );
```

vs

```
bool imreadmulti(const String& filename, std::vector<Mat>& mats, int flags = IMREAD_ANYCOLOR);
```

The last one was added here: #3575
Repository: tensorflow
Issue: Use of Keras `jit_compile` in a distribution strategy causes a `std::system_error`
Labels: stat:awaiting tensorflower,type:bug,comp:dist-strat,TF 2.9

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Source

binary

### Tensorflow Version

tf 2.9.1

### Custom Code

No

### OS Platform and Distribution

_No response_

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

11.2/8.1.1.33

### GPU model and memory

_No response_

### Current Behaviour?


The following error is thrown during training after a number of steps / epochs 
```shell
terminate called after throwing an instance of 'std::system_error'
what():  Resource temporarily unavailable
```
I am able to reproduce this error in colab with my sample code



### Standalone code to reproduce the issue

```python
import keras
import tensorflow as tf

def build_model_() -> keras.Model:
    input = tf.keras.layers.Input(shape=(5,), name='input_a')
    x = tf.keras.layers.Dense(512, activation = 'relu')(input)
    x = tf.keras.layers.Dense(512, activation = 'relu')(x)
    output = tf.keras.layers.Dense(1, name='output')(x)
    model = tf.keras.models.Model(inputs=input, outputs=output)
    return model


strategy = tf.distribute.MirroredStrategy()
print(f"Can see {strategy.num_replicas_in_sync} gpus")
with strategy.scope():
  model = build_model_()
  model.compile(loss = 'mse', jit_compile=True)

BATCH_SIZE_PER_REPLICA = 1024
GLOBAL_BATCH_SIZE = BATCH_SIZE_PER_REPLICA * strategy.num_replicas_in_sync

options = tf.data.Options()
options.experimental_distribute.auto_shard_policy = tf.data.experimental.AutoShardPolicy.DATA

dataset = tf.data.Dataset.from_tensors(
    (tf.ones(5), 1)
).repeat(10_000_000).batch(GLOBAL_BATCH_SIZE).with_options(options)

history = model.fit(
    x = dataset,
    epochs=7,
    verbose = 1,
)
```


### Relevant log output

_No response_</details>
Repository: flutter
Issue: [image_picker] Make `LostDataResponse.files` non-nullable
Labels: p: image_picker,package,team-ecosystem,P3,p: requires breaking change,triaged-ecosystem

Best practice is to make collections non-nullable when possible so that we don't have two different ways to express empty. Currently we're being careful to return null when the list would be empty, to match the docs, but it would be easy to get that wrong and potentially break client code.

The next time we do a breaking change to `image_picker` we should make it non-nullable. It's complicated by the fact that it's in the platform interface even though it's part of the public API, so it would be a breaking change to the platform interface as well.
Repository: tauri
Issue: [bug] Could not determine the accessibility bus address
Labels: type: bug,platform: Linux,platform: Nix/NixOS

### Describe the bug

Hello,

Might be linked to https://github.com/tauri-apps/tauri/issues/4174, not sure as it's the same error but not the same case at all.

When trying to run tauri dev for benchmark purpose (https://github.com/Elanis/web-to-desktop-framework-comparison/pull/73), I'm having an error saying `Could not determine the accessibility bus address`. Google isn't helping a lot this time :/

This ends like this:
```
Building [=======================> ] 366/367: app(bin)                    
Finished dev [unoptimized + debuginfo] target(s) in 7m 31s
Running `target/debug/app`
Could not determine the accessibility bus address
```
([Link to full logs, with specific line](https://github.com/Elanis/web-to-desktop-framework-comparison/runs/6834052075?check_suite_focus=true#step:11:4771))


### Reproduction

- Create an empty app
- Create a github action CI on ubuntu-latest
   - Install recommended linux packages (https://tauri.studio/v1/guides/getting-started/prerequisites#setting-up-linux)
   - npx tauri dev

### Expected behavior

_No response_

### Platform and versions

```shell
Packages
  › @tauri-apps/cli [NPM]: 1.0.0-rc.13
  › @tauri-apps/api [NPM]: 1.0.0-rc.6
  › tauri [RUST]: 1.0.0-rc.14,
  › tauri-build [RUST]: 1.0.0-rc.12,
  › tao [RUST]: 0.9.1,
  › wry [RUST]: 0.17.0,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: ../dist

App directory structure
  ├─ dist
  ├─ node_modules
  └─ src-tauri
```


### Stack trace

_No response_

### Additional context

Here is my pull request where I try to fix that behavior: https://github.com/Elanis/web-to-desktop-framework-comparison/pull/73
Repository: pytorch
Issue: `prepare_qat_fx` docstring doesn't run
Labels: oncall: quantization,triaged,module: fx

This code example is in the docstring for `torch.ao.quantization.quantize_fx_prepare_qat_fx`:

https://github.com/pytorch/pytorch/blob/35eda5f95956c3631e5684d519213944ab66b012/torch/ao/quantization/quantize_fx.py#L495-L509

There are two issues:
(1) The import `from torch.ao.quantization import prepare_fx` doesn't actually work. The path is wrong.
(2) This example doesn't even use the function it is describing, but instead uses `prepare_fx`, which is for PTQ, not QAT

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @ezyang @SherlockNoMad @EikanWang @wenzhe-nrv
Repository: rust
Issue: Rust doesn't warn about never read fields in unreachable pub structures
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
mod m {
    pub struct Foo {
        pub a: i32,
        pub b: i32,
    }
}
fn main() {
    let _x = m::Foo { a: 3, b: 4 };
}
```

The current output is:

```
```

<!-- The following is not always necessary. -->
Ideally the output should look like:

```
warning: field is never read: `a`
 --> src/main.rs:3:9
  |
3 |         pub a: i32,
  |         ^^^^^^^^^^
  |
  = note: `#[warn(dead_code)]` on by default

warning: field is never read: `b`
 --> src/main.rs:4:9
  |
4 |         pub b: i32,
  |         ^^^^^^^^^^
```

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
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.
-->

When using `pub(crate)` the warnings appear, which suggests to me that the same should be the case when having unreachable `pub`.

```rust
mod m {
    pub(crate) struct Foo {
        pub a: i32,
        pub b: i32,
    }
}
fn main() {
    let _x = m::Foo { a: 3, b: 4 };
}
```
Repository: vscode
Issue: Git - add capability to compare files/folders
Labels: feature-request,git

Issue Type: <b>Bug</b>

problem using vscode is it didn't have decent git tool.
developers needs to do many thing with git.
vscode is crap when i need to review my changes with version control.

VS Code version: Code 1.68.0 (Universal) (4af164ea3a06f701fe3e89a2bcbb421d2026b68f, 2022-06-08T11:44:00.250Z)
OS version: Darwin x64 19.6.0
Restricted Mode: No


<!-- generated by issue reporter -->
Repository: create-react-app
Issue: Bug: 
Labels: Status: Unconfirmed

While using proxy (for development purposes) React is adding a "Refer" HTTP header. The contents for mentioned header is by default "http://localhost:3000", which is true for local machine it is running on. But when connecting to a remote serrver with CSRF enabled, like with Laravel, that value breaks the response causing it to fail (code 419), probably because the server treats "localhost" as different reference than our local machine. 
I am not sure whenever it is a bug, but maybe changing the value to actual IP of local machine will fix those issues.

React version: 18.0.0

## Steps To Reproduce

1. npx create-react-app
2. set proxy to a remote backend server with CSRF token (tested for Laravel server)
3. try to POST/GET any data, even the first request will fail with code 419
4.  or send the same request as react does (visible through wireshark or similiar programm) using postman/curl
5.  if we remove or modify he "Refer" header, everything will work as intended. You can input ANY String, just not localhost

## The current behavior
Requests fail because of CSRF key mismatch caused by reference to localhost passed to server

## The expected behavior
The server will have IP passed as a refrence, so the requests won't fail (hopefully)
Repository: electron
Issue: [Feature Request]: Add event that fires when the application is about to enter or exit a modal state
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

I want to be able to tell my webapp (hosted in a BrowserWindow/BrowserView) if the main window is disabled because there's a modal on top (`showMessageBox`, `showMessageBoxAsync`, `showErrorBox`, `print`, etc.)

### Proposed Solution

I'm not sure how feasible this is, but if there could be some events like `enter-modal-state` and `exit-mode-state` on `BrowserWindow` that would fire and give me a chance to send up a message to the webapp before actually becoming modal.

Maybe this would require executing the actual show-modal/print dialog logic on the next tick to give a chance for my handler to run and send up the message?

### Alternatives Considered

Otherwise, I need to find all the places my app shows some kind of modal and send up a message in each place / create wrapper functions that do that.

Maybe there's also some kind of .NET solution where I can detect this case before the main process is actually blocked up and alert my webapp?

### Additional Information

_No response_
Repository: tauri
Issue: [feat] [macOS] Configure `acceptsFirstMouse` for specific elements
Labels: type: feature request,status: upstream,platform: macOS,status: backlog

### Describe the bug

Elements with `data-tauri-drag-region` can't be dragged while the window isn't in focus, which is not how native windows (or Electron's implementation) works

Note: `acceptsFirstMouse` doesn't entirely solve this because that would also make everything in the window clickable

### Reproduction

_No response_

### Expected behavior

_No response_

### Platform and versions

```shell
Environment
  › OS: Mac OS 10.15.7 X64
  › Node.js: 16.15.0
  › npm: 8.12.1
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-apple-darwin 

Packages
  › @tauri-apps/cli [NPM]: 1.0.0-rc.12 (outdated, latest: 1.0.0-rc.13)
  › @tauri-apps/api [NPM]: 1.0.0-rc.6
  › tauri [RUST]: git+https://github.com/tauri-apps/tauri?branch=mac-app-hide#ade64c9b1695043c40ffccb3a38b11d1a7f1b6bb (1.0.0-rc.12),
  › tauri-build [RUST]: 1.0.0-rc.10,
  › tao [RUST]: 0.9.1,
  › wry [RUST]: 0.17.0,

App
  › build-type: bundle
  › CSP: default-src 'self'; img-src *
  › distDir: ../build
  › devPath: http://localhost:9000/
  › framework: Svelte

App directory structure
  ├─ node_modules
  ├─ public
  ├─ .github
  ├─ src-tauri
  ├─ build
  ├─ .git
  ├─ assets
  └─ src
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: flutter
Issue: [Impeller] Extend coverage API for filters to allow supplying input coverage Rects
Labels: engine,c: rendering,P2,e: impeller,team-engine,triaged-engine

Currently, filters resolve coverage rectangles from inputs directly, but there are situations where it's convenient to be able to fetch coverage prior to assigning filter inputs. For example, with backdrop filters, the input for the filter is the parent pass texture. However, the size of the parent pass texture is in part determined by the output size of the filter itself. If its a kernel filter that may expand or contract the texture size (such as Blur and Erode), the parent pass layer should also expand or contract in size.

This circular coverage dependency can be resolved by changing the EntityPass coverage resolution to:
1. Compute the subpass coverage as it currently does.
2. Pass the unfiltered coverage rectangle through the coverage routine of the subpass backdrop filter.
3. Intersect with the SaveLayer bounds rect as usual, if one was given.
Repository: PowerToys
Issue: 希望FancyZones可以根据分辨变化切换布局
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

希望能有一种机制,在FancyZones检测到分辨率变化时切换到指定的布局

### Scenario when this would be used?

场景:  
我的办公电脑显示器是3440x1440  
但是我的笔记本是2560x1440  
很显然这2种分辨率下窗口布局是不一样的  
有时候我会以远程桌面的方式连接到我的办公电脑上进行办公  
这时候需要手动切换FancyZones布局比较麻烦


### Supporting information

_No response_
Repository: bitcoin
Issue: Onlynet=ipv4 disables Tor advertisements
Labels: Bug

I want my node to accept inbound IPv4 and Tor connections, but not make any outbound Tor connections. So I set:

```
listen=1
server=1
onlynet=ipv4
onion=x.x.x.x:9050
externalip=x.x.x.x
externalip=xxx.onion
```

I expect that `onlynet` will limit the outgoing connections to IPv4 only, and `onion` combined with `externalip` allow for Tor incoming connections.

**Actual behavior**

Tor gets completely disabled:

```
    {
      "name": "onion",
      "limited": true,
      "reachable": false,
      "proxy": "x.x.x.x:9050"
    }

```
Limited is true and reachable is false. Also it does not advertise the onion address, just the IPv4:

```
  "localaddresses": [
    {
      "address": "x.x.x.x",
      "port": 8333,
      "score": 270
    }
    ]
```
As soon as I remove the `onlynet` flag, Tor starts working and the address gets advertised.

It seems this behaviour is conflicting with the documentation (which state that `onlynet` affects outbound only).

So is this a bug and if not, how can I reach my goal of limiting outbound to non-tor addresses?
Repository: pytorch
Issue: Batches are being duplicated from go http call
Labels: triaged

### 🐛 Describe the bug

Hi there,

I'm currently testing a  sentence bert (MNLI) model hosted on torchserve GPU.  Here is the relevant encoding call.

```python
        embedding_list = self.model.encode(queries, batch_size=min(len(queries), 512)) 
```

I'm testing two entrypoints to understand latency of this model. 

This first, is in python with a simple requests call

```python

for i in range(1000):
  requests.post('http://localhost:8989/predictions/bert_soft_label_one_to_many_query_scores_new', headers=headers, json=json_blob_10_6500_chars)
  time.sleep(.1) 
```

For the python call, with 10 encodings of ~6500 chars each (total 65k), I see a prediction latency of ~90-120ms. Great (screenshot below)! I also notice similar responses with 100 encoding per call.
<img width="1201" alt="image" src="https://user-images.githubusercontent.com/8621935/173171373-38ccfb07-e137-4b36-8090-c71c8b4db652.png">


However, I'm also testing latency from a golang http calls with the following function call. This code is encoding up to 100 objects per request with ~140  chars each (~14k total), I'm seeing much slower latency but also it looks like the requests are being duplicated? Notice the double `batches` line.  

<img width="1335" alt="image" src="https://user-images.githubusercontent.com/8621935/173171482-ad472166-bcb2-4632-8479-16c14ed227ab.png">


```golang

func (c TorchservedClient) NewGetOneToManyQueryScores(ctx context.Context, otmr *OneToManyQueryScoreRequest) (*OneToManyQueryScoreResponse, error) {
	if otmr == nil {
		return nil, fmt.Errorf("request is empty")
	}
	otmrJson, err := json.Marshal(otmr)
	if err != nil {
		return nil, err
	}
	// This endpoint corresponds to the model name in the .mar file. The base url passed in should look like `http://torchserved-0.torchserved:8080/predictions ` and we add in the model name to this url.
	req, err := http.NewRequestWithContext(ctx, http.MethodPost, c.makeURL("bert_soft_label_one_to_many_query_scores_new"), bytes.NewBuffer(otmrJson))
	if err != nil {
		return nil, fmt.Errorf("Request construction failed: %w", err)
	}

	req.Header.Set("Content-Type", "application/json")
	resp, err := c.client.Do(req)
	if err != nil {
		return nil, fmt.Errorf("POST %s failed: %w", req.URL, err)
	}

	defer webutil.Discard(resp)
	if resp.StatusCode != http.StatusOK {
		b, _ := ioutil.ReadAll(resp.Body)
		return nil, fmt.Errorf("POST %s returned %v %v", req.URL, resp.StatusCode, string(b))
	}

	var otmResp OneToManyQueryScoreResponse
	if err := json.NewDecoder(resp.Body).Decode(&otmResp); err != nil {
		return nil, fmt.Errorf("failed to parse response for POST %s: %w", req.URL, err)
	}

	return &otmResp, nil
}

```

Any advice for what may be going on here?

### Versions

Versions of relevant libraries:
[pip3] mypy==0.942
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.21.2
[pip3] torch==1.10.0
[pip3] torchserve==0.5.3
[pip3] torchvision==0.11.1