sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/go: doc -http should start a pkgsite instance and open a browser
Labels: Proposal,Proposal-Accepted,FeatureRequest,GoCommand,pkgsite/cmd

The `go doc` command displays documentation to stdout, which is handy for quick forays for a single package or symbol, but for extended reading a browser is more convenient, as it has better typography and linked cross-references. We propose that `go doc -http` should start a [pkgsite](https://github.com/golang/pkgsite) instance in the background (if one is not running already)  and open a web browser to the correct URL for the package or symbol.

The pkgsite program is currently rather large and slow to start as it was designed as a [long-lived server for a large corpus](https://pkg.go.dev/) on Google Cloud. Issue #61399 tracks the work to slim it down and reduce dependencies.

Open questions:
- How should successive `go doc` processes communicate the port or pid of the running instance, and deal with server crashes?
- The server would necessarily outlive the go command. Is an explicit "stop" operation necessary?
- Should the -http flag be a boolean, or an integer port? I think boolean (picking any unused port) would be more friendly.

@rsc @matloob
Repository: PowerToys
Issue: File Locksmith opens when a program (WizTree) is trying to open a file with the associated handler
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.1

### Installation method

Microsoft Store, WinGet

### Running as admin

Yes

### Area(s) with issue?

File Locksmith

### Steps to reproduce

0. Have the following installed:
- PowerToys
- Wiztree 4.19 (a disk space analysis tool)
Ensure that File Locksmith is enabled.

1. As an admin user, open WizTree. It will ask for administrator permission to access all folders.
2. Navigate to a folder containing a file associated with a default program (e.g., PDF, JPG, DOCX, TXT)
3. Right-click the filename in the file browser or the graphical file-size representation
4. Click "Open" (bolded) from the context menu (depending on the configuration, for some filetypes this may be "Open with XXX", where XXX is the associated program, e.g., "Open with Adobe Acrobat")



### ✔️ Expected Behavior

The associated program opens the file selected.

### ❌ Actual Behavior

File Locksmith opens, displaying lock information for the file.

### Other Software

[Wiztree ](https://diskanalyzer.com/) 4.19
Repository: go
Issue: x/build/cmd/relui: merge 'Start Google Docker build' + 'Await Google Docker build' into one retryable task
Labels: Builders,NeedsInvestigation

The Google Docker build task is currently made of two tasks: one to start a Cloud Build invocation, and another to await its result. This has a flaw in that if the Cloud Build invocation happens to fail (with a retryable failure, such as a temporary internet connectivity error), it's not possible to retry it via relui UI. It will keep awaiting the original Cloud Build invocation, even if it failed.

This is the tracking issue to improve that, so it will be possible to resolve retryable failures in relui (either via the automatic 3 retries, or with a manual retry).

CC @dr2chase, @golang/release.
Repository: react-native
Issue: ws affected by a DoS when handling a request with many HTTP headers
Labels: Help Wanted :octocat:,🌐Networking

### Description

ws affected by a DoS when handling a request with many HTTP headers
https://github.com/advisories/GHSA-3h5v-q93c-6h6q

# Solution
Bump WS 
https://github.com/facebook/react-native/blob/main/packages/react-native/package.json#L147

### Steps to reproduce

NA

### React Native Version

*

### Affected Platforms

Other (please specify)

### Output of `npx react-native info`

```text
NA
```


### Stacktrace or Logs

```text
NA
```


### Reproducer

NA

### Screenshots and Videos

_No response_
Repository: ollama
Issue: DevCoders Llama3 uncensored breaks between 0.1.42 -> 0.1.43
Labels: bug

### What is the issue?

Importing and quantizing this model: https://huggingface.co/DevsDoCode/LLama-3-8b-Uncensored
(`ollama create -q Q4_K_M llama3-uncensored`)
with this Modelfile:
```
FROM /path/to/LLama-3-8b-Uncensored
TEMPLATE """{{ if .System }}
system


{{ .System }}
{{ end }}{{ if .Prompt }}
user


{{ .Prompt }}
{{ end }}
assistant


{{ .Response }}
"""
PARAMETER stop "
"
PARAMETER stop "
"
PARAMETER stop "
"
PARAMETER num_keep 24
```
has broken between v0.1.42 and v0.1.43


On 0.1.42, the model responds normally:
```
$ ollama -v
ollama version is 0.1.42
$ ollama run llama3-uncensored:latest
>>> hello
Hello there, how can I assist you today?
>>> whats up
Not much, just hanging out. What about you?
```

On 0.1.43, the model responds with gibberish:
```
$ ollama -v
ollama version is 0.1.43
$ ollama run llama3-uncensored:latest
>>> hello
http://www/other/sat/else/where/more//www/else/where//else/where/else//www/else/where/where//www/else/where/where//http://www/other/sat/else/where/more//www/else/where//else/where/else//www/else/where/where//www/else/where/where//www/elle/where//www/elle/Where//www/elle/Where//www/Where//www/elle// Where//www/elle// Where//www/elle//
Where//www/elle/Where//www/elle// Where//www/elle// Where//^C

>>> whats up
http://www/else/where:// www/else/ where:// http://www/else/ Where // www/else/ where: `http://www/else/ Where **
www/else**/ where: `http://www/else/ Where:** `http://www/else/ Where:** `http://www/else/ Where:**
`http://www/else/ Where:** ` http:// www/ else/ ` http:// www / else/ Where ` http:// www/ else/ ` http:// www /
else// where: ` http:// ` http:// www / else/ ` http:// ` ` http:// ` http:// ` http:// ` ` h http:// ` ` http://
` ` h http:// ` ` h ` http:// ` ' h ** ` h ** ` h ** ` h ** ` h ** ** ` h ** ` h** ** ` h ** ** ` h ** ** ` h **
** `h** ** **h ** ** **h** ** **h** ** **h** ** **h** ** **h** ** **h** ** **h** ** **h** ** **h** ** **h** **
**h** ** **
```


### OS

WSL2

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.1.43
Repository: pytorch
Issue: RuntimeError: get_parameter is not supported on ScriptModules
Labels: oncall: jit,module: windows

### 🐛 Describe the bug

Hi everyone as the title says, I'm wondering if get_parameter is no more supported for ScriptModules.
Here a trivial example:

```python
import torch

class InputContainer(torch.nn.Module):
    def __init__(self, obj):
        super().__init__()
        for key, value in obj.items():
            setattr(self, key, value)

inputs = {
        "audio" : torch.rand((553172,))
        }
inputs_model = InputContainer(inputs)
inputs_script = torch.jit.script(inputs_model)
inputs_script.save("rmvpe_inputs.pt")
inputs_script.get_parameter("audio")

```
```
File "c:\Users\simos\miniconda3\envs\rcv\lib\site-packages\torch\jit\_script.py", line 981, in fail
    raise RuntimeError(name + " is not supported on ScriptModules")
RuntimeError: get_parameter is not supported on ScriptModules
```

what does it mean? are not docs up to date?

docs ref:
https://pytorch.org/docs/stable/generated/torch.jit.ScriptModule.html#torch.jit.ScriptModule.get_parameter


### Versions

PyTorch version: 2.2.2+cpu
Python version: 3.10.14

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @peterjc123 @mszhanyi @skyline75489 @nbcsm @vladimir-aubrecht @iremyux @Blackhex @cristianPanaite
Repository: PowerToys
Issue: [FilePreview] Add option to toggle minimap
Labels: Idea-Enhancement,Resolution-Fix Committed,Product-File Explorer

### Description of the new feature / enhancement

*This applies to Peek and Preview Pane.*

Monaco has the option for rendering a minimap, but it is hardcode disabled in PT.
https://github.com/microsoft/PowerToys/blob/9509d7c1ccd3554d457d5617153e7a412a7760ae/src/common/FilePreviewCommon/Assets/Monaco/index.html#L83
IMO the minimap is a useful feature and I hope there was an option for enabling it. I suggest it should be an option in the settings, but also toggleable from the editor by right-clicking (similar to wrapping).

### Scenario when this would be used?

Previewing code

### Supporting information

_No response_
Repository: rust
Issue: Tracking Issue for `core::clone::CloneToUninit` trait
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(clone_to_uninit)]`

This is a tracking issue for `CloneToUninit` and its impls. This trait backs the behavior of `Rc::make_mut` and `Arc::make_mut`, and likely in the future also `Box::clone`.

### Public API

```rust
// core::clone

pub unsafe trait CloneToUninit {
    unsafe fn clone_to_uninit(&self, dst: *mut Self);
}

unsafe impl<T: Clone> CloneToUninit for T;
unsafe impl<T: Clone> CloneToUninit for [T];

// TODO:
// unsafe impl CloneToUninit for str;
// unsafe impl CloneToUninit for CStr;
// unsafe impl CloneToUninit for OsStr;
// unsafe impl CloneToUninit for Path;
```

### Steps / History

- [x] Implementation: https://github.com/rust-lang/rust/pull/116113
- [ ] https://github.com/rust-lang/rust/pull/126877
- [ ] Convert `Box::clone` to be based on `CloneToUninit`
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilized. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- Consider using `*mut ()` in the signature instead of `*mut Self`. This makes CloneToUninit dyn-safe. https://github.com/rust-lang/rust/pull/116113#discussion_r1335303908

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: rust
Issue: trying to get pointer to extern typed field causes runtime panic
Labels: C-discussion,F-extern_types

<!--
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.
-->

I tried this code:

```rust
#![feature(extern_types)]
extern {
    type Opaque;
}

struct Thing {
    _pad: u8,
    o: Opaque,
}

fn main() {
    let v = b"a";
    let x: &Thing = unsafe { std::mem::transmute(&v) };
    let field_ptr = &x.o as *const Opaque;
    println!("{:X}", field_ptr as usize)
}
```

I expected to see this happen: printing a stack address

Instead, this happened: panic: attempted to compute the size or alignment of extern type

### Context
one of the main usecases for extern types is representing trailing fields of variable size for C ffi.  this bug completely makes this impossible.  it also panics during a piece of safe code that should be infallible.  this panic does not occur if the extern type is the only field.

### Meta
<!--
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.
-->

`rustc --version --verbose`:
```
rustc 1.80.0-nightly (debd22da6 2024-05-29)
binary: rustc
commit-hash: debd22da66cfa97c74040ebf68e420672ac8560e
commit-date: 2024-05-29
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.6
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
Compiling playground v0.0.1 (/playground)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.48s
     Running `target/debug/playground`
thread 'main' panicked at library/core/src/panicking.rs:221:5:
attempted to compute the size or alignment of extern type `Opaque`
stack backtrace:
   0: rust_begin_unwind
             at /rustc/684b3553f70148ded97a80371c2405984d4f6aa7/library/std/src/panicking.rs:661:5
   1: core::panicking::panic_nounwind_fmt::runtime
             at /rustc/684b3553f70148ded97a80371c2405984d4f6aa7/library/core/src/panicking.rs:112:18
   2: core::panicking::panic_nounwind_fmt
             at /rustc/684b3553f70148ded97a80371c2405984d4f6aa7/library/core/src/panicking.rs:122:5
   3: core::panicking::panic_nounwind
             at /rustc/684b3553f70148ded97a80371c2405984d4f6aa7/library/core/src/panicking.rs:221:5
   4: playground::main
             at ./[src/main.rs:14](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021#):21
   5: core::ops::function::FnOnce::call_once
             at /rustc/684b3553f70148ded97a80371c2405984d4f6aa7/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread caused non-unwinding panic. aborting.
```

</p>
</details>
Repository: flutter
Issue: [pigeon] Make the codec public
Labels: c: new feature,package,team-ecosystem,p: pigeon,P2,triaged-ecosystem

While working on the conversion of `google_maps_flutter` to Pigeon, I encountered an important use case for being able to access the Pigeon serialization codec: platform view creation parameters.

The plugin has a lot of structured data that it passes in Pigeon calls (map options, collections of each of the map object types, etc.), but it also passes many of those same structures in the platform view creation call. We'll want to be able to set up Pigeon data classes for all them, and then use them in both Pigeon calls and in the creation params. The engine APIs for creating platform views allow specifying a codec that's used for the passed parameter object, so if we make the Pigeon codec public, then we could make the creation parameter object a Pigeon data class instead of the current Map of string->complex maps/lists.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Directory Structure for "sd_vae" & "sd_lora" when added to Top Row via Quicksettings list
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

TL;DR: Directory Structure for VAE and Networks would save us all a headache.

The "Stable Diffusion checkpoint" lists directory structure, which is great for keeping things organized according to model type: SD1, SD2, SDXL, SD3, etc.

"SD VAE" & "Add network to prompt" list everything in alphabetical order and ignore structure.

If you have a lot of different VAEs or Networks (Lora, Lycoris, etc) for many of the different model types it can be extremely confusing and will lead to loading the wrong VAE or Network with the wrong model type.

### Proposed workflow

1. Go to Top Row (provided you're already using sd_vae & sd_lora under Quicksettings)
2. Press the list
3. See Directory Structure like the Checkpoint List in the top left


### Additional information

_No response_
Repository: ollama
Issue: OLLAMA_MODELS is not honored after being changed (beyond the first time it is set)
Labels: bug

### What is the issue?

I set `OLLAMA_MODELS` to a new directory to ensure a large download would have space, and then tried to move `OLLAMA_MODELS` back  to the default directory on Windows - and although the environmental variable is set, ollama continues to search in the  previous `OLLAMA_MODELS` path, even after restarting all terminals or rebooting.

### OS

Windows (not via WSL)

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.1.44
Repository: electron
Issue: [Feature Request]: systemPreferences.getAccentColor Linux support
Labels: enhancement :sparkles:,platform/linux,component/system-preferences

### 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

`systemPreferences.getAccentColor` only works for Windows and MacOS. I assume this is due to the various different Linux desktop environments out there, all of which may or may not support accent color and with different APIs.

### Proposed Solution

Most popular Linux desktop environments now come built in with support for Accent Colors, with support being recently added to GNOME, and being in KDE Plasma and XDG-Desktop-Portal for a bit. This should be good grounds for supporting these systems.

### Alternatives Considered

The alternative is to manually implement this in your electron app, but seems quite silly given that a method named `getAccentColor` already exists.

### Additional Information

_No response_
Repository: flutter
Issue: [web] Remove virtual keyboard timer hack on iOS Safari
Labels: a: text input,engine,platform-web,P2,c: tech-debt,browser: safari-ios,team-web,triaged-web

On iOS, we have a hack that moves the input element off screen while the virtual keyboard is popping up, and later positions the input element back where it's supposed to be. This was done to prevent Safari from scrolling the page while the virtual keyboard is popping up.

Today, we have a modern API that we can use to prevent that behavior without any hacks:
- [`HTMLElement.focus({preventScroll: true});`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/focus#preventscroll)

This API is available since iOS Safari 15.5. Let's try it and cleanup the old hack if it works.
Repository: go
Issue: net/http: TestTransportDialCancelRace/h1 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestTransportDialCancelRace/h1"
```

Issue created automatically to collect these failures.

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

    === RUN   TestTransportDialCancelRace/h1
        transport_test.go:4299: expected canceled request error; got <nil>
    --- FAIL: TestTransportDialCancelRace/h1 (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: rust
Issue: Tracking Issue for `-Z verbose-asm`
Labels: C-tracking-issue

This is a tracking issue for the `-Z verbose-asm` compiler flag, which emits backend-generated comments with the assembly.

MCP: https://github.com/rust-lang/compiler-team/issues/762

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement the MCP https://github.com/rust-lang/rust/issues/126802
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Formatting for new syntax has been added to the [Style Guide] ([nightly-style-procedure])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions

None at this time

### Implementation history

- Original implementation as `asm_comments` at https://github.com/rust-lang/rust/pull/53290
- Adjusting to be in line with the MCP https://github.com/rust-lang/rust/issues/126802
Repository: storybook
Issue: [Documentation]: <Source> format prop incorrectly states it takes in BuiltInParserName
Labels: documentation,needs triage

### Describe the problem

https://github.com/storybookjs/storybook/blob/next/docs/api/doc-block-source.md?plain=1#L115

This documentation is misleading (unless I'm missing something...)

```
Type: boolean | 'dedent' | BuiltInParserName

Default: parameters.docs.source.format or true

Specifies the formatting used on source code. Both true and 'dedent' have the same effect of removing any extraneous indentation. Supports all valid [prettier parser names](https://prettier.io/docs/en/configuration.html#setting-the-parserdocsenoptionshtmlparser-option).
```

## BuiltInParserName

"Supports all valid prettier parser names" - but what does that mean? I tried entering `typescript` which is a valid parser name and I get the following in the console:

```
ConfigError: Couldn't resolve parser "typescript". Plugins must be explicitly added to the standalone bundle.
```

I did a little more digging and found the following in what I believe is the formatting utility the `<Source>` block is using:

```typescript
import memoize from 'memoizerific';

import prettierHtml from 'prettier/plugins/html';
import prettier from 'prettier/standalone';
import { dedent } from 'ts-dedent';
import type { SyntaxHighlighterFormatTypes } from './syntaxhighlighter-types';

export const formatter = memoize(2)(async (type: SyntaxHighlighterFormatTypes, source: string) => {
  if (type === false) {
    return source;
  }
  if (type === 'dedent' || type === true) {
    return dedent(source);
  }

  return (
    await prettier.format(source, {
      parser: type,
      plugins: [prettierHtml],
      htmlWhitespaceSensitivity: 'ignore',
    })
  ).trim();
});
```

https://github.com/storybookjs/storybook/blob/next/code/ui/components/src/components/syntaxhighlighter/formatter.ts#L19

From how I interpret this, this formatter function is only loading the Prettier HTML parser. That is why we're getting the error about needing the typescript parser added to the bundle.

At least that is my understanding.

If that is the case then this option to pass `BuiltInParserName` into the format prop of `<Source>` should be removed from the docs.

Of course the better case would be to somehow make this work the way the docs describe by either adding the parsers or somehow adding an option for the parsers to be passed in.

### Additional context

_No response_