sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: static export trailingslash scss path not being located correctly
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.13.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.9
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: export
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Static HTML Export (output: "export")

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/chanwoong528/hk-bonghwang

### To Reproduce

```js
// next.config.js
/** @type {import('next').NextConfig} */
const path = require("path");
const withImages = require("next-images");

const nextConfig = {
  output: "export",
  reactStrictMode: true,
  trailingSlash: true,  // assetPrefix: "/temp/bonghwang/out",
  assetPrefix: ".",
  sassOptions: {
    fiber: false,
    includePaths: [path.join(__dirname, "styles")],
  },
  images: {
    unoptimized: true,
  ...
  },
  webpack: (config, options) => {
    config.module.rules.push(
      {
        test: /\.(png|gif|jpg|jpeg|svg|woff|woff2|)(\?|$)/,
        // issuer: /\.(css|sass|scss)$/i,
        type: 'asset/resource',
        generator: {
          filename: `${options.dev ? "[path][name][ext]" : "[name][ext]"}`,
          publicPath: `${options.dev ? "../../media/" : "../media/"}`,
          outputPath: `./static/media/`,
        },
      },
    );
    return config;
  },
};

module.exports = nextConfig; 
```


### Describe the Bug

static export trailingslash scss path not being located correctly
where output folder would be consist of

```
.next/
     static/
            css
                css.hash.css
about/
     index.html
someotherroutefolder/
index.html (a)
```

where index.html(a) css is being loaded as expected from 
`<link rel="stylesheet" href="./_next/static/css/cd0981ee31cd398f.css" data-precedence="next">`
but since index.html inside about folder should be one depth deeper, but still generate same as above which is 
`<link rel="stylesheet" href="./_next/static/css/cd0981ee31cd398f.css" data-precedence="next">`

therefore in sub directory files cannot be refered to proper link of css



### Expected Behavior

where index.html(a) css is being loaded as expected from 
`<link rel="stylesheet" href="./_next/static/css/cd0981ee31cd398f.css" data-precedence="next">`
in subdirectory like about/ ,should be generate link tag as
`<link rel="stylesheet" href="../_next/static/css/cd0981ee31cd398f.css" data-precedence="next">`

### Which browser are you using? (if relevant)

not relavant

### How are you deploying your application? (if relevant)

ftp folder
Repository: ollama
Issue: Fine-tuning support
Labels: feature request

First of all, thanks for building this tool and releasing it as open source. I like that the interfaces seem similar to `docker`.

I also like the idea of Modelfile. Maybe it could also be used to define a finetuning process. That would also allow making the build process be part of a CI/CD routine and would allow building private finetuned models with a good developer UX, which I'm sure lots of people are looking for presently.
Repository: next.js
Issue: Absolute Imports Don't work in Yarn Workspaces
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: 3.6.1
      pnpm: N/A
    Relevant Packages:
      next: 13.4.11
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Package manager (npm, pnpm, Yarn)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/radzionc/reactkit/tree/feat/monorepo

### To Reproduce

You can copy the repository on the `monorepo` branch and try to run the NextJS app.

### Describe the Bug

When I'm trying to import from the `ui` package I get the error like this:
```tsx
Module not found: Can't resolve 'ui/animations/transitions'
  1 | import styled, { css } from "styled-components"
> 2 | import { defaultTransitionCSS } from "ui/animations/transitions"
  3 | import { HStack } from "ui/Stack"
  4 | import { Text } from "ui/Text"
  5 | import { getColor } from "ui/theme/getters"
```

While the `ui` package has `baseUrl` set to `.`.

### Expected Behavior

The NextJs app should be able to import packages that use absolute imports.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: vscode
Issue: Allow different indentation settings in sections of the file
Labels: feature-request,editor-core

<!-- ⚠️⚠️ 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. -->
Currently, vscode fully controls whether the file uses tab or space to indent. However, as we know, using tabs in yaml files is a syntax error. When using Vue SFC, we expect using spaces to indent in yaml codeblocks, like this:

