sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: Mixing Keras Layers and TF modules.
Labels: type:support,comp:keras,2.17

### Issue type

Support

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.17

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 22.04

### Mobile device

_No response_

### Python version

3.12

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

tf.Module can trace tf.Variable but it cannot trace variables from tf.keras or tf.keras.Variable. 

### Standalone code to reproduce the issue

```shell
class MockLayer(tf.Module):

    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.m = tf.keras.Variable(tf.random.normal([5, 5]), name="m")
        self.w = tf.keras.Variable(tf.random.normal([5, 5]), name="w")

    def __call__(self, inputs):
        return self.m * inputs

layer1 = MockLayer()
print([v.name for v in layer1.trainable_variables])
```

is empty.

```
class MockLayer(tf.Module):

    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.m = tf.Variable(tf.random.normal([5, 5]), name="m")
        self.w = tf.Variable(tf.random.normal([5, 5]), name="w")

    def __call__(self, inputs):
        return self.m * inputs

layer1 = MockLayer()
print([v.name for v in layer1.trainable_variables])
```

Works.

Specifically I am more interested in keras layers like 

```

class MockLayer(tf.Module):

    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.norm = tf.keras.layers.LayerNormalization(*args, **kwargs)

    def __call__(self, inputs):
        return self.norm(inputs)
```

For which tracing does not appear to work. 

I am interested in trying https://github.com/google/sequence-layers but they seem mostly broken on this TF version and python version due to the tracing issues. 

I am curious to try fixing it, but not sure what's a supported path. Using keras layers in tf.Module does not work due to tracing issues.. and using Keras layers only does not work because Keras is missing many features like composite tensors. 

Is there a way around this? :)
```


### Relevant log output

_No response_
Repository: ollama
Issue: Allow use of locally installed CUDA or ROCm
Labels: feature request

Ollama tries to install its own copy of CUDA or ROCm, even when the same version is already installed as a system-wide installation
Repository: vscode
Issue: When trying to open a 300MB log file the VCD Crashes
Labels: freeze-slow-crash-leak

<!-- Failed to upload "fake_log.log" -->
<!-- Failed to upload "300MB_log.log" -->

Type: <b>Bug</b>

When trying to open a 300MB log file the VCD Crashes 

The window terminated unexpectedly (reason "crashed", code:'132')

With a log file of 50MB it doesnt crash.

VS Code version: Code 1.96.2 (..., 2024-12-19T10:22:47.216Z)
OS version: Linux x64 6.8.0-49-generic
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz (16 x 1093)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off<br>webnn: disabled_off|
|Load (avg)|4, 5, 4|
|Memory (System)|62.53GB (43.42GB free)|
|Process Argv|--crash-reporter-id f48e985a-bee3-49a4-8365-e242b141d0c3|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|ubuntu|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu|
|XDG_SESSION_TYPE|x11|
</details><details><summary>Extensions (27)</summary>

Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.5.0
gitlens|eam|16.0.0
copilot|Git|1.245.0
copilot-chat|Git|0.22.2
vscode-github-actions|git|0.27.0
debugpy|ms-|2024.10.0
python|ms-|2024.20.0
vscode-pylance|ms-|2024.9.1
remote-containers|ms-|0.388.0
remote-ssh|ms-|0.116.0
remote-ssh-edit|ms-|0.87.0
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.11
cpptools-extension-pack|ms-|1.3.0
makefile-tools|ms-|0.11.13
remote-explorer|ms-|0.4.3
java|red|1.37.0
code-spell-checker|str|3.0.1
cmake|twx|0.0.17
intellicode-api-usage-examples|Vis|0.2.9
vscodeintellicode|Vis|1.3.2
vscode-gradle|vsc|3.16.4
vscode-java-debug|vsc|0.58.1
vscode-java-dependency|vsc|0.24.1
vscode-java-pack|vsc|0.29.0
vscode-java-test|vsc|0.43.0
vscode-maven|vsc|0.44.0

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

```

</details>

<!-- generated by issue reporter --><!-- Failed to upload "fake_log.log" -->

