sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: CAdvisor stats collection should be configurable.
Labels: sig/node,kind/feature,triage/accepted

### What would you like to be added?

Found this https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/cadvisor/cadvisor_linux.go#L53 while looking at the cadvisor code.
```
// TODO(vmarmol): Make configurable.
// The amount of time for which to keep stats in memory.
const statsCacheDuration = 2 * time.Minute
const maxHousekeepingInterval = 15 * time.Second
const defaultHousekeepingInterval = 10 * time.Second
const allowDynamicHousekeeping = true
```

These stats should be configurable in KubeletConfig. 

We should keep the defaults set if the user does not specify them in the KubeletConfig. 

### Why is this needed?

It would be nice to change these during e2e tests and I also think users would like the ability to change this.
Repository: node
Issue: Support remote sourceMap
Labels: feature request,source maps

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

In some size-sensitive cases, we want to compress the output to ship smaller packages, we also want to keep useful stack traces for bug reports. Therefore I hope Node.js can resolve remote sourceMap files.

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

Resolve sourceMap at a remote URL. Here is an example (that it does not work today):

```js
// a.js
import { __addDisposableResource, __disposeResources } from "tslib";
throw new Error();
var x;
const env_1 = { stack: [], error: void 0, hasError: false };
try {
    x = __addDisposableResource(env_1, undefined, false);
}
catch (e_1) {
    env_1.error = e_1;
    env_1.hasError = true;
}
finally {
    __disposeResources(env_1);
}
//# sourceMappingURL=http://127.0.0.1:8080/a.js.map
```

```json
// http://127.0.0.1:8080/a.js.map
{"version":3,"file":"a.js","sourceRoot":"","sources":["a.ts"],"names":[],"mappings":";AAAA,MAAM,IAAI,KAAK,EAAE,CAAA;;;;IACX,mCAAI,SAAS,QAAA,CAAA","sourcesContent":["throw new Error()\nusing x = undefined\nexport {}\n\n"]}
```

Run `node --enable-source-maps ./a.js` does not use the sourcemap.

### What alternatives have you considered?

_No response_
Repository: pytorch
Issue: Use sys.settrace or torch function mode to compute how much of a model was not covered by Dynamo
Labels: module: logging,triaged,oncall: pt2

### 🐛 Describe the bug

Suppose you have a model with a bunch of graph breaks / WON'T CONVERT. How much of the model have you managed to capture versus not capture?  There are two metrics you could use to figure this out:

* When you run the model in eager mode, it will have run some number calls to torch functions. You can count how many of these calls occur outside of Dynamo compiled regions, compared to those captured in Dynamo regions. This gives you "missing torch function call captures / total number of torch function calls in torch.compile region"
* When you run the model in eager mode, you will run some number of bytecodes. You can use sys.settrace to count how many bytecodes are processed in the eager region, and get "number of bytecodes evaluated outside of Dynamo region / total number of bytecodes"

This can give you a much better idea of how much of the model you've managed to capture, as opposed to just number of graph breaks.

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @zou3519
Repository: pytorch
Issue: PGO-style mode automatic dynamic shapes
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

It's annoying that if you have a model with some dynamism and you're using automatic dynamic shapes, you have to useless compile a static config first, before you discover the real dynamic.

You can workaround this by manually annotating inputs as dynamic or not.

However, if you have some sort of PGO style setup, where you have profiles from previous runs, you can bypass the recompile and the manual annotation, and just use the profile from the previous run to immediately go straight to being dynamic.

We need some sort of PGO setup as a prerequisite. It is probably not worth setting it up for only this. But if we have it, this is a very easy thing to use it for.

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @zou3519
Repository: ant-design
Issue: RangePicker (w/ presets) placement should support "center"
Labels: Inactive,improvement

### Reproduction link

https://stackblitz.com/edit/react-mkvzhx?file=demo.tsx

### Steps to reproduce

1. Add a range picker somewhere in the middle of the screen in your app.
2. Add `presets` to the RangePicker
2. Open the range picker on a smaller screen size