```vue
<custom lang="yaml">
foo:
  bar: true
</custom>
```

But we cannot control what should be used for indentation, which results in an embarrassing situation: we have to use spaces in yaml codeblocks, but when we press `tab`, it still prints a tab, not spaces.
Repository: flutter
Issue: [Impeller] Investigate adding sub-passes as a first class feature in `//impeller/renderer`
Labels: c: proposal,P3,e: impeller,team-engine,triaged-engine

We are reworking the render passes on Vulkan to implicitly introduce sub-passes when input attachments are referenced in shaders. For tilers, this is a performance improvement and Flutter will use this in cases like advanced blends.

If subpasses where a first class feature in the HAL, it might be easier (because of the explicitness) to optimize filter chains and other techniques used in deferred renderers.

Is Impeller missing a trick by abstracting away subpasses as an implementation detail of Vulkan render passes? Backends that don't support subpasses can trivially fall back to a render-pass per subpass.
Repository: go
Issue: x/tools/gopls: extract(refactor) fails on anonymous structs 
Labels: gopls,Tools

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?
```
go version go1.20.6 darwin/amd64

golang.org/x/tools/gopls v0.12.4
    golang.org/x/tools/gopls@(devel)
````

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?
darwin, amd64


### What did you expect to see?
Refactor of code with anonymous struct completes successfully


### What did you see instead?
`parent nil` error while extracting code with anonymous struct
I was able to reproduce the issue in both Neovim and VSCode.

On the demo below, you can see a successful refactor of named struct and then fail on anonymous struct.
https://github.com/golang/go/assets/27726430/f3096917-4158-4bf1-be52-4477863fa454
Repository: pytorch
Issue: Compile error PyTorch 2.0.1 / GCC 13.1.0
Labels: module: build,triaged

### 🐛 Describe the bug

I came across a strange error when compiling PyTorch (only C++ API, Python disabled) on A64FX using GCC 13.1.0.

When compiling the file `aten/src/ATen/native/mkldnn/Pooling.cpp` GCC turns on `-Werror` without turning on `-Wno-dangling-reference` so that
```
aten/src/ATen/core/IListRef_inl.h:171:17: error: possibly dangling reference to a temporary [-Werror=dangling-reference]
  171 |     const auto& ivalue = (*it).get();
```
This seems to be triggered by line 534 in `caffe2/CMakeLists.txt`:
```
# Required workaround for LLVM 9 includes.
if(NOT MSVC)
  set_source_files_properties(${TORCH_SRC_DIR}/csrc/jit/tensorexpr/llvm_jit.cpp PROPERTIES COMPILE_FLAGS -Wno-noexcept-type)
  # Force -Werror on several files
  set_source_files_properties(${CMAKE_CURRENT_LIST_DIR}/../aten/src/ATen/native/mkldnn/Pooling.cpp PROPERTIES COMPILE_FLAGS "-Werror")
