sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Template literal type derived from string is not a subtype of the TLT derived from any
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

"template literal type", "any", "string", "mutually assignable types"

### 🕗 Version & Regression Information

- This changed between versions 4.1.5 and 4.2.3
- This changed in commit or PR 411c6d04c6007cd3bb74ef0ce6cc11e8c699a2b5 (reported by every-ts)


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=4.2.3#code/C4TwDgpgBA4g9nAJgRigXigAwCQG8B2ArgLYBGEATgL6ZQQAewE+iAzlngIb4g1QD8UYBULQAXFABmnADasIAbigB6ZUJEQAUKEiwEiAEzoOuUgEsA5mfzA+DJi3Y5c3XrUHDRUCdLmKVap5aOtDwSADMxs6kCDIQ3HaMzGwmrnweGt5SsvJKquqi2uCh+gAsUXhEMjKJDinOae4F4tl+eYEaRbphiACsFbiELBCS1hCItclOXDzpzVm+uQHNml3QAEKcKAOswtYWk46ps01BCzn++WfWUKUAdMh3vQA0rfJQN-cGd+FrUJuGHZ7fAWKAAHygRDIlHBUHMVhssJicDi3FhVRksKGiBGYwmtHsU2ObgE8x8F3a80+Dyer0W0Gp31+mgAxnB8LsoHAANYSBonYwAcmQgqgnGmBBI5GomAUmnyAHluR98LcaS8oGziGAZJxrOxGT9WezOWZWKxRHyZiSMMLReKTLsKPsaHKgA

### 💻 Code

```ts
type Good1 = `${number}` extends `${any}` ? true : false; // true
type Good2 = `${bigint}` extends `${any}` ? true : false; // true
type Good3 = `${boolean}` extends `${any}` ? true : false; // true
type Good4 = `${null}` extends `${any}` ? true : false; // true
type Good5 = `${undefined}` extends `${any}` ? true : false; // true

type Bad1 = `${string}` extends `${any}` ? true : false; // true in 4.1.5, false in 4.2.3
type Bad2 = `${string | number | bigint | boolean | null | undefined}` extends `${any}` ? true : false; // true in 4.1.5, false in 4.2.3

const ok: `${any}` = '1' as `${number}`;
// Ok in 4.1.5, complains in 4.2.3
const issue: `${any}` = '1' as `${string}`;
```

### 🙁 Actual behavior

Type 'string' is not assignable to type '`${any}`'.(2322)

### 🙂 Expected behavior

Should compile with no errors, since `` `${any}` `` and `string` should be the same type (or at least mutually assignable).

### Additional information about the issue

Proposed solution: simplify the type `` `${any}` `` to `string` like it is done with the `` `${string}` `` type.

Rationale: for any type `X` that is either concrete or generic (with a restriction to valid arguments of a template literal type) the type `` `${string|X}` `` simplifies to `string`. Therefore, if TypeScript strives to any consistency, we would expect `` `${string|any}` `` (i.e. `` `${any}` ``) to also simplify to `string`.

I have no idea why we currently have `` `${any}` extends `${number}` `` true (which could break with my suggestion if no other changes are made), but this bug report is not concerted with this. I'm leaving this up to the maintainers.

Proposed solution 2: Just make `` string extends `${any}` `` and  `` `${any}` extends string `` true.
Repository: material-ui
Issue: [Stepper] Lacks accessibility
Labels: accessibility,component: stepper,package: material-ui

### Summary

