sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: [data loss] METABUG: don't overwrite files
Labels: wontfix

## description of the problem

yt-dlp/youtube-dl is the only program(s) I know overwriting files without asking the user. Overwriting files is dangerous because it potentially causes **DATA LOSS**. Data loss is a very serious issue and should never occur!

All other programs I know warn the user if a file (image, video, document, etc.) already exists and ask the user if it should really be replaced (Y/N).

I hear you say that only "temporary files" are deleted:

_Originally posted by @pukkandan in https://github.com/yt-dlp/yt-dlp/issues/6705#issuecomment-1499870495_

>> files are unintentionally overwritten
>> This should **NEVER** occur with `--no-overwrites --no-post-overwrites` , no ?
>
> Temporary files are deleted if they can't be resumed, irrespective of any options.

I disagree with this notion. Downloads are not "temporary files" in the conventional sense. Other programs delete/overwrite (conventional) temporary files without user interaction only if they don't contain meaningful data for the user (i.e. scratch file, dump file, other files that ensure the programs operation, .... etc.). But the files yt-dlp overwrites are not of that sort but are downloads. So the data is meaningful to the user and potentially very valuable, especially if the source material is not available for download any longer and thus can't be obtained anymore.

For example, I downloaded the historic CNN livestream of President Trump's arrest and yt-dlp overwrote my download, which is now gone forever and unobtainable (#6705).


## related issues

I create this issue as a META bug subsuming all other instances where users have been affected by files overwritten by yt-dlp:

* #6501
* #6846 
* #6705 = livestream download should not overwrite previous downloads
* #6416
* #1467
* #2426 *"the audio and video files will overwrite each other"*
* #6228
* #5977
* #3160
* #2854

## how to solve the problem

I argue that files should never be overwritten without user consent!
Ask the user if files should get overwritten like all other programs do.

If for some reason you are not willing or unable to accept this common standard, then at least respect the user choice when then user explicitly tells yt-dlp `--no-overwrites --no-post-overwrites`.

The helpfile also is very clear: Do not overwrite **ANY** files!

```
--no-overwrites           Do not overwrite any files
--no-post-overwrites      Do not overwrite post-processed files
````
Repository: flutter
Issue: [iOS] Feature request: CupertinoListTile selected property
Labels: c: new feature,framework,f: cupertino,c: proposal,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

It would be great to have a selected property on CupertinoListTile just like we have for ListTile on Android. This is a feature on native iOS and part of native apps. I implemented my own for the time being, but I'm having VoiceOver issues with what I created.

## Proposal
Make the same selected property that Material ListTile has. Make it play well with VoiceOver of course so that VoiceOver reads the tile as "selected."
Repository: go
Issue: x/tools/gopls: don't discard errors computing diagnostics
Labels: NeedsInvestigation,gopls,Tools

The diagnostics logic in gopls must deal with many kinds of error, but ultimately they all get merely written to the server log because there is no place to show them to the user. But this means serious internal errors such as the one reported in https://github.com/golang/go/issues/58152#issuecomment-1500660413 (whose root cause is https://github.com/golang/go/issues/59289) are only detected this way.

We should make sure to use bug.Report for internal errors (bugs), and think about other ways to gather up errors (e.g. serious misconfiguration) so that they don't get neglected.
Repository: youtube-dl
Issue: 404 error with tweet video
Labels: broken-IE

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that all URLs and arguments with special characters are properly quoted or escaped as explained in http://yt-dl.org/escape.
- Search the bugtracker for similar issues: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Read bugs section in FAQ: http://yt-dl.org/reporting
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a broken site support issue
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
- [x] I've searched the bugtracker for similar bug reports including closed ones
- [x] I've read bugs section in FAQ


## Verbose log

<!--
Provide the complete verbose output of youtube-dl that clearly demonstrates the problem.
Add the `-v` flag to your command line you run youtube-dl with (`youtube-dl -v <your command line>`), copy the WHOLE output and insert it below. It should look similar to this:
 [debug] System config: []
 [debug] User config: []
 [debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
 [debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
 [debug] youtube-dl version 2021.12.17
 [debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
 [debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
 [debug] Proxy map: {}
 <more lines>
-->

```
 ERROR: Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