endif()
```
Is this special treatment of the file `Pooling.cpp` really necessary? If so, one should maybe add `-Wno-dangling-reference`.

### Error logs

_No response_

### Minified repro

_No response_

### Versions

Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Rocky Linux release 8.4 (Green Obsidian) (aarch64)
GCC version: (GCC) 8.5.0 20210514 (Red Hat 8.5.0-15)
Clang version: 12.0.1 (Red Hat 12.0.1-4.module+el8.5.0+715+58f51d49)
CMake version: version 3.20.2
Libc version: glibc-2.17

Python version: 3.6.8 (default, Nov  9 2021, 14:47:09)  [GCC 8.5.0 20210514 (Red Hat 8.5.0-3)] (64-bit runtime)
Python platform: Linux-4.18.0-305.25.1.el8_4.aarch64-aarch64-with-centos-8.4-Green_Obsidian
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

CPU:
Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              48
On-line CPU(s) list: 0-47
Thread(s) per core:  1
Core(s) per cluster: 12
Socket(s):           -
Cluster(s):          4
NUMA node(s):        4
Vendor ID:           FUJITSU
Model:               0
Model name:          A64FX
Stepping:            0x1
BogoMIPS:            200.00
NUMA node0 CPU(s):   0-11
NUMA node1 CPU(s):   12-23
NUMA node2 CPU(s):   24-35
NUMA node3 CPU(s):   36-47
Flags:               fp asimd evtstrm sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm fcma dcpop sve

Versions of relevant libraries:
[pip3] numpy==1.14.3
[conda] Could not collect

cc @malfet @seemethere @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: go
Issue: net/http: TestIssue4191_InfiniteGetToPutTimeout failures with timeouts
Labels: Testing,NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && test == "TestIssue4191_InfiniteGetToPutTimeout" && `increasing timeout` && `Error issuing GET`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/6ec0890ff76db8b975315e9ba62e17d3754d4ed2)):

    --- FAIL: TestIssue4191_InfiniteGetToPutTimeout (0.00s)
        --- FAIL: TestIssue4191_InfiniteGetToPutTimeout/h1 (2.44s)
            transport_test.go:2289: increasing timeout
            transport_test.go:2294: Error issuing GET: Get "http://127.0.0.1:58443/get": read tcp 127.0.0.1:58441->127.0.0.1:58443: i/o timeout


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: [FSDP] using CPUOffload cannot make the code runing stop
Labels: triaged,module: fsdp

### 🐛 Describe the bug

I was tried to use offload fsdp to run the vicuna training, 

however, after I run this command. the code looks like keeping still for 3-4hours and prints nothing like and the last warning before it stay  is 

```
Please use torch.distributed.reduce_scatter_tensor instead.
  "torch.distributed._reduce_scatter_base is a private function and will "
```


### Versions



```
torchrun --nproc_per_node=8 --master_port=20002 fastchat/train/train_mem.py \
    --model_name_or_path /home/ma-user/work/jianqiao/alpca-lora/weights  \
    --data_path data/sharegpt_clean_gpt4_openchat_v2_maxlen1024.json \
    --bf16 False \
    --fp16 True \
    --output_dir output_vicuna \
    --num_train_epochs 3 \
    --per_device_train_batch_size 1 \
    --per_device_eval_batch_size 1 \
    --gradient_accumulation_steps 16 \
    --evaluation_strategy "no" \
    --save_strategy "steps" \
    --save_steps 1200 \
    --save_total_limit 10 \
    --learning_rate 2e-5 \
    --weight_decay 0. \
    --warmup_ratio 0.03 \
    --lr_scheduler_type "cosine" \
    --logging_steps 1 \
    --fsdp "full_shard offload auto_wrap" \
    --fsdp_transformer_layer_cls_to_wrap 'LlamaDecoderLayer' \
    --tf32 False \
    --model_max_length 1024 \
    --gradient_checkpointing True \
    --lazy_preprocess True \
    --data_key items
```

Could anybody help to solve this issue?

Thanks.

cc @zhaojuanmao @mrshenli @rohan-varma @awgu
Repository: material-ui
Issue: Input elements in MUI modal are blurred after first focus
Labels: component: modal

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

I am using material UI <Modal> component and I am facing this issue: When I open modal and try to focus any input element in modal (for example <Autocomplete> or <Textfield> the first focus is **blurred immediately**. The second focus and so on are behaving correctly (the focus is persisted). I tried using Modal props  disableAutoFocus, disableRestoreFocus,  disableEnforceFocus but none of this works

This is my minimal example code: (when I open the modal and focus the Textfield for the first time, the focus is immediately blurred)

```jsx
 <Modal
        open={!!editTemplateId}
        onClose={() => setEditTemplateId(undefined)}
      >
        <Box
          sx={{
            width: '600px',
            ...modalStyles,
          }}
        >
          <TextField
            variant="filled"
            label={t('edit-modal.subject')}
            sx={{ width: '100%', mb: 2 }}
            value={ts}
            onChange={(e) => st(e.target.value)}
          />
        </Box>
      </Modal>
