sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: svelte
Issue: Layout shift when transitioning between two elements.
Labels: transition/animation

### Describe the problem

When using transitions with a `delay`, the DOM element is created and has a size as soon as the transition starts rather than when the delay is completed.

This causes both elements to take up space o the screen. In particular when wishing to replace one element with another this causes layout shifts.

[This REPL](https://svelte.dev/repl/573ce419b926471992cb2845fea79362?version=3.42.1) demonstrates the issue.

### Describe the proposed solution

The element should not take up space in the document until after the delay has passed. This can alternately be configurable with an option alongside `delay`.

I know this is non-trivial to accomplish with CSS transitions as `display` is not animatable. I don't have a good proposal for technical implementation I'm afraid, at least not one than uses CSS `delay`s.

### Alternatives considered

There are ways to work around this. [Here is one](https://svelte.dev/repl/8292b220aad9434fb70d30a4c03488b1?version=3.42.1).

This workaround introduces another state to avoid mounting the second element until just as the first one is removed. However, it is clunky as it requires another state just to re-implement the functionality of the `delay` passed to `fly`.

Another alternative is a dedicated system of "replacing" one element with another through some transition similar to how `crossfade` is usd to move an element. This, however, seems over the top when the functionality is so very nearly there already.

### Importance

nice to have
Repository: TypeScript
Issue: Very slow typescript autocomplete/intellisense
Labels: Needs Investigation,Rescheduled

*TS Template added by @mjbvz*

**TypeScript Version**: 4.3.5

**Search Terms**
- completions
- intellisense 


---

Does this issue occur when all extensions are disabled?: Yes

Steps to Reproduce:

1. Open any NodeJS-TypeScript project
2. Write the first letter of a class or variable
3. Wait for the intellisense to show

Here's a screen record of the problem:
![Vs](https://user-images.githubusercontent.com/6418354/127800226-3ce84aad-a5c8-4726-814f-7399c2ce77e8.gif)

Version: 1.58.2 (user setup)
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:10:15.214Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.18363
Typescript version: 4.3.5
Repository: pytorch
Issue: [BE] Clean up DDP Single-Program Multi-Device Vestige in reducer.cpp
Labels: oncall: distributed,module: bootcamp

See #47012 for more context. 

There were multiple efforts to remove SPMD mode from DDP (e.g., #55353 #58592). For example, since now there is only one model replica per process, we can simplify the `std::vector<std::vector<at::Tensor>>` to `std::vector<at::Tensor>` and change all the sites using this variable as well. 

https://github.com/pytorch/pytorch/blob/1022443168b5fad55bbd03d087abf574c9d2e9df/torch/csrc/distributed/c10d/reducer.cpp#L74

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd @cbalioglu @gcramer23
Repository: TypeScript
Issue: transpileModule miscompiles const/let to var without renaming, shadowing globals
Labels: Bug

# Bug Report

`typescript.transpileModule` incorrectly compiles `{ const console = 'local'; }`, which does not shadow the global `console`, to `{ var console = 'local'; }`, which does.

### 🔎 Search Terms

transpileModule, const, let, var, rename, scope, shadow, global

(#14542 is possibly related, but that doesn’t show a miscompilation.)

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `transpileModule`

### ⏯ Playground Link

(Playground does not expose `transpileModule`.)

### 💻 Code

```js
const typescript = require("typescript");
const code = "{ const console = 'local'; } console.log('ok')";
const transpiled = typescript.transpileModule(code, {}).outputText;
console.log(transpiled);
eval(transpiled);
```

### 🙁 Actual behavior

```
{
    var console = 'local';
}
console.log('ok');

undefined:4
console.log('ok');
        ^

TypeError: console.log is not a function
    at eval (eval at <anonymous> (/tmp/test.js:5:1), <anonymous>:4:9)
    at Object.<anonymous> (/tmp/test.js:5:1)
    at Module._compile (internal/modules/cjs/loader.js:1072:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
    at Module.load (internal/modules/cjs/loader.js:937:32)
    at Function.Module._load (internal/modules/cjs/loader.js:778:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47
```

### 🙂 Expected behavior

```
{
    var console_1 = 'local';
}
console.log('ok');

ok
```
Repository: neovim
Issue: Support concealing as \t or as multiple characters
Labels: enhancement,display,conceal

### Feature already in Vim?

No

### Feature description

This is sort of related to #1419 but it is not the same thing: elastic tabstops, as I understand it, rely on different text being written in the source file (to use tabs, which will then be rendered more creatively).

What I want to do is render two spaces in the text at the start of lines as a `\t` (which I can then change the width of with ts=), or some other number of spaces as I struggle a *lot* with reading 2-space-indented codebases due to a disability, and there is not much that can be done to avoid reading these, so I want my editor to help me with this by allowing me to visually indent them at a larger size without changing the text content of the file.

This functionality exists in VSCode as an extension that does some funny CSS to render the spaces scaled in width (their approach would not work for nvim of course):
https://marketplace.visualstudio.com/items?itemName=kylepaulsen.stretchy-spaces

Currently, doing something like `:exe "syn match Normal '    ' contained conceal cchar=\t"` does not work as it will throw an "E844: invalid cchar value". I maintain an indent guides plugin that can match leading indents for highlighting purposes, so making this mechanism work with concealing as tabs or multiple characters would achieve the stated goal, I believe.
Repository: storybook
Issue: ArgTypes `table.defaultValue` not showing in MDX ArgsTable on Docs Tab
Labels: bug,has workaround,block: argstable

**Describe the bug**
Defining a default value and description manually using argTypes on the Meta element of an MDX-based Story isn't showing in the ArgsTable on the Docs tab.  It shows both in the control panel of the Canvas tag, but not Docs.

Example
```
<Meta
  title="Theme/QtmThemeProvider"
  component={QtmThemeProvider}
  argTypes={{
    themeSetting: {
      type: 'QtmThemeSetting',
      description: 'Determines what theme should be applied to the application.',
      table: {
        defaultValue: { summary: 'light' }
      },
    }
  }}
/>
```

Docs
![image](https://user-images.githubusercontent.com/8071845/129104220-cd3673ac-92e1-443a-b44c-d136958edbab.png)

Canvas
![image](https://user-images.githubusercontent.com/8071845/129104357-c665e755-635f-43fa-8af9-d075f9abc178.png)

**To Reproduce**
Reproduction repo:  https://github.com/michaelfaith/storybook-mdx-argtype-bug

**System**
```
System:
  OS: Windows 10 10.0.19041
  CPU: (4) x64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Binaries:
  Node: 14.17.5 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.11 - ~\AppData\Roaming\npm\yarn.CMD
  npm: 6.14.14 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Chrome: 92.0.4515.131
  Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.67)
```
Repository: pytorch
Issue: ROCm build documentation lacks needed dependencies
Labels: module: build,module: docs,module: rocm,triaged,actionable

## 📚 Documentation

When following the build from source guide to build the ROCm version of pytorch (see https://github.com/pytorch/pytorch/issues/53738 for why i'm even doing that in the first place), the build will fail for multiple missing dependencies not listed in the guide for building for AMD. There are also a few environment variables that are missing for the build (see https://github.com/pytorch/pytorch/issues/62536) and I had no luck setting `ROCclr_DIR` directly to the config file the build is asking for. I even built is manually following the [AMD guide](https://rocmdocs.amd.com/en/latest/Installation_Guide/HIP-Installation.html#build-rocclr) (which also sets that variable) and pytorch still whines about it not being present when building.

Short list of those I could find were missing from the docs for building:
- `rocblas`
- `rocrand`
- `hipfft`
- `miopen-hip`
- probably others but I gave up after spending 6 hours trying to build the program.

## Potential Solutions

Update the docs to include a **proper** guide to building on ROCm wheels on linux that includes installing dependencies and setting environment variables for the build process

OR

Update the build process to include building wheels for `gfx803` as was intended (I think anyways, it's mentioned in the `LoadHIP.cmake` as a supported architecture) but a small oversight does not allow (again, see https://github.com/pytorch/pytorch/issues/53738 and the corresponding PR to fix it: https://github.com/pytorch/pytorch/pull/54653)


cc @malfet @seemethere @svekars @carljparker @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @walterddr @brianjo @mruberry
Repository: deno
Issue: Array accesses/stores need primordials
Labels: bug,web,runtime

```js
Object.defineProperty(Array.prototype, "0", {
  set: (v) => {
    throw new Error("WTF");
  },
});
console.log("Test");
```

```
Test
error: Uncaught Error: WTF
    throw new Error("WTF");
          ^
    at <anonymous> (file:///home/abotella/test.js:3:11)
```
Repository: go
Issue: io: ReadFull should not forward io.ErrUnexpectedEOF from underlying reader
Labels: NeedsInvestigation

The logic for `io.ReadFull` returns errors from the underlying `io.Reader` verbatim.

In the case where `io.Reader` returns `io.ErrUnexpectedEOF`, it is impossible for the caller of `io.ReadFull` to distinguish between whether:
* the underlying `io.Reader` abruptly ended and is in a truncated state, or
* the underlying `io.Reader` ended correctly and there is no more data.

To avoid this ambiguity, we should wrap any `io.ErrUnexpectedEOF` from the underlying `io.Reader`.

However, I suspect that this is a breaking change and the best that we can hope for is to just document this.

\cc @josharian @catzkorn
Repository: TypeScript
Issue: `Readonly<unknown>` is assignable to type `object`
Labels: Suggestion,Needs Proposal

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

Readonly, unknown, object
<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 Version & Regression Information

4.4.0-beta, 4.3.5, 3.3.3

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.3.5#code/MYewdgzgLgBAhgLhgVzAazCA7mGBeGARgG4AoUSWAI3xgHkqArAU2CgDoAzAJ2eYC9mACjgBKMhWgxgSEE1awCVYkA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
const a: unknown = 1;
const b = Object.freeze(a); // Readonly<unknown>
const c: object = b;
```

### 🙁 Actual behavior

The code compiles with no errors.

### 🙂 Expected behavior

The code fails to compile with error: `Type 'Readonly<unknown>' is not assignable to type 'object'.`.
Since `unknown` is not assignable to `object`, one would expect `Readonly<unknown>` to still be not assignable to `object`.
Repository: go
Issue: proposal: io: add ReaderFunc and WriterFunc
Labels: Proposal,Proposal-Hold

I propose adding the following:
```go
type ReaderFunc func([]byte) (int, error)
func (f ReaderFunc) Read(b []byte) (int, error) {
    return f(b)
}

type WriterFunc func([]byte) (int, error)
func (f WriterFunc ) Write(b []byte) (int, error) {
    return f(b)
}
```

In tests, I find it common that I need an `io.Reader` or `io.Writer` with specialized behavior. Usually, this is only necessary for a single test case within a large table-driven test. In order to have a customized `io.Reader`, I need to declare a concrete type to implement the `Read` method. Since you can only declare a type with methods at the top-level, this results in the declaration potentially being located far away from the code actually using it.

The proposed `ReaderFunc` (and `WriterFunc`) allows me to create an `io.Reader` that 1) requires no named declarations, and 2) have the specialized `Read` behavior inlined with the place that actually plans on using it.

Example usage:
```go
// Cancel the request after the first read to abruptly end the stream.
var calls int
ctx, cancel := context.WithCancel(context.Background())
req, err := http.NewRequest("POST", url, io.ReaderFunc(func(b []byte) (int, error) {
	if calls > 0 {
		cancel()
	}
	calls++
	return copy(b, []byte("whatever")), nil
}))
req = req.WithContext(ctx)
```

This a library-specific workaround to the several proposed language changes (see #21670, #25860, #47487, and many others). Being a non-language change, it is presumably a more palatable change than a full language change. I personally can only recall ever needing something like #21670 for `io.Reader` and `io.Writer`.

This is very similar to the existing [`http.HandlerFunc`](https://pkg.go.dev/net/http#HandlerFunc) type.

\cc @josharian
Repository: godot
Issue: Breakpoint without blank line won't load all local debug variables
Labels: bug,topic:gdscript,topic:editor

### Godot version

3.3.1.stable.official

### System information

Windows 10

### Issue description

When a breakpoint is at the end of an indentation from a for loop it will not display any debug variables that were created within the for loop. 
![image](https://user-images.githubusercontent.com/22126580/129292990-f679f8c4-98ce-4966-89f3-638e903b536a.png)




### Steps to reproduce

add a line of code after a for loop without a blank line in between. Add a breakpoint on a regular line of code and notice the local variables while within a for loop. Move the breakpoint to the last indentation in the for loop. notice all of the variables created within the for loop are missing.

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: split up test/test_autograd.py
Labels: module: autograd,triaged,better-engineering

test/test_autograd.py is around 9400 lines and takes ~10s. It's not too bad. But it would be nice to have some better organization to the code.

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: flutter
Issue: [plugin][iOS] FlutterTextureRegister: unregisterTexture can't release memory
Labels: platform-ios,perf: memory,has reproducible steps,P2,found in release: 2.2,found in release: 2.5,team-ios,triaged-ios

```
__block int64_t textureId = 0;
        __weak __typeof(self)weakSelf = self;
        GLSLRender *glsRender = [[GLSLRender alloc] initWithVertexArray:vertexArray Width:model.cutParam.width Height: model.cutParam.height UpdateCallback:^{
            __strong __typeof(weakSelf)strongSelf = weakSelf;
            [strongSelf.registrar.textures textureFrameAvailable:textureId];
        }];
        textureId = [_registrar.textures registerTexture:glsRender];
        
        result(@(textureId));

[_registrar.textures unregisterTexture:textureId.longLongValue];
```

When I keep creating textureId   because the unregisterTexture: method can’t release the memory, the memory will gradually increase
Repository: flutter
Issue: TextSelection doesn't support TextAffinities for non-collapsed selection
Labels: a: text input,framework,P2,team-framework,triaged-framework

[TextSelection](https://master-api.flutter.dev/flutter/services/TextSelection-class.html) has a single [affinity](https://master-api.flutter.dev/flutter/services/TextSelection/affinity.html) property, and according to its docs, it only applies when collapsed:

> If the text range is collapsed and has more than one visual location (e.g., occurs at a line break), which of the two locations to use when painting the caret.

I think that this may be an oversight and a source of bugs, especially when using a keyboard.  For example, these selections are different, but Flutter has no way to distinguish between the two:

<table>
  <tr>
    <th>extent TextAffinity.downstream</th>
    <th>extent TextAffinity.upstream</th>
    <th>Flutter treats them both as:</th>
  </tr>
  <tr>
    <td>
<pre>
This text wra|ps because it's
|too long.
</pre>
    </td>
    <td>
<pre>
This text wra|ps because it's |
too long.
</pre>
    </td>
    <td><img width="314" alt="Screen Shot 2021-08-12 at 6 32 07 PM" src="https://user-images.githubusercontent.com/389558/129292344-403ad8a3-5c72-48c1-9086-67837ff2bdd6.png"></td>
  </tr>
</table>

### Why does it matter?

When using keyboard shortcuts that jump to the beginning/end of a line, it's important to know what line the base and extent are on.  Consider doing cmd-shift-right (expand to end of line) in my example in the table above.  If the extent is upstream, the selection shouldn't change.  If it's downstream, it should select to the end fo the field.  Always assuming one or the other affinity won't always make sense.

### Related
https://github.com/flutter/flutter/pull/87973/files#r685632915
https://github.com/flutter/flutter/pull/85653
Repository: pytorch
Issue: document our compatibility with upstream packages (e.g. languages, compilers, tools)
Labels: module: docs,triaged

Not too infrequently, people ask questions like we can use C++17 or some feature in a newer version of Python. We have a rough methodology for addressing these questions, but it's not documented anywhere and it might mean different things to different people.

Writing this down serves several purposes:
1) it forces us to get on the same page about the policy
2) it is handy to point people to when the question inevitably recurs
3) it aids in planning: looking at the document we ought to be able to identify a rough date when some feature or library can be taken advantage of. That can assist in evaluating tradeoffs, timing prep work to take advantage of a particular feature, or deciding whether we want to live with a suboptimal situation that can be resolved by a future upgrade.


cc @brianjo @mruberry
Repository: PowerToys
Issue: [powertoys run] add time calculation (days:hours:minutes)
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

### Description of the new feature / enhancement

do time calculation with powertoys run,so i can easily plan how much time i have to spend per day
form be like (1:00*3+55:38+49:42+1:01:26)/30=
and show result in multiple form
prototype:
![image](https://user-images.githubusercontent.com/61088063/129299965-c0110881-e0fa-4722-9ef4-317a93c59e89.png)
feature list:
- calculate time with the form of xx:xx:xx+xx:xx:xx-xx:xx:xx
- plus,minus and multiplication for calculate the amount of time, and division for result the average time per day
- full width colon support(https://github.com/microsoft/PowerToys/issues/12664)
- show multiple form of result(nice to have)

### Scenario when this would be used?

I want it because i'm planning my online course to know how many hours/minutes i have to watch,so i can finish the course in this month.

### Supporting information

_No response_
Repository: pytorch
Issue: Memory leak in `ddp_zero_hook.py` hooks
Labels: module: memory usage,triaged,module: ddp

There is a memory leak that occurs due to referencing the `ddp: DistributedDataParallel` variable in `hook_with_zero_step()` and `hook_with_zero_step_interleaved()` (namely, the reference count for model parameters and other internal variables like the `_DDPBucketAssignment`s remain positive when they should have reached zero). The temporary solution is to convert `ddp` variable to a weak reference `ddp_ref`. See https://github.com/pytorch/pytorch/pull/63162#discussion_r688137351. We should investigate why this weak reference fixes the memory leak and/or devise a permanent fix.

I noticed the memory leak when `torch.cuda.max_memory_allocated()` was steadily increasing when running models back-to-back in cases where it should have stayed flat. The following function was useful for seeing some of the objects that were not being garbage collected:
```
import gc
def check_gc():
    if dist.get_rank() == 0:
        for obj in gc.get_objects():
            try:
                if torch.is_tensor(obj) or (hasattr(obj, 'data') \
                    and torch.is_tensor(obj.data)):
                    print(
                        f"obj {id(obj)} of type {type(obj)} "
                        f"with size {obj.size()} has "
                        f"{sys.getrefcount(obj)} refs"
                    )
            except:
                pass
            try:
                if isinstance(obj, _DDPBucketAssignment):
                    print(f"{obj} has {sys.getrefcount(obj)} refs")
            except:
                pass
```
Repository: pytorch
Issue: Torch.nn.functional.interpolate() function memory release problem
Labels: module: memory usage,triaged,module: interpolation

## questions：
 for some reason, I have to use (pytorch 1.3.0 and torchvision 0.2.1), When I use torch.nn.functional.interpolate(), I find that the memory usage keeps increasing. After consulting the data, I found that the torch.nn.functional.interpolate() corresponding to pytorch1.3 version does not support empty batch sizes. I don’t know if it is It is not this problem that the memory ratio of my deep learning model keeps increasing at runtime, so can I simply rewrite this function so that it supports empty batch sizes?
## Environment:
This is my server environment configuration
![image](https://user-images.githubusercontent.com/47623700/129312802-6ad60733-51dc-4683-8b3f-1cf8d5423a99.png)