```


## Description

I'm trying to download metadata from tweets video and i'm getting 404 error. But yesterday was working very well
Repository: godot
Issue: Placing scene from scene collection in Tilemap while having tool script running '_tile_data_runtime_update' causes crash.
Labels: bug,topic:editor,crash,topic:2d

### Godot version

4.0.2

### System information

Windows 10

### Issue description

Placing scene from scene collection in Tilemap while having tool script running '_tile_data_runtime_update' causes crash.



### Steps to reproduce

1. Have tilemap running tool script with '_tile_data_runtime_update'.
2. Place tile.
3. Place scene from scene collection over tiles.
 

### Minimal reproduction project

[TileMapTest.zip](https://github.com/godotengine/godot/files/11181774/TileMapTest.zip)
Repository: flutter
Issue: Remove "All rights reserved." from Flutter source file license headers.
Labels: framework,engine,P2,team-engine,triaged-engine

According to our legal advisers:
> The words “all rights reserved” should never have been added, and it advertises a misunderstanding of copyright law (those words haven’t been legally meaningful in over 30 years) and does occasionally confuse downstream users regarding the licensing status of the code

This will require updating every source file, and the engine's license checker script.

cc @renaudd @Hixie
Repository: next.js
Issue: (create-next-app) Intellisense does not recognize alias paths
Labels: create-next-app,bug,TypeScript

### 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.6.0: Sun Nov  6 23:31:09 PST 2022; root:xnu-8020.240.14~1/RELEASE_ARM64_T8110
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.3.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

CLI (create-next-app), TypeScript (plugin, built-in types)

### Link to the code that reproduces this issue

nolink

### To Reproduce

Follow the steps below:

1. Create a new project using `npx create-next-app@latest`.
2. In the installer questions section, answer the following:
 ✔ Would you like to use TypeScript with this project?  **YES**
✔ Would you like to use ESLint with this project? **NO**
✔ Would you like to use Tailwind CSS with this project? **NO**
✔ Would you like to use `src/` directory with this project? **YES**
✔ Would you like to use experimental `app/` directory with this project? **NO**
✔ What import alias would you like configured? **@/***
3. Go to the `src/pages/index.tsx` path and try modifying the `import styles from '@/styles/Home.module.css'` line by removing everything after `from` to write it manually. When trying to type `@/styles` the browser's intellisense doesn't find the path in its autocompletion (it doesn't give an error).

### Describe the Bug

Code editor intellisense (VS Code) does not recognize aliased path, while it does not give an error resolving the path, it is not visible in editor autocompletion when typing `@/styles` (even using `ctrl+ space`).

When creating a new project using the above stepping configuration, a `tsconfig.json` file is created with the following configuration for the alias.

```json
{
   ...
   "paths": {
      "@/*": ["./src/*"]
    },
   ...
}
```

Apparently the previous configuration is what is causing the intelissense of the editor to not be able to help indicate the paths to the `@/` writer when importing any component.

### Expected Behavior

I hope the editor can suggest which folder or path I want to use when typing `@/` when importing a component.

Adding the following additional configuration to the `tsconfig.json` file seems to fix the problem.

```diff
{
    ...
+  "baseUrl": ".",
    "paths": {
       "@/*": ["./src/*"]
     },
    ...
}
```

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: puppeteer
Issue: [Bug/Question]: (Chromium) Getting service worker prevents it from starting
Labels: bug,upstream,confirmed,disable-analyzer

### Bug expectation

Context is in:
https://crbug.com/1371432

And the reproduction case is here: https://github.com/Manvel/puppeteer-kill-extension-sw.

I'm wondering what chromium DevTools code is being called when the following code is being called?

```
async function getWorker(browser) {
  const targets = browser.targets();
  const backgroundPageTarget = targets.find(
    (target) =>
      target.url().startsWith("chrome-extension://") &&
      (target.type() === "background_page" || target.type() === "service_worker")
  );
  return backgroundPageTarget.worker();
}