```


### Current behavior 😯

Input elements in the <Modal> component are blurred for the first time they are focused

### Expected behavior 🤔

Focus on input element should persist

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: godot
Issue: apksigner returned error #2”
Labels: discussion,platform:android,topic:export

### Godot version

v3.5.2.stable.official 

### System information

Ubuntu 20.04.4 LTS

### Issue description

 Got the error “apksigner returned error #2” while exporting.

https://docs.godotengine.org/en/3.5/tutorials/export/exporting_for_android.html 
 
Referred to mentioned fixes.  Updated the JDK version to 11 but still got the same error for both Godot 4.1 and 3.5. as well.

### Steps to reproduce

Export for android

### Minimal reproduction project

No response
Repository: godot
Issue: Attach Node Script window use different default Path value before and after save scene
Labels: bug,topic:editor,confirmed

### Godot version

v4.1.stable.official [970459615]

### System information

macOS Ventura 13.4.1 (c) (22F770820d)

### Issue description

The `Path` in `Attach Node Script` window has a wrong default value. It used a cached value based on Node Tree level I think. 

### Steps to reproduce

1. Create a new project
2. Create a base node `Label`
3. Save and reload the scene as `label.tscn`
5. Delete the `Label` node and create another node `Sprite2D`
6. `Attach Node Script` to the newly created node, and the default value for `Path` is `res://label.gd` (default to scene name). 

Without save and reload the scene, the `Path` value is default to node name.

The `Attach Node Script`'s default `Path` value has an inconsistent behavior depend on whether the user save and reload the scene or project.

### Minimal reproduction project

N/A
Repository: go
Issue: x/website: add regression tests HTML anchors of important docs don't change
Labels: Documentation,help wanted,NeedsInvestigation,website


Previously the documentation for `go doc` links was at: https://go.dev/doc/comment#doc-links
Now it is at: https://go.dev/doc/comment#doclinks
The difference is in the hashref.

As now both links are in use (probably mostly by myself as I am a big promoter of godoc links), a redirect would be helpful.
Repository: node
Issue: `test/internet/test-net-autoselectfamily-timeout-close` times out on daily internet tests CI
Labels: flaky-test

### Test

internet/test-net-autoselectfamily-timeout-close

### Platform

_No response_

### Console output

```console
13:05:23 not ok 27 internet/test-net-autoselectfamily-timeout-close
13:05:23   ---
13:05:23   duration_ms: 120067.17800
13:05:23   severity: fail
13:05:23   exitcode: -15
13:05:23   stack: |-
13:05:23     timeout
13:05:23   ...
```


### Build links

- https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/31639/console
- https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/31687/console

### Additional information