### What is expected?

If no value set for `placement` prop, component should figure out how to best position itself.

<img width="859" alt="image" src="https://github.com/ant-design/ant-design/assets/14989804/72420170-657f-4563-b73b-e27312eaa90d">


### What is actually happening?

<img width="856" alt="image" src="https://github.com/ant-design/ant-design/assets/14989804/a42359c6-7214-48f9-b0b4-4b72cbe75da0">


The component is getting positioned either on the left or right side. This does not work when the component is positioned near the middle of the screen, as there isn't enough space on either side.

There should either be a `center` option for placement, or that when the component realizes that there isn't enough space on the right or left side, it just would position itself in the center.

| Environment | Info |
| --- | --- |
| antd | 5.14.1 |
| React | 18.2.0 |
| System | Mac Sonoma |
| Browser | Chrome 120 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: tauri
Issue: [bug] Windows uninstaller unable to terminate running app
Labels: type: bug,status: needs triage

### Describe the bug

When running the uninstaller (generated by Tauri's default WIX template) while the app is still running, instead of simply terminating it and executing the uninstall cleanly, I get the attached error message.

![image](https://github.com/tauri-apps/tauri/assets/55365828/79e3bf2d-2e57-468a-b86c-515e19c9aaa9)

After selecting OK, the app is uninstalled (all files are removed) but after taking a look at the Task Manager, an instance of the app continues to run in the background.

If I reinstall the app, I can't run it (as I'm enforcing single instance) until I manually terminate the process via the Task Manager.

### Reproduction

**This error can be reproduced even on the** [tauri/examples/api](https://github.com/tauri-apps/tauri/tree/dev/examples/api) example app.
1. Build Tauri Windows app using Tauri's WIX template.
2. Install application used the generated installer.
3. Run the installed application.
4. While the application is still running, run the app's uninstaller.
5. Continue with uninstall.
6. After uninstall is "complete", go to Task Manager and see an instance of the app continuing to run on the background.

### Expected behavior

The uninstaller should be able to terminate the app's running process before uninstalling the app. After the uninstall is complete, no instance of the app should be left running in the background.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 121.0.2277.112
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: 1.75.0-x86_64-pc-windows-msvc (overridden by 'C:\Users\MyUser\Desktop\my-app\rust-toolchain.toml')
    - node: 18.18.2
    - npm: 9.8.1

[-] Packages
    - tauri [RUST]: 1.5.3
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.5
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.9

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../build
    - devPath: http://localhost:3000/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

As an alternate solution, I tried modifying Tauri's WIX template ([main.wxs](https://github.com/tauri-apps/tauri/blob/1.x/tooling/bundler/src/bundle/windows/templates/main.wxs)) by adding a `CustomAction` that terminates the app and all related processes (via the `taskkill.exe /T /F /IM "MyApp.exe"` command) but no luck on that end either.
Repository: pytorch
Issue: undefined reference to `__atomic_exchange_1'
Labels: needs reproduction,module: build,triaged

The error occurred while compiling on the resc-v schema
make[2]: *** [caffe2/CMakeFiles/kernel_lambda_legacy_test.dir/build.make:101: bin/kernel_lambda_legacy_test] Error 1
make[1]: *** [CMakeFiles/Makefile2:4714: caffe2/CMakeFiles/kernel_lambda_legacy_test.dir/all] Error 2
/usr/bin/ld: /root/pytorch/build/lib/libtorch_cpu.so: undefined reference to `__atomic_exchange_1'

cc @malfet @seemethere
Repository: three.js
Issue: Frustum: IntersectsBox function can produce incorrect results
Labels: Bug

### Description

The Frustum.intersectsBox function can produce a false positive in some cases where a box outside the frustum is large enough and positioned such that it crosses multiple frustum planes and therefore is not marked as separated by a single plane. [This article](https://iquilezles.org/articles/frustumcorrect/) suggests that checking whether the planes of the box separate the shapes will provide a more consistent result (though still not perfect in all cases). In order to do that we'd likely need to store or compute the edge points of the frustum.

This is related to [3DTilesRendererJS](https://github.com/NASA-AMMOS/3DTilesRendererJS). We were using an OBB / Frustum intersect function based on the three.js AABB implementation and were seeing that a lot of tiles were visible despite being a large distance from the camera.

cc @WestLangley 

### Reproduction steps

Configure a box and frustum such that they produce the error case (See jsfiddle)

### Code

See jsfiddle.

### Live example

https://jsfiddle.net/89rtuaqp/2/

The box is colored red if it intersects the visualized camera frustum.

### Screenshots

<img width="310" alt="image" src="https://github.com/mrdoob/three.js/assets/734200/4f2b7138-0fdb-4ee7-8f8b-1ee22fd08297">


### Version

161

### Device

_No response_

### Browser

_No response_

### OS

_No response_
Repository: godot
Issue: Linux: Scene editor: Control: Releasing mouse primary button after Alt+drag for centered Control resize will not end resize operation
Labels: enhancement,platform:linuxbsd,topic:editor,topic:porting,topic:input

### Tested versions

- Reproducible in v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Ubuntu 22.04.3 LTS 22.04 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 860M (nvidia; 535.154.05) - Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 Threads)

### Issue description

Alt+drag is convenient to resize a Control centered around the initial center

However, on some linux desktops I cannot hold Alt *before* pressing the mouse primary button, as it would move the window.

As a result, I must hold Alt *after* pressing mouse button, which happens to work and will update Control rect to be centered even though I did it late, which is great.

However, after release the mouse button, I get stuck in the resize operation state. Even after releasing Alt, I'm still stuck, and it will cause me to lose my good centered rescale by rescaling in a non-centered matter.

The only way to confirm the resize while it's still centered is to click once more after mouse button release (preferably holding Alt in case you accidentally move the mouse by a few pixels). And you may move the mouse a little while trying that.

https://github.com/godotengine/godot/assets/1067772/cb0eddd0-e18f-4938-b4ed-7b5f53e69291

It may or may not be related to the Linux desktop that's also responsible for window move on Alt+mouse drag.

The solution I found was to press Alt before the click, but to avoid moving window I also combined it with Meta/Super key, following this thread: https://askubuntu.com/questions/521423/how-can-i-disable-altclick-window-dragging

The workaround process is so:
- hold Meta+Alt
- with mouse primary button, drag the Control to center-resize
- release mouse primary button
- release Meta+Alt (in fact, you can even release Meta as soon as you starting dragging)

### Steps to reproduce

1. Create a Control
2. Hold Alt then Drag -> on some desktops, window will move
3. Drag then hold Alt while still dragging -> centered resize starts
4. Release mouse primary button
5. Move around: stuck in centered resize
6. Release Alt
7. Move around: stuck in normal resize
8. Click -> resize finally ends

### Minimal reproduction project (MRP)

N/A
Repository: pytorch
Issue: Collate function in libtorch c++ API
Labels: module: cpp,module: dataloader,triaged,enhancement

### 🚀 The feature, motivation and pitch

The c++ API, seems to be lacking the collate_fn capability that is available in pytorch. I was wondering if this can be added to the "dataloader_options.h". 
Thanks. 

### Alternatives

_No response_

### Additional context

_No response_

cc @jbschlosser @SsnL @VitalyFedyunin @ejguan @dzhulgakov
Repository: transformers
Issue: Swapping `tqdm` to `rich`
Labels: Feature request

### Feature request

Hi, for `AutoTokenizer.train_new_from_iterator` there's a hardcoded `tqdm` progress bar I want to swap to `rich` and I'm happy to PR it back.

I can see on github it's at `transformers/src/transformers/tokenization_utils_fast.py` and I can see in lines #790 and #791 that there's a further method `train_from_iterator` but at this point I can't find where the actual code is? Can anyone point me to the right direction?

Also, is there any reason to go against adding `rich` as a dependency?
Where are the `tqdm` specific bits of code, so I can go through them?
Thanks!

### Motivation

I'm not fond of `tqdm` it seems to create issues when used on AWS, SageMaker, etc. It's span is large and doesn't contain nearly enough information as `rich` can. I wanna start by going over `AutoTokenizer` because it's where I first spotted it.

### Your contribution

Slowly work through bits of code which rely on `tqdm` and add the option to swap for `rich` instead.
Repository: PowerToys
Issue: Mouse appearing on second screen in Issue #26338 still occurs after waking up laptop from sleep
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.78.0

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Use mouse without borders as usual.
Put the host laptop to sleep and let the secondary laptop keep running.
Wake up the host machine after a period of time.
I then encounter issue #26338 

### ✔️ Expected Behavior

Mouse should hide

### ❌ Actual Behavior

Mouse appears on the center top of the other screen

### Other Software

_No response_
Repository: PowerToys
Issue: [Mouse without borders] Make "Block screen saver on other machines" also prevent screen turn off on other machines.
Labels: Needs-Triage

### Description of the new feature / enhancement

Currently the "Block screen saver on other machines" prevents the screen from going to sleep. 
But if the screen is set to go to go off in the power settings after a period of time, It causes the screen to flash black for a second (When it's turning off ) before turning on again.


### Scenario when this would be used?

I think that this is a complementary feature to the "block screen saver on other machines" feature.

### Supporting information

_No response_
Repository: go
Issue: fmt: inconsistent pointer formatting with b/d/o/x/X verbs
Labels: NeedsInvestigation

### Go version

Playground Go 1.22

### Output of `go env` in your module/workspace:

```shell
Playground 1.22 go env
```


### What did you do?

https://go.dev/play/p/ivQo1wTK4NM

### What did you see happen?

0xc000014070
&{%!b(string=baz)}
&{%!d(string=baz)}
&{%!o(string=baz)}
&{62617a}
&{62617A}


### What did you expect to see?

https://pkg.go.dev/fmt#hdr-Printing for go1.22.0 states:

> The %b, %d, %o, %x and %X verbs also work with pointers,
formatting the value exactly as if it were an integer.

Either the documentation should be fixed or the behavior of fmt.
Repository: deno
Issue: Show no-slow-types diagnostics in the LSP
Labels: feat,lsp

A little complicated because it requires having a ModuleGraph, but we should look into a way to show no-slow-types diagnostics in the LSP w/ quick fixes for JSR.
Repository: go
Issue: x/tools/gopls: consider multiplexing navigation across all Views (with partial results?)
Labels: gopls,Tools,gopls/metadata

This is a follow up issue to #29202 and #57979.

In those issues we added dynamic support for working on multiple modules or GOOS/GOARCH combinations simultaneously. While this may simplify workspace configuration, it does mean that certain navigation queries may be confusing, because most operations in gopls still pick exactly one build from which to execute.

The simplest example of this is cross-references requests: if the user is in a file, and finds references to e.g. `fmt.Sprintf`, that references query will only return results _for the default build of that file_. This can be confusing if e.g. finding references to a standard library symbol from `foo.go` returns different results than finding references from e.g. `foo_windows.go`.

I was intentionally trying to tread carefully with respect to the performance implications of tracking multiple builds: we don't want to do twice the work when a user may typically be working on one build at a time.  For example, consider the case of a symbol in the shared package graph of the default build and a `GOOS=windows` build. In the common case, the set of references will be identical across both builds, and so doing twice the work is not desirable. Additionally, for the case of multiple-modules, this problem can usually be mitigated by adding a `go.work` file, if desired.

However, this is very liable to be confusing. It would be relatively straightforward to multiplex queries across all builds containing a file, and merge the results.  We should consider doing so, based on feedback. Perhaps there's something else we can do to solve this problem -- I wish the user had the ability to differentiate "fast references" from "all possible references".

One solution may be to use the partial results support that most of these operations include. We can return an initial set of results once we've processed the default build, and proceed with additional builds. However, this would the first time we've done something like this, so it requires careful testing across LSP clients.

References is one operation illustrating the problem. The same applies to definition, implementations, call hierarchy, etc. -- anything related to navigation.  I think this is less important for things like hover, signatureHelp, or completion.

CC @adonovan
Repository: go
Issue: x/tools/gopls: consider static configuration for multiple builds
Labels: gopls,Tools

This is a follow up to #29202. In that issue, we added dynamic support for tracking multiple GOOS/GOARCH combinations, based on the set of open files. (e.g. if you open `foo_windows.go`, gopls will create a new View with `GOOS=windows`).

In some cases, it may be desirable for users to explicitly configure these builds, for example if they know a priori that they are targeting several ports, or sets of build tags. We should consider supporting this, for example via configuration like so:

```
"builds": [{
  "env": ["GOOS=windows", "GOWORK=off"],
  "flags": ["-tags", "example"]
}, {
  // another build...
}]
```
Repository: go
Issue: x/tools/gopls: investigate better support for CGO_ENABLED=0
Labels: gopls,Tools

This is a speculative issue: we may be able to improve support for working with `CGO_ENABLED=0` (or `GOOS=...`, as is set automatically by the solution to #29202).

For example, we could investigate using https://pkg.go.dev/go/types#Config.FakeImportC. I don't yet know if this is feasible, but it could make gopls more usable in scenarios where a c toolchain is unavailable, or prohibitively slow.
Repository: flutter
Issue: Framework FTL failures not turning the tree red
Labels: team-infra,P2,triaged-infra

https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20firebase_android_embedding_v2_smoke_test/17576/overview
Repository: material-ui
Issue: [docs-infra] Prevent to set `undefined` as a default value
Labels: enhancement,scope: docs-infra

> Why not?

```suggestion
  /**
   * The height of the chart in px. If not defined, it takes the height of the parent element.
   */
  height: PropTypes.number,
```

It looks funny on the API page:

<img width="761" alt="SCR-20240215-oysy" src="https://github.com/mui/mui-x/assets/3165635/523ec24e-bee5-4be4-9328-a9151936c5bb">

As far as I know, we only do this if it's `null`. `undefined` is the default "prop default value". In https://github.com/mui/material-ui/pull/41114 I try to improve its display.

If this change makes sense, then I think we should throw an error in docs-infra when the default is undefined, saying to remove it as redundant, to prevent future regressions.

_Originally posted by @oliviertassinari in https://github.com/mui/mui-x/pull/11996#discussion_r1491248717_
            
**Search keywords**:
Repository: react
Issue: Bug: `textarea` inputs in Safari stop accepting input on certain empty lines
Labels: Status: Unconfirmed

This is a strange one that I honestly couldn't believe wasn't caused by our app, but it turns out I can reproduce it in a minimal fresh React app as well: if you have a `<textarea>` input and you select and delete any line other than the first, second, or last, you cannot type in that input anymore until you leave and refocus it. This is only reproducible in Safari.

React version: 18.2.0
Safari version: 17.3
MacOS version: Sonoma 14.3

## Steps To Reproduce

1. Render a `<textarea>` with four or more lines of initial content
2. Select a line other than the first, second, or last
3. Delete that line by pressing <kbd>Delete</kbd> 
4. Attempt to keep typing

**Link to code example**: https://github.com/iansan5653/textarea-safari-bug

Screen recording of the bug (based on running the linked repo):

https://github.com/facebook/react/assets/2294248/12cc3ece-5f0d-4856-8420-a080fa2d569f



## The current behavior

Upon deleting the line, the line cannot be typed into anymore. Moving the caret to another line allows typing, but moving it back to the deleted line does not. Sometimes an errant character appears in the deleted line. Blurring (moving focus away from) the input and refocusing it makes the whole input interactive again, but does not restore lost input.

## The expected behavior

The input should remain full interactive as normal.

## More details

- Happens with controlled or uncontrolled inputs
- Does not reproduce in Chrome or Firefox
- Does not reproduce if you select the line and just start typing - you must delete the content first
- Does not seem to reproduce if the input starts out at less than four lines and then more lines are typed