When navigating the [Stepper](https://mui.com/material-ui/react-stepper/#linear) component with voice assistant and keyboard-only navigation, it doesn't read out which step you're currently in when you go to the next step. It also doesn't hint the user how many steps there are in total.

### Examples

_No response_

### Motivation

_No response_

**Search keywords**: Stepper lacks accessibility
Repository: deno
Issue: `FileHandle` missing methods
Labels: bug,good first issue,node compat

FileHandle class (in `node:fs/promises`) still misses the below methods:

ref: https://nodejs.org/api/fs.html#class-filehandle

- [ ] Event: 'close'
- [ ] filehandle.appendFile(data[, options])
- [x] filehandle.chmod(mode) #27522 
- [ ] filehandle.chown(uid, gid) #27638
- [x] filehandle.close() https://github.com/denoland/deno/pull/19357
- [ ] filehandle.createReadStream([options]) #27591
- [ ] filehandle.createWriteStream([options])
- [ ] filehandle.datasync()
- [x] filehandle.fd
- [x] filehandle.read(buffer, offset, length, position) #19359
- [x] filehandle.read([options]) #19359
- [x] filehandle.read(buffer[, options]) #19359
- [ ] filehandle.readableWebStream(options)
- [x] filehandle.readFile(options)
- [ ] filehandle.readLines([options])
- [ ] filehandle.readv(buffers[, position])
- [x] filehandle.stat([options]) #26719
- [ ] filehandle.sync()
- [x] filehandle.truncate(len) #27389
- [x] filehandle.utimes(atime, mtime) #27582
- [x] filehandle.write(buffer, offset[, length[, position]]) #19385
- [x] filehandle.write(string[, position[, encoding]]) #19385
- [x] filehandle.writeFile(data, options) #25555
- [x] filehandle.writev(buffers[, position]) #27563

_Originally posted by @k-nasa in https://github.com/denoland/deno/issues/19165#issuecomment-1574509694_
Repository: electron
Issue: [Bug]: SaveDialog is not treating Package as File when setting defaultPath to a file that already exists
Labels: platform/macOS,bug :beetle:,has-repro-gist,stale,32-x-y

### 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 bug report that matches the one I want to file, without success.

### Electron Version

32.0.0

### What operating system(s) are you using?

macOS

### Operating System Version

macOS Sonoma 14.6.1

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

When using the saveDialog, if the path is set to an existing file (package) the the file should not be selectable and the "file already Existing" warning should appear instead.

### Actual Behavior

To test this - you can point the saveDialog defaultPath to any existing package file (i.e. xcodeproj)

`dialog.showSaveDialog({ 
  defaultPath: YOUR_PATH_TO_EXISTING_PACKAGE_FILE.xcodeproj, 
  properties: [], 
  filters: { name: 'directories', extensions: [] }, // to prevent file selection
  properties: ['showOverwriteConfirmation']
})`

You see that the dialog then selects the package (as if it was a directory) and shows its content.

Also if the extension is removed, then it also does not detect it as a duplicate file.

Any info or guidance to how to resolve is appreciated.

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: terminal
Issue: [Windows Terminal]: Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,In-PR,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11ySev2

### Windows Terminal version

1.22.2362.0

### Windows build number

27695.1000

### Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 27695.1000)
App: Windows Terminal Preview
Screen Reader: Narrator

### Steps to reproduce

**Repro steps :**
1.Open Windows Terminal.
2.Navigate to the editor.
3.Turn on Narrator by pressing 'Ctrl + Windows + Enter' keys.
4.Now turn on mark mode by pressing 'Ctrl + Shift + M' keys.
5. Now navigate among words using 'Ctrl + Left/Right' keys.
6.Observe the screen reader narration here.

**Observation using NVDA and JAWS screen reader:**
Same issue repro with NVDA and JAWS screen reader also.

**User Experience**
Users who rely on screen reader may not get the info properly while navigating in mark mode.
 
 **WCAG Reference Link:**
 https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships
 
**Attachment :**
[Screen reader is not announcing full word information while navigating via ctrl + left_right arrow keys.zip](https://github.com/user-attachments/files/16943981/Screen.reader.is.not.announcing.full.word.information.while.navigating.via.ctrl.%2B.left_right.arrow.keys.zip)


### Expected Behavior

Screen reader should narrate complete word information while navigating using ctrl + left/right arrow keys in mark mode.

### Actual Behavior

Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode.
For example:
For word "Microsoft", screen reader is just announcing as 'M selected' when we navigate using 'Ctrl + Left' arrow key and announces as 't selected' using 'Ctrl + Right' arrow.
Repository: TypeScript
Issue: Improve Iterator Helper Type Signatures
Labels: Needs Investigation

### ⚙ Compilation target

ESNext

### ⚙ Library

esnext.iterator.d.ts

### Missing / Incorrect Definition

- [x] `Iterator.from(value: Iterator)` - PR #59927
  - [x] ~`value` iterator argument with `TNext` other than `undefined` should be accepted;~ this is a bad idea; my mistake
  - [ ] Since `IteratorObject` instances (objects whose prototype is `Iterator.prototype`) are not wrapped by `Iterator.from`, we could add an `Iterator.from` overload to represent those cases and pass through all generic type parameters: `from<T, TReturn = any, TNext = any>(value: IteratorObject<T, TReturn, TNext>): IteratorObject<T, TReturn, TNext>;`
  - [x] `TReturn` type should be passed through from the argument to the return type
- [x] Iterator helper intermediate operators (`filter`, `map` etc) do not propagate the return value of their source iterator and should have `TReturn` set to `undefined`
  - [x] This is already the case in the current declarations
- [x] ~Iterator objects returned from `Iterator.from` and the other built-in iterators returned from `Array.values` etc always have a `return` method (built-in iterators returned from `Array.values` etc also always have a `throw` method)~ thanks to @bakkot for the clarification
  - [x] There is no way that I am aware of to express this behavior in TypeScript with the current definition of `IteratorObject` without also forcing user-defined classes extending from the javascript `Iterator` class to also implement the `return` method, which would be wrong. The impact on client code is minimal as the Iterator object's `return` method can always be called safely using the `return!()` notation.

### Sample Code

```TypeScript
https://github.com/nikolaybotev/iteratorhelpersdemo
```


### Documentation Link

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Iterator

and

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols
Repository: rust
Issue: Deadlock when capturing a backtrace from allocator during panic with test output capturing enabled
Labels: regression-from-stable-to-stable,C-bug,A-backtrace

I tried this code (minimized from a larger testcase):

```rust
use std::alloc::{GlobalAlloc, Layout};
use std::cell::Cell;
use std::backtrace::Backtrace;
use std::thread_local;

thread_local! {
    static CAN_ALLOCATE: Cell<bool> = const { Cell::new(true) };
}

#[derive(Debug)]
pub struct NoAllocate(std::alloc::System);

unsafe impl GlobalAlloc for NoAllocate {
    unsafe fn alloc(&self, layout: Layout) -> *mut u8 {
        if !CAN_ALLOCATE.replace(true) {
            let _ =  Backtrace::force_capture();
        }
        self.0.alloc(layout)
    }

    unsafe fn dealloc(&self, ptr: *mut u8, layout: Layout) {
        self.0.dealloc(ptr, layout);
    }
}

#[global_allocator]
static GLOBAL: NoAllocate = NoAllocate(std::alloc::System);

#[test]
#[should_panic]
fn main() {
    CAN_ALLOCATE.set(false);
    panic!();
}
```

Compiled with `rustc --test main.rs`.

I expected to see this happen: the test successfully panics and exits.

Instead, this happened: the test deadlocks.

Relevant section of backtrace:

```
...
#4  std::sync::mutex::Mutex::lock<()> () at std/src/sync/mutex.rs:317
#5  std::sys::backtrace::lock () at std/src/sys/backtrace.rs:18
#6  std::backtrace::Backtrace::create () at std/src/backtrace.rs:326
#7  0x0000555555585b25 in std::backtrace::Backtrace::force_capture () at std/src/backtrace.rs:312
#8  0x000055555556ab52 in <main::NoAllocate as core::alloc::global::GlobalAlloc>::alloc ()
#9  0x000055555556ac45 in __rust_alloc ()
...
#15 alloc::vec::Vec::reserve<u8, alloc::alloc::Global> () at alloc/src/vec/mod.rs:973
...
#22 0x00005555555879a3 in std::io::Write::write_fmt<alloc::vec::Vec<u8, alloc::alloc::Global>> () at std/src/io/mod.rs:1823
#23 0x000055555558aeb7 in std::panicking::default_hook::{closure#1} () at std/src/panicking.rs:256
```

This is specifically related to output capturing from the test runner, running the same code as a non-test binary or with `--nocapture` works perfectly.

### Meta

This worked in `1.80.1` and `nightly-2024-07-13`, it started failing in `1.81.0` and `nightly-2024-07-14`.

The deadlock was introduced by https://github.com/rust-lang/rust/pull/127397 (cc @jyn514).

The lock is first taken when starting to print from the default panic hook:

https://github.com/rust-lang/rust/blob/26b2b8d162ff6cc399c7e8005230beea7eb12037/library/std/src/panicking.rs#L257

The first print to the output then happens:

https://github.com/rust-lang/rust/blob/26b2b8d162ff6cc399c7e8005230beea7eb12037/library/std/src/panicking.rs#L258

For captured output this requires then reallocating the `Vec` storing the capture, so it calls into the allocator, hitting the `Backtrace::force_capture` because this is the first allocation in the test. This attempts to re-entrantly acquire the lock a second time, deadlocking:

https://github.com/rust-lang/rust/blob/26b2b8d162ff6cc399c7e8005230beea7eb12037/library/std/src/backtrace.rs#L326
Repository: rust
Issue: [rustdoc] type aliases in function signatures can be confusing
Labels: T-rustdoc,C-discussion

### Location

https://doc.rust-lang.org/std/io/struct.Lines.html

### Summary

https://doc.rust-lang.org/std/io/struct.Lines.html states that Lines::fmt has a return value of "Result" 
whereas  https://doc.rust-lang.org/std/fmt/trait.Debug.html#tymethod.fmt says that fmt has a return value of "Result<(),E>"
Repository: PowerToys
Issue: Workspaces can close software
Labels: Idea-Enhancement,Needs-Triage,Product-Workspaces

### Description of the new feature / enhancement

I would like workspaces to not only open software, but also close software. Sort of a "this is my programming workspace" or "This is my triage emails workspace" or "This is my, share my screen workspace"

### Scenario when this would be used?

I could see this being used by people looking to increase productivity, share screens, in conference rooms, etc. I think the workspace idea is a great thing, and it just needs a little bit of features fleshed.

Something I'm sure is inbound anyway as it _just_ released. Thanks! 😀

### Supporting information

Nothing specific really - just thought it would be nice to have
Repository: flutter
Issue: [image_picker] Support option for already selected images in ImagePicker().pickMultiImage()
Labels: c: new feature,p: image_picker,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

### Use case

Currently, pickMultiImage() returns a [List] object with the Images that were picked.

When selecting multiple Images, sometimes you might need to let the user preview the images before saving them in state. If the user wants to edit the selected images, calling the ImagePicker().pickMultiImage() function again does not save the previously selected images.

This function should have an optional parameter for already selected images, so that when the new native Galery view is opened, the images that were selected from a previous state are marked with selected.


### Proposal

Adding an optional parameter for selected images (maybe a [List<Object>] for already selected images should add more functionality to this flow.
Repository: godot
Issue: `TileMapLayer` build-in navigation prints `navigation_map.is_null()` errors on builds with `disable_3d=true`
Labels: bug,topic:navigation,topic:2d

### Tested versions

4.3.stable.mono

### System information

Godot v4.3.stable.mono - macOS 14.6.1 - GLES3 (Compatibility) - Apple M2 - Apple M2 (8 Threads)

### Issue description

When running an iOS app built using a custom export template with disable_3d = "yes", the following errors appear in the Xcode output window:

`ERROR: Condition "navigation_map.is_null()" is true.
at: _navigation_update_cell (scene/2d/tile_map_layer.cpp:1031)`

One message appears for every tile added to a TileMapLayer in a 2D Godot project. Although these errors do not appear to cause any problems, a lot of output is generated for projects with a large number of levels.

### Steps to reproduce

Reproducible with a minimal Godot project.
No code, just a TileMapLayer scene with a number of tiles added.

### Minimal reproduction project (MRP)

N/A
Repository: langchain
Issue: DOC: Description of `kwargs` in `langchain_core.prompts.chat.HumanMessagePromptTemplate.from_template_file()` misleading
Labels: 🤖:docs

### URL

https://api.python.langchain.com/en/latest/prompts/langchain_core.prompts.chat.HumanMessagePromptTemplate.html

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

The documentation for the class method `from_template_file()` for the class `langchain_core.prompts.chat.HumanMessagePromptTemplate` is misleading, since it states that `kwargs` are "keyword arguments to pass to the constructor". However this is not true. `kwargs` will be passed to `from_template()`, which means that `partial_variables` will **not** be passed to the constructor, but will be handled by `from_template`.

### Idea or request for content:

The description "keyword arguments to pass to the constructor." should probably be changed to "keyword arguments to pass to `from_template`.".

Note that there might be more alternative constructors that suffer from this problem.
Repository: go
Issue: runtime: crash when ending checkmarks
Labels: NeedsInvestigation,compiler/runtime

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?


### 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='/Users/mm/Library/Caches/go-build'
GOENV='/Users/mm/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/mm/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/mm/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/mm/go/src/github.com/MikeMitchellWebDev/go_checkmark'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/mm/go/src/github.com/MikeMitchellWebDev/go_checkmark/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/Users/mm/Library/Application Support/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='/usr/bin/clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/Users/mm/go/src/github.com/MikeMitchellWebDev/go_checkmark/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/5y/wtzzmjlj5v52pg7wr8ptbg_m0000gp/T/go-build641299882=/tmp/go-build -gno-record-gcc-switches -fno-common'
GOROOT/bin/go version: go version devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000 darwin/amd64
GOROOT/bin/go tool compile -V: compile version devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000
uname -v: Darwin Kernel Version 20.6.0: Thu Jul  6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_X86_64
ProductName:	macOS
ProductVersion:	11.7.10
BuildVersion:	20G1427
lldb --version: lldb-1300.0.42.3
Swift version 5.5.2-dev
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
./GODEBUG=gccheckmark=1 ./gc_knobs
./gc_knobs_client -g 200 -s 1 -r 10 -p "/Users/mm/backbone"

(both gc_knobs_client and gc_knobs are available on my github https://github.com/MikeMitchellWebDev/gc_knobs and  https://github.com/MikeMitchellWebDev/gc_knobs_client)



### What did you expect to see?



### What did you see instead?
see attached file [workbufs.txt](https://github.com/user-attachments/files/16945450/workbufs.txt)
Repository: go
Issue: runtime: checkmarks found unexpected unmarked object
Labels: NeedsInvestigation,compiler/runtime

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?


### 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='/Users/mm/Library/Caches/go-build'
GOENV='/Users/mm/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/mm/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/mm/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/mm/go/src/github.com/MikeMitchellWebDev/go_checkmark'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/mm/go/src/github.com/MikeMitchellWebDev/go_checkmark/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/Users/mm/Library/Application Support/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='/usr/bin/clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/Users/mm/go/src/github.com/MikeMitchellWebDev/go_checkmark/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/5y/wtzzmjlj5v52pg7wr8ptbg_m0000gp/T/go-build968457191=/tmp/go-build -gno-record-gcc-switches -fno-common'
GOROOT/bin/go version: go version devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000 darwin/amd64
GOROOT/bin/go tool compile -V: compile version devel go1.24-f3b0219 Tue Aug 27 21:02:02 2024 +0000
uname -v: Darwin Kernel Version 20.6.0: Thu Jul  6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_X86_64
ProductName:	macOS
ProductVersion:	11.7.10
BuildVersion:	20G1427
lldb --version: lldb-1300.0.42.3
Swift version 5.5.2-dev
</pre></details>

### What did you do?
./GODEBUG=gccheckmark=1 ./gc_knobs
./gc_knobs_client -g 200 -s 1 -r 10 -p "/Users/mm/backbone"

(both gc_knobs_client and gc_knobs are available on my github)  https://github.com/MikeMitchellWebDev/gc_knobs_client and https://github.com/MikeMitchellWebDev/gc_knobs
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?



### What did you see instead?

[unexpected_unmarked_object.txt](https://github.com/user-attachments/files/16945485/unexpected_unmarked_object.txt)