The `internet` suite of tests are run daily as part of [node-daily-master](https://ci.nodejs.org/job/node-daily-master/) (they are not run as part of the regular CI job as they reach out to other servers across the internet). The daily CI runs the internet test suite by running [test-commit-custom-suites-freestyle](https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/) with `internet` set as the `CI_JS_SUITES` build parameter.
Repository: deno
Issue: Ability to control the backing storage of Deno.openKv
Labels: ext/kv

In order to be able to write tests using Deno Kv there should be a way to control the storage.

Using strace I was able to locate the actual backing file: `~/.cache/deno/location_data/d6f888b9dae5a9d23bf85990c7609f8e3471db775bdd3bdf64c55c695353991d/kv.sqlite3`. This file is shared for all invocations of deno from inside the project. I'd like to be able to specify `:memory:` (for regular test runs) or some other file (for debugging) as a backing store.

I am not sure what the right knobs would be. Probably cmdline argument would work the best for me. That would allow using empty ephemeral store as well as some curated prepopulated store for regression tests.
Repository: go
Issue: cmd/compile: overhaul inliner
Labels: Performance,compiler/runtime

We’re starting a project to overhaul the inlining optimization pass in the Go compiler, with the goal of having a far more effective inliner in Go 1.22. This issue will track this work. [This document](https://docs.google.com/document/d/1a6p7-nbk5PVyM1S2tmccFrrIuGzCyzclstBtaciHxVw/edit) motivates this project and outlines our general design goals. More detailed design documents will follow.

This project is being driven by @thanm and @mdempsky, but we would love to have input from the community. Inlining is inherently very heuristic and can be a deep rabbit hole to go down, so I’m sure many of our design decisions will be motivated by pragmatism and trying to ship something better than what we have for Go 1.22, even if it’s not perfect, with the goal of further improving it in later releases.
Repository: material-ui
Issue: [docs] Update docs related to using Next.js's Link with Material UI
Labels: docs,nextjs

The API for `<Link/>` is very different for Pages Router and App Router:

- App Router Link: https://nextjs.org/docs/app/api-reference/components/link
- Pages Router Link: https://nextjs.org/docs/pages/api-reference/components/link

The docs on routing [here](https://mui.com/material-ui/guides/routing/#next-js) should be updated

TODO:

- [ ] 1. Remove `legacyBehavior={true}` #44871
- [ ] 2. Update https://mui.com/material-ui/integrations/routing/#next-js-pages-router, `NextLinkComposed` doesn't seem to make sense anymore.
Repository: PowerToys
Issue: Keyboard Manager Doesn't Work in Task Manager
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Priority-2,Status-Reproducible

### Microsoft PowerToys version

0.71.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Remap a key that you can use while Windows Task Manager is open, for example Caps Lock -> anything. Verify that it works at the desktop or in another application, then open Task Manager. Pressing Caps Lock while Task Manager is the focused application will now enable caps lock instead of whatever you mapped it to. This also happened with keys remapped to play/pause and next track.

### ✔️ Expected Behavior

Keyboard Manager should work the same regardless of the focused application.

### ❌ Actual Behavior

It does not.

### Other Software

Task Manager in Windows 11 Pro Insider Preview Build 25905.rs_prerelease.230707-1739.
Repository: ollama
Issue: Don't automatically start on startup / have an option to disable this
Labels: feature request

EDIT: [there's a PR for it now](https://github.com/ollama/ollama/pull/7097)!

---

Thanks for making this!

I noticed that on macOS (I suppose it's the same on Windows), the app sets itself to open at login. This is done here:

https://github.com/jmorganca/ollama/blob/91cd54016c47b71223e8263c44250766874e05cf/app/src/index.ts#L175,L180

1) I'm not sure whether that should be the case by default (up for discussion)
2) I don't remember seeing a warning about this when installing the app (this might be debatable as well)
3) it would be great to have an option within the app to disable this

Cheers
Repository: excalidraw
Issue: UX Improvement to resizing a selection of frames 
Labels: bug,enhancement,frames

Action: I want to resize a group of frames and all of the contents inside of those frames

- When I click and drag to select a large group of frames
- The anticipated behaviour is that resizing this selection will resize all frames and all contents within frames - in a similar way to how groups or regular selection works
- Right now, only the frames resize and the internal contents get left behind at their original size:

<img width="778" alt="Screenshot 2023-07-21 at 15 26 38" src="https://github.com/excalidraw/excalidraw/assets/5108043/c758b206-f4e5-4419-aa18-f4b37cc76159">

<img width="1123" alt="Screenshot 2023-07-21 at 15 29 57" src="https://github.com/excalidraw/excalidraw/assets/5108043/977269de-1bcd-4b7f-a1f0-4d4d9cfd52bb">