const worker = await getWorker(browser); 
```

This might help us determine where the bug is that is causing the service worker to never finish starting. I'm not as familiar with the chromium DevTools API so I wasn't confident I could track backwards that way.

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Minimal, reproducible example

```TypeScript
// (see the reproduction case for code, but I'll re-paste for reference)

const puppeteer = require("puppeteer");
const extensionPath = "extension";
let browser;
async function run()
{
   browser = await puppeteer.launch({headless: false , 
    executablePath: "/usr/local/google/home/jlulejian/chromium-checkouts/clone1/chromium/src/out/Release/chrome",
    args: [
    `--disable-extensions-except=${extensionPath}`,
    `--load-extension=${extensionPath}`,
    "--no-sandbox"
  ]});
  await sleep(1000); // Arbitriary wait time, so extension is loaded.

  // THE LINE BELOW CAUSES THE EXTENSION SERVICE WORKER TO GO INTO DEAD MODE,
  // MEANING THE SERVICE WORKER NEVER WAKES UP.
  const worker = await getWorker(browser); 

  const page = await browser.newPage();
  await page.goto("http://example.com");
  const swIntPage = await browser.newPage();
  await swIntPage.goto("chrome://serviceworker-internals");
  await page.bringToFront();
  await swIntPage.click("#serviceworker-list .stop");
  await page.click("#send-rpc-msg");
}

async function getWorker(browser) {
  const targets = browser.targets();
  const backgroundPageTarget = targets.find(
    (target) =>
      target.url().startsWith("chrome-extension://") &&
      (target.type() === "background_page" || target.type() === "service_worker")
  );
  return backgroundPageTarget.worker();
}

function sleep(ms) {
  return new Promise((resolve) => setTimeout(() => resolve(), ms));
}

run();
```


### Error string

no error

### Puppeteer configuration

```TypeScript
(no configuration AFAICT)
```


### Puppeteer version

19.8.5

### Node version

18.12.1

### Package manager

npm

### Package manager version

9.2.0

### Operating system

Linux
Repository: godot
Issue: Editor: Leaving fullscreen mode does not preserve maximized state (DisplayServer regression)
Labels: bug,platform:linuxbsd,topic:editor,topic:porting,confirmed,regression

### Godot version

4.0.2.stable

### System information

Arch Linux

### Issue description

In the editor, we can toggle fullscreen via _Editor > Toggle Fullscreen_.

When exiting fullscreen mode, the window will always leave maximized state.

Expected behavior: Restore the previous maximized state when leaving fullscreen mode.

### Steps to reproduce

1. Open the Godot editor. The window is maximized (by default).
2. Editor > Toggle Fullscreen. Now the window is fullscreen.
3. Editor > Toggle Fullscreen. The window exits fullscreen, but is not maximized.

### Minimal reproduction project

Open any project.
Repository: stable-diffusion-webui
Issue: [Bug]: API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

when i use api img2img  error happend
API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}

### Steps to reproduce the problem

API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}


### What should have happened?

API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}

### Commit where the problem happens

API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}

### What platforms do you use to access the UI ?

_No response_

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}
```


### List of extensions

API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}

### Console logs

```Shell
API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}
```


### Additional information

API error: POST: http://127.0.0.1:7860/sdapi/v1/img2img {'error': 'HTTPException', 'detail': 'Invalid encoded image', 'body': '', 'errors': ''}
Repository: deno
Issue: problems with sine update
Labels: needs investigation

Hello, it presents this problem when updating deno to its most recent version.

```
deno upgrade

Deno is upgrading to version 1.32.3
error: The operation could not be completed because the file contains a virus or potentially unwanted software. (or error 225)
```