First time [the bug has been reported for 1.96.1](https://github.com/microsoft/vscode/issues/236568).
Repository: go
Issue: net: TestDialListenerAddr failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestDialListenerAddr"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8726880560451781425)):

    === RUN   TestDialListenerAddr
        dial_test.go:964: listening on "127.0.0.1:64007"
        dial_test.go:982: Dial("tcp4", "[::]:64007"): dial tcp4 0.0.0.0:64007: connect: connection refused
    --- FAIL: TestDialListenerAddr (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: proposal: log/slog: native support for handling List
Labels: Proposal

### Proposal Details

The current implementation of `log/slog` does not fully support logging arrays or slices. As a result, the type implementing the `slog.Valuer` interface is not respected when passed as an element of an array or slice and the `Handler` cannot handle the elements within the input array or slice either.

One possible workaround is to create a custom `List` using a generic struct that implements the `slog.LogValuer` interface, returns a `Group` and uses the index as the key. An example of this approach can be found in this comment https://github.com/golang/go/issues/63204#issuecomment-2428962553

However, it would make more sense and be more practical if `List` were natively supported

```go
type listptr  *Value    // used in Value.any when the Value is a []Value

const (
	KindAny Kind = iota
	KindBool
	KindDuration
	KindFloat64
	KindInt64
	KindString
	KindTime
	KindUint64
	KindGroup
	KindLogValuer
        KindList 
)

// ListValue returns a [Value] for a slice of arbitrary values.
func ListValue(vs ...Value) Value {
	return Value{num: uint64(len(vs)), any: listptr(unsafe.SliceData(vs))}
}

// List returns v's value as a []Value.
// It panics if v's [Kind] is not [KindList].
func (v Value) List() []Value{
	if sp, ok := v.any.(listptr); ok {
		return unsafe.Slice((*Value)(sp), v.num)
	}
	panic("List: bad kind")
}

func (v Value) list() []Value{
	return unsafe.Slice((*Value)(v.any.(listptr)), v.num)
}
```
Repository: vscode
Issue: Make the activity icons toggleable when on top (and bottom)
Labels: feature-request,workbench-views

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Hi there :)

I like to enable and disable a certain view, when I click on its icon. 

That is already possible when the icon of said activity is on the side with the default setting. 

The top/setting seems to not have that. 

https://github.com/user-attachments/assets/04aebe11-e7da-4f85-b8c7-74250f94e280
Repository: storybook
Issue: [Tracking] Typesafe CSF factories
Labels: feature request,csf,Tracking

Tracking issue to implement the following RFC:: 
https://github.com/storybookjs/storybook/discussions/30112

```[tasklist]
### Create a POC where all pieces are working together (by week 2)
- [x] API
- [x] Basic type safety for React
- [x] Runtime
- [x] AST
- [ ] https://github.com/storybookjs/storybook/issues/30169
- [ ] https://github.com/storybookjs/storybook/issues/30173
- [ ] https://github.com/storybookjs/storybook/issues/30175
- [x] Vitest
- [x] CLI templates only for sandboxes + minimal codemod
- [x] Basic codemod
- [ ] https://github.com/storybookjs/storybook/issues/30170
- [ ] https://github.com/storybookjs/storybook/issues/30244
- [ ] https://github.com/storybookjs/storybook/issues/30241
- [x] Test runner
- [x] QA
```

```[tasklist]
### Convert to releasable form (by week 5)
- [ ] https://github.com/storybookjs/storybook/issues/30243
- [ ] https://github.com/storybookjs/storybook/issues/30239
- [ ] https://github.com/storybookjs/storybook/issues/30240
- [ ] https://github.com/storybookjs/storybook/issues/30316
- [ ] https://github.com/storybookjs/storybook/issues/30357
- [ ] https://github.com/storybookjs/storybook/issues/30242
- [ ] https://github.com/storybookjs/storybook/issues/30235
- [ ] https://github.com/storybookjs/storybook/issues/30236
- [ ] https://github.com/storybookjs/storybook/issues/30237
- [ ] https://github.com/storybookjs/storybook/issues/30238
- [ ] Transform args, parameters and play into root properties as getters + deprecation message to use .input instead
- [x] use csf-2-to-3 codemod as part of csf-factories codemod
```

```[tasklist]
### Docs
- [ ] https://github.com/storybookjs/storybook/issues/30329
- [ ] https://github.com/storybookjs/storybook/issues/30342
- [ ] https://github.com/storybookjs/storybook/issues/30383
```

```[tasklist]
### Nice to have milestone
- [ ] Implement Jeppe's proposal to get rid of essentials
- [ ] Implement other renderers
- [ ] Refactor ESLint to use csf-tools and implement CSF factory features
- [ ] Shrink the react docs entrypoint
- [ ] Advanced type safety
- [ ] Third party Addons
- [ ] Write new story file with CSF factory in "Add new component" feature if preview file uses csf factory
```
Repository: godot
Issue: You can only copy a scene path once.
Labels: bug,topic:editor

### Tested versions

v4.4.dev7.official [46c8f8c5c]
v3.6.stable.official [de2f0f147]

### System information

win11

### Issue description

You cannot copy a scene path again using the shortcut CTRL + SHIFT + C if you copy any other text immediately after.
To copy the scene path again, deselect the scene (in the "File System" dock) and select it again, then you can copy the scene path using the shortcut.


### Steps to reproduce

1. Select a scene in the "File System" dock.
2. Copy its path using the shortcut CTRL + SHIFT + C.
3. Paste the text and verify that the path was copied.
4. Copy any other text, such as the name of a node. The scene from which you copied the path remains selected.
5. Go back to the scene that remains selected in the "File System" (Click on the scene, although it will remain selected) dock and try copying its path again using CTRL + SHIFT + C.
6. Paste the copied path and you will see that it was not copied.

### Minimal reproduction project (MRP)

...
Repository: kubernetes
Issue: can MountPath contain  ":" ?
Labels: kind/bug,priority/backlog,sig/storage,sig/node,sig/windows,triage/accepted

### What happened?

https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/core/types.go#L2110-L2113
```
	RecursiveReadOnly *RecursiveReadOnlyMode
	// Required. If the path is not an absolute path (e.g. some/path) it
	// will be prepended with the appropriate root prefix for the operating
	// system.  On Linux this is '/', on Windows this is 'C:\'.
	MountPath string
```
but
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/api/core/v1/types.go#L2283
```
	// Path within the container at which the volume should be mounted.  Must
	// not contain ':'.
	MountPath string `json:"mountPath" protobuf:"bytes,3,opt,name=mountPath"`
```
some people use mountpath:/etc/localtime:ro (k8s should use readonly:true)  will not work on containerd but work on docker.

### What did you expect to happen?

mountPath  can't contain  ":" 

### How can we reproduce it (as minimally and precisely as possible)?

set mountpath:/etc/localtime:ro 

### Anything else we need to know?

_No response_

### Kubernetes version

any

### Cloud provider

no 

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: go
Issue: net: TestDialLocal failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestDialLocal"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8726880560451781425)):

    === RUN   TestDialLocal
        dial_test.go:71: dial tcp :64041: connect: connection refused
    --- FAIL: TestDialLocal (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ollama
Issue: Enable auto-save functionality via CLI flag
Labels: feature request

Having ollama models keep track of past conversations improves the quality of answers dramatically. Using `/save <model>` manually with every run is time-consuming, and prone to be forgotten. Allowing a flag similar to `ollama run --auto-save-on-exit <model>` would make this process a lot smoother. The solutions proposed on https://github.com/ollama/ollama/issues/1238 and https://github.com/ollama/ollama/issues/3800 are not sufficient to satisfy this feature request.

Thank you for the hard work already done 🙏
Repository: flutter
Issue: Separate properties for the selected day of the DatePicker
Labels: c: new feature,framework,f: material design,f: date/time picker,c: proposal,P3,team-design,triaged-design

### Use case

Currently the Flutter engine uses the `dayOverlayColor` to assign color to the selected day button. This is not intuitive and also limits the customization of the Date Picker, since the `dayOverlayColor` and `dayBackgroundColor` must be similar, since there is no way to select the color of the text of the selected day.

Imagine the following: I'm using a white background for all dates and a blue text color.

```dart
dayBackgroundColor: Colors.white,
dayForegroundColor: Colors.blue,
```

If I set the `dayOverlayColor` to `Colors.blue`, when the user selects a date, I'd have a round blue button with, what would appear to be, no text.

### Proposal

I propose that we add the following properties:

`selectedBackgroundColor` and `selectedForegroundColor`

where both properties, similar to the ones we have today, control, respectively, the background and foreground colors of the button. 

or

`selectedDayTheme`

where we could have a `ButtonStyle` to assign the colors.

I also propose that we standardize the other properties to be like the `confirmButtonStyle`, making it intuitive for the user to customize the dialog.

PS: the same thing should be done to the year buttons as well.
Repository: node
Issue: Native addon use ThreadsafeFunction in multithreads env casue EXC_BAD_ACCESS in worker_threads in Node 18
Labels: node-api

### Version

v18.20.5

The Node 20, Node 22 works fine

### What steps will reproduce the bug?

The minimal reproduce example is very difficult to construct; if anyone is interested, they can check how to reproduce in the Rust project:

1. Clone `https://github.com/napi-rs/napi-rs`
2. Checkout to `12-23-feat_napi_impl_readablestream_and_asyncgenerator` branch
3. Install latest stable Rust, it's `1.83.0` at this moment
4. `corepack enable`
5. `yarn install`
6. `yarn workspace @examples/napi build`


- if you want to run test directly `yarn workspace @examples/napi test __tests__/stream.spec.ts`
- if you want to run `lldb`
  - `cd examples/napi`
  - `lldb node`
  - `run --loader ts-node/esm/transpile-only ../../node_modules/ava/entrypoints/cli.mjs __tests__/stream.spec.ts`

lldb log:
```
lldb) bt
* thread #13, stop reason = EXC_BAD_ACCESS (code=1, address=0x10)
  * frame #0: 0x00000001000803dc node`napi_env__::DeleteMe() + 52
    frame #1: 0x000000010008373c node`v8impl::(anonymous namespace)::ThreadSafeFunction::~ThreadSafeFunction() + 84
    frame #2: 0x0000000100083784 node`v8impl::(anonymous namespace)::ThreadSafeFunction::~ThreadSafeFunction() + 12
    frame #3: 0x0000000100083980 node`void node::Environment::CloseHandle<uv_handle_s, v8impl::(anonymous namespace)::ThreadSafeFunction::CloseHandlesAndMaybeDelete(bool)::'lambda'(uv_handle_s*)>(uv_handle_s*, v8impl::(anonymous namespace)::ThreadSafeFunction::CloseHandlesAndMaybeDelete(bool)::'lambda'(uv_handle_s*))::'lambda'(uv_handle_s*)::__invoke(uv_handle_s*) + 240
    frame #4: 0x000000010244a280 libuv.1.dylib`uv_run + 520
    frame #5: 0x000000010005f58c node`node::Environment::CleanupHandles() + 252
    frame #6: 0x000000010005fbb8 node`node::Environment::RunCleanup() + 372
    frame #7: 0x000000010000beb0 node`node::FreeEnvironment(node::Environment*) + 120
    frame #8: 0x000000010014371c node`node::OnScopeLeaveImpl<node::worker::Worker::Run()::$_0>::~OnScopeLeaveImpl() + 112
    frame #9: 0x0000000100143390 node`node::worker::Worker::Run() + 1408
    frame #10: 0x0000000100145b60 node`node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_0::__invoke(void*) + 56
    frame #11: 0x000000018afe02e4 libsystem_pthread.dylib`_pthread_start + 136
```

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

Very easy to reproduce.

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

Process exit with normal exit code

### What do you see instead?

After some bisects, I found the latest properly Node 18 is `18.18.2`, in the [v18.18.2..v18.19.0 diff](https://github.com/nodejs/node/compare/v18.18.2..v18.19.0), I think this PR is most likely to cause this issue https://github.com/nodejs/node/pull/42651.



### Additional information

_No response_
Repository: go
Issue: net: TestDialWithNonZeroDeadline failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestDialWithNonZeroDeadline"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8726880560451781425)):

    === RUN   TestDialWithNonZeroDeadline
        dial_test.go:1106: dial tcp :63997: connect: connection refused
    --- FAIL: TestDialWithNonZeroDeadline (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: TypeScript
Issue: Import path autocomplete regression: No classic resolution autocomplete when package does not have any "exports" but resolves fine
Labels: Bug,Help Wanted

### 🔎 Search Terms

"resolvePackageJsonExports", "no file autocomplete when importing internal package files with moduleResolution node16"

### 🕗 Version & Regression Information

This changed between versions [5.7.0-dev.20241031](https://www.npmjs.com/package/typescript/v/5.7.0-dev.20241031) and [5.7.0-dev.20241101](https://www.npmjs.com/package/typescript/v/5.7.0-dev.20241101)

Confirmed the issue exists on `typescript@next`

### ⏯ Playground Link

https://codesandbox.io/p/devbox/qpxkh5?file=%2Findex.ts%3A13%2C1

### 💻 Code

```ts

// This resolves correctly but it doesn't autocomplete the /internal path even
// though the package @my/base (inside the folder base-package) does NOT have "exports" inside the package.json
import { INTERNAL_CONSTANT } from "@my/base/internal";

// try to update the import below to include the "/internal" at the end and see that it does not autocomplete

import { INTERNAL_CONSTANT as INTERNAL_CONSTANT2 } from "@my/base";

// try to set resolvePackageJsonExports to false inside tsconfig.json and try to update the import above again. 
// Autocomplete works AS EXPECTED.

```

### 🙁 Actual behavior

Autocomplete of internal folders of packages without "exports" does not work when `"resolvePackageJsonExports": true`

### 🙂 Expected behavior

Autocomplete of internal folders of packages without "exports" inside the package.json should be the same whether the `resolvePackageJsonExports` flag is enabled or not

### Additional information about the issue

Regression must have happened between 2024/10/31 and 2024/11/1 based on my testing of the nightly builds. Could not provide a non-VM sandbox of the issue because it requires 2 npm packages to show the issue ( monorepo style )
Repository: svelte
Issue: Suggestions to Improve Clarity in the Example of Passing State into Functions
Labels: documentation

Hi there! I found the example of passing state into functions a bit complicated and unclear. It might help to simplify the explanation or break it down into smaller steps. I'd really appreciate it!

now:
https://svelte.dev/docs/svelte/$state#Passing-state-into-functions
```ts
function add(getA: () => number, getB: () => number) {
	return () => getA() + getB();
}

let a = 1;
let b = 2;
let total = add(() => a, () => b);
console.log(total()); // 3

a = 3;
b = 4;
console.log(total()); // 7
```

suggested:
```ts
function add(a: number, b: number) {
return a + b;
}

let a = 1;
let b = 2;

function total() {
return add(a, b);
}

console.log(total()); // 3

a = 3;
b = 4;

console.log(total()); // 7
```

or even :

```ts
<script lang="ts">
	const add = (a: number, b: number) => a + b;

	let a = 1;
	let b = 2;

	const total = () => add(a, b);

	console.log(total()); // 3

	a = 3;
	b = 4;

	console.log(total()); // 7
</script>
```


For the 3 versions i see the same result !
Repository: rust
Issue: Tracking Issue for amdgpu target
Labels: A-LLVM,T-compiler,C-tracking-issue,O-amdgpu

This issue tracks the implementation of the amdgpu target.

- [x] MCP: https://github.com/rust-lang/compiler-team/issues/823

Old, closed tracking issue: #51575

Current work-in-progress branch: https://github.com/Flakebi/rust/tree/amdgpu

### Implementation

- [ ] Add amdgpu target: #134740
- [x] Disable `f128` in `compiler-builtins`: https://github.com/rust-lang/compiler-builtins/pull/737
- [ ] Cast `alloca`s to default address space: #135025
- [ ] Cast global vars to default address space: #135026
- [ ] Add triple to `cc` crate (once target is in nightly)
- [ ] Add test compiling `core` and `alloc` (depends on `cc` crate)
- [x] Add `gpu-kernel` calling convention:  #135047
- [ ] Export `<kernel>.kd` kernel descriptor symbol: #135909
- [ ] Require explicit `-C target-cpu=`: #135030
- [ ] Fix requiring lto automatically
- [x] Remove range-metadata amdgpu workaround: #135027

### Bugs

- Debug compilation fails due to a bug in LLVM’s `AMDGPUResourceUsageAnalysis`. This is fixed in llvm `main`, so will be fixed with the update to LLVM 20