Thank you for reading
Repository: go
Issue: x/pkgsite: add a special case to search ONLY within std / stdlib
Labels: FeatureRequest,pkgsite,pkgsite/search

### What is the URL of the page with the issue?

https://pkg.go.dev/std

### What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36

### Screenshot

N/A

### What did you do?

When I type something like `NewReader` it searches everything. I would like to see a way to confine my search to standard library. It's nice that stdlib results are labeled as such but either a special case or syntax addition to actual constrain my search would be very helpful.
Repository: go
Issue: x/tools/cmd/signature-fuzzer/fuzz-runner: TestRunner failures
Labels: NeedsInvestigation,Tools

```
#!watchflakes
post <- pkg == "golang.org/x/tools/cmd/signature-fuzzer/fuzz-runner" && test == "TestRunner"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/e9a3197740f4627db99ee2deb8b7008532ba184c)):

    --- FAIL: TestRunner (2.78s)
        --- FAIL: TestRunner/Minimization2 (0.27s)
            rnr_test.go:131: 
            rnr_test.go:137: -emitbad=2 did not trigger runtime error (invocation "/opt/golang/tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/TestRunner587605598/001/bin/runner [-emitbad=2 -badfcnidx=1 -badpkgidx=1 -forcetmpclean -cleancache=0 -numit=1 -numfcns=3 -numpkgs=3 -seed=55909]"): output: 
        --- FAIL: TestRunner/Basic (0.28s)
            rnr_test.go:62: 
            rnr_test.go:64: error invoking fuzz-runner: signal: segmentation Fault (core dumped)
        --- FAIL: TestRunner/Minimization1 (0.29s)
            rnr_test.go:101: 
            rnr_test.go:107: -emitbad=1 did not trigger syntax error (invocation "/opt/golang/tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/TestRunner587605598/001/bin/runner [-emitbad=1 -badfcnidx=2 -badpkgidx=2 -forcetmpclean -cleancache=0 -numit=1 -numfcns=3 -numpkgs=3 -seed=909]"): output: 


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: Tailwind option in CLI breaks the automatic docker CI/CD
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
This is the line in our `Dockerfile` that automatically creates a Next.js app:

    RUN npx --yes create-next-app next --use-npm --js --eslint --no-src-dir --experimental-app --import-alias @/*

This was working just fine until Next.js 13.3.0 introduced an option in the CLI to choose Tailwind to be configured automatically.

This option breaks the CLI automation.

What should we do?
```


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

_No response_

### Link to the code that reproduces this issue

There is no need for a MRE

### To Reproduce

- Create a `Dockerfile`
- Add these lines to it:

```
FROM node:lts-bullseye-slim
RUN npx --yes create-next-app next --use-npm --js --eslint --no-src-dir --experimental-app --import-alias @/*
WORKDIR /next

RUN npm i \
    && npm i --save @date-io/date-fns
```

- The run `docker build -t Temp .` to build that `Dockerfile`
- You should see this line:
> Would you like to use Tailwind CSS with this project? › No / YesRemoving intermediate container 5210306338ee

This means that the line that installs the next app is not successfully executed and that layer is removed from the docker image. Therefore the next lines won't work and we get this error:

> npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /next/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/next/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 


### Describe the Bug

CLI has added an option to use Tailwind CSS. This option needs to be configurable via flags and the corresponding flag is not in the documentation.

### Expected Behavior

To be able to create a Next.js application in an Unattended CLI

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

_No response_

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

_No response_
Repository: PowerToys
Issue: Give folders a one-key comment function
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

- If you have many similar or similar folders, you can add different remarks to them, such as project name, date, and content, so as to distinguish and find them.
- When users want to record information about folders, they can add notes to them, such as source, purpose, and precautions, for reference.

### Scenario when this would be used?

- When users want to add some personalized or interesting tags to folders, they can add comments to them, such as mood, comments, feelings, etc., to add fun and creativity.

### Supporting information

_No response_