sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: flutter --version fails when offline
Labels: tool,platform-mac,has reproducible steps,P2,found in release: 2.8,team-tool,triaged-tool

## Repro steps

1. Download a stable macOS build from the releases page: https://docs.flutter.dev/development/tools/sdk/releases

2. Go offline (turn off wifi and anyther other network connection)

3. Extract the downloaded zip (e.g. ~/tmp/flutter)

4. Open a terminal, and run `~/tmp/flutter/bin/flutter --version`

## Actual result

```
$ ~/tmp/flutter/bin/flutter --version
VersionCheckError: Command exited with code 128: git fetch
__flutter_version_check__ stable
Standard error: fatal: unable to access
'https://github.com/flutter/flutter.git/': Could not resolve host: github.com

Flutter 2.8.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 77d935af4d (3 weeks ago) • 2021-12-16 08:37:33 -0800
Engine • revision 890a5fca2e
Tools • Dart 2.15.1
mit-macbookpro4:~ mit$
```

## Expected result|

No error.
Repository: pytorch
Issue: Rewrite tests in test_nn to not depend on LAPACK
Labels: module: nn,module: tests,triaged,actionable

Several tests in `test/test_nn.py` depend on pytorch to be compiled with LAPACK support.

These tests should be rewritten using a set of functions not depending on LAPACK so that they can be run in any configuration, and the temporary `@skipIfNoLapack` should be removed for rewritten tests.

The tests in question are:

- [ ] test_register_and_remove_parametrization
- [ ] test_serialization_parametrization
- [ ] test_initialization_parametrization
- [ ] test_multiple_inputs_parametrization
- [ ] test_caching_parametrization

See #70913 for the discussion of the issue.

@albanD @Lezcano 


cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: angular
Issue: Ivy: Render HTML from String / dynamic rendering
Labels: feature,area: core,area: compiler,feature: under consideration,compiler: jit

### Which @angular/* package(s) are relevant/releated to the feature request?

compiler, core, platform-browser-dynamic, platform-browser

### Description

As far as I know the old aproach was to inject the JITCompiler and use it to render your HTML in an anonymous component.
This worked so far. I use editable HTML in DB which uses key features as substituting variables and directives like *ngIf or  *ngSwitch.

Which does not work anymore in production mode (Angular 12.x)
I browsed stackoverflow and other forums to find an workarround for this and these are not working anymore (like loading the JITCompiler into Providers, which results in  "JIT Compiler unavailable". 
 
As I found not soulution for ivy/ng 12 i considered this feature as still missing. 

Best,

Malte


### Proposed solution

Component to render html strings.

Example:
``` Html
<render-component [html]="..." [render-data]="{ show: true}></render-component>
````

[html] has the following value:
``` Javascript
"<p *ngIf=\"show\">Hello!</p>"
```

Which display in the case if show is true:

``` Html
<p>Hello!</p>
```



### Alternatives considered

An Service to render html on the fly.


E.g.:

[p3x-compile](https://github.com/patrikx3/angular-compile)
[Html Compile](https://github.com/codehint-ng/ng-controls/blob/master/projects/html-compiler/src/lib/html-compiler.component.ts)
Repository: rust
Issue: Tracking Issue for `panic::update_hook`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(panic_update_hook)]`

This is a tracking issue for the `panic::update_hook` function.

This function allows creating panic hooks that forward the call to the previously set panic hook, without race conditions. It works by taking a closure that receives the old panic hook and the panic info, and it is atomically set as the panic hook by ensuring that during the execution of `panic::update_hook` no other thread can modify the panic hook.

This common use case:

```rust
let prev = panic::take_hook();
panic::set_hook(Box::new(move |info| {
    println!("panic handler A");
    prev(info);
}));
```

Becomes:

```rust
panic::update_hook(|prev, info| {
    println!("panic handler A");
    prev(info);
});
```

Using the old approach is fine if there is some guarantee that there are no other threads trying to change the panic hook. The main goal of this feature is to enable the use case of safely adding panic hooks after the application has been initialized, because the existing functions `panic::set_hook` and `panic::take_hook` are not enough to implement that, consider this case:

*    Thread A calls `panic::take_hook()`
*    Thread B calls `panic::take_hook()`
*    Thread A calls `panic::set_hook()`
*    Thread B calls `panic::set_hook()`

And the result is that the original panic hook has been lost, as well as the panic hook set by thread A. The resulting panic hook will be the one set by thread B, which forwards to the default panic hook. Using the new `panic::update_hook` function, this race condition is impossible, and the result will be either `A, B, original` or `B, A, original`.

### Public API

```rust
// std::panic

pub fn update_hook<F>(hook_fn: F)
where
    F: Fn(&(dyn Fn(&PanicInfo<'_>) + Send + Sync + 'static), &PanicInfo<'_>)
        + Sync
        + Send
        + 'static,
```

### Steps / History

- [x] Implementation: #92598
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions


- Is the API flexible enough for most use cases? For example it is not possible to drop the previous handler, but if the user wanted to replace the old handler they could just use `panic::set_hook`. An alternative implementation is to take a closure that creates a panic handler, like this (available in commit 8bdf5c3de6c6e4e01f7f6241cd0f2a606c7486df):

```rust
panic::update_hook(|prev| {
    Box::new(move |info| {
        println!("panic handler A");
        prev(info);
    })
});
```

That approach should be more flexible because it transfers ownership to the closure, but if the outermost closure panics the error message is "panicked while processing panic" which is not nice. This is a consequence of holding the `HOOK_LOCK` while executing the closure. Could be avoided using catch_unwind?
Repository: transformers
Issue: [JAX/FLAX]: CLM Tokenizer Training confusion
Labels: WIP

Hi,

after looking at the current readme of the [CLM tokenizer training example](https://github.com/huggingface/transformers/tree/master/examples/flax/language-modeling#train-tokenizer-1), there's something strange in the model configuration:

The `config.json` file looks like this:

```json
GPT2Config {
  "_name_or_path": "./",
  "activation_function": "gelu_new",
  "architectures": [
    "GPT2LMHeadModel"
  ],
  "attn_pdrop": 0.0,
  "bos_token_id": 50256,
  "embd_pdrop": 0.0,
  "eos_token_id": 50256,
  "initializer_range": 0.02,
  "layer_norm_epsilon": 1e-05,
  "model_type": "gpt2",
  "n_ctx": 1024,
  "n_embd": 768,
  "n_head": 12,
  "n_inner": null,
  "n_layer": 12,
  "n_positions": 1024,
  "reorder_and_upcast_attn": false,
  "resid_pdrop": 0.0,
  "scale_attn_by_inverse_layer_idx": false,
  "scale_attn_weights": true,
  "summary_activation": null,
  "summary_first_dropout": 0.1,
  "summary_proj_to_labels": true,
  "summary_type": "cls_index",
  "summary_use_proj": true,
  "task_specific_params": {
    "text-generation": {
      "do_sample": true,
      "max_length": 50
    }
  },
  "transformers_version": "4.16.0.dev0",
  "use_cache": true,
  "vocab_size": 50257
}

```

Vocab size is 50257, and `eos_token_id` is set to 50256. I think that setting `eos_token_id` is wrong, because of the following example:

```bash
In [10]: tokenizer.convert_ids_to_tokens([1797, 705, 225, 50256])
Out[10]: ['hal', 'lo', 'Ġ', 'Ġgeestigheid']
```

Id *50256* is originally set to `'Ġgeestigheid'`. I'm not 100% sure, but it should be set to 50257 (and thus outside the vocabulary), because of:

```bash
In [7]: tokenizer.encode("hallo 
")
Out[7]: [1797, 705, 225, 50257]
```

It shows that `eos_token` is set to `
` and from the tokenizer part, `eos_token_id` then should be set to `50257`?!

Now I'm using the official GPT-2 model as reference:

It uses `"eos_token_id": 50256` in the `config.json` file, some tokenizer tests:

```bash
In [6]: tokenizer.eos_token
Out[6]: '
'

In [7]: tokenizer.eos_token_id
Out[7]: 50256

In [8]: tokenizer.encode("Hello 
")
Out[8]: [15496, 220, 50256]
```

Which is correct.

And there's another issue: after looking at the `tokenizer.json` file for GPT-2, the following entry exists:

```bash
"
":50256}
```

which is perfect, but: for the own trained vocab this entry does not exist! I'm not sure if this is a bug in the Tokenizers library or intended :thinking:
Repository: godot
Issue: `ProjectSettings.set_initial_value()` does not set a setting's default value when queried via `get_setting()`
Labels: discussion,topic:core,topic:editor,confirmed,topic:plugin

### Godot version

4.0.dev (8f6cba3a4)

### System information

Fedora 34, GeForce GTX 1080 (NVIDIA 495.46)

### Issue description

`ProjectSettings.set_initial_value()` does not set a setting's default value when queried via `get_setting()`. This likely happens because the setting is not persisted to `project.godot` when its value is equal to the default. One way to address this would be to always save custom settings' values to `project.godot`, even if they are equal to the default value.

I'm not sure whether this is a bug or design decision. Either way, this should be documented in the class reference. See https://github.com/godotengine/godot-docs/issues/5497#issuecomment-1006771969 where I originally mentioned this.

### Steps to reproduce

- Create an editor plugin.
- In the plugin main script's `_enter_tree()` function, define a new project setting: https://github.com/Calinou/godot-photo-mode-demo/blob/5029be379192d736d34d270f1c7696f19ec6de29/addons/photo_mode/plugin.gd
- In another script, get the project setting's value: https://github.com/Calinou/godot-photo-mode-demo/blob/5029be379192d736d34d270f1c7696f19ec6de29/addons/photo_mode/photo_mode.gd#L238-L244
- The initial value is not returned if the value is not saved to `project.godot`. This occurs if the value is not changed from its default. The setting defined here defaults to `true`, but `null` will be returned (and converted to `false` with `bool()`) if the setting is not persisted to `project.godot`.

### Minimal reproduction project

https://github.com/Calinou/godot-photo-mode-demo
I can make a more minimal reproduction project if needed.
Repository: godot
Issue: Vulkan: Error spam when mixing Spot and Omni Lights and Shadows
Labels: bug,topic:rendering,topic:3d

### Godot version

v4.0.dev.20220105.official [8f6cba3a4]

### System information

Windows 11, Vulkan, Nvidia Quadro K2000 472.84

### Issue description

When using both Omni and Spot lights with shadows on, once you go get past the available shadow map slots, as you change which shadows are in the Shadow Map, you can end up getting an error spam of `servers/rendering/renderer_rd/renderer_scene_render_rd.h:1188 - Condition "!li->shadow_atlases.has(p_shadow_atlas)" is true. Returning: 0` and the lights start getting assigned the wrong shadows from the shadow map.

This is probably because Omni lights take 2 spots in the Shadow map, and Spot lights take only 1, and as you're changing the Shadow Map atlas configuration it panics when omni light cannot get the 2nd Shadow Map to be right after the 1st Shadow Map in the Shadow Map Atlas.


### Steps to reproduce

Open MRP in Editor
toggle visibility of the hidden omni light. Hide it, and unhide the spot light. Unhide the omni light -> Error

### Minimal reproduction project

[Bug.zip](https://github.com/godotengine/godot/files/7830368/Bug.zip)
Repository: youtube-dl
Issue: How to get started with Moderation? 
Labels: question

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones

Dear Community, 
this project has blown my mind every time I used it. To give back to the community I would like to donate my time to support this project. While I can program python, I would rather start with moderation at the beginning. I did some search, but could not find "moderation guidelines". Are there any? If not, can I just start and improve by doing?
Repository: vscode
Issue: Show results for "Go to symbol in workspace" incrementally
Labels: feature-request,workspace-symbols

<!-- ⚠️⚠️ 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. -->
When having multiple language servers, it would be useful to show results for "Go to symbol in workspace" as soon as they are available instead of waiting for all language servers to be done providing theirs. This is similar to what was done for hover providers in #137714.

Why is this needed? I'm using both clangd and the python language server at the same time. When using "Go to symbol in workspace" to look up a C++ symbol, clangd provides results almost instantly. However, pylance takes forever to provide symbols (on the order of minutes, not seconds), which makes the feature basically unusable for looking up C++ symbols, unless I disable the python language server.

I do realize that this may have many of the same problems mentioned in the similar request for completion (see https://github.com/microsoft/vscode/issues/107343#issuecomment-698195033), so suggestions for other workarounds would be much appreciated.
Repository: PowerToys
Issue: Listing of currently assigned activation shortcuts for PT utilities
Labels: Idea-Enhancement,Product-Settings,Cost-Large

### Description of the new feature / enhancement

This feature would produce a listing (printer-friendly optionally) of the currently assigned shortcuts for the utilities. Could be placed in the General section, or even become a utility of its own.

### Scenario when this would be used?

Instead of going to each utility separately to view the current activation shortcut for each, this would produce a succinct list that can be used as a quick refresher, and can optionally be printed. Would also assist when contemplating what activation shortcuts are not already in use when desiring to change the shortcut for one of the utilities.

### Supporting information

_No response_
Repository: neovim
Issue: nvim -e attempts to redraw lines and provide line editing even though TERM is dumb
Labels: bug,startup

### Neovim version (nvim -v)

0.6.1

### Vim (not Nvim) behaves the same?

no, Vim 8.2.3995

### Operating system/version

Debian unstable/amd64

### Terminal name/version

None (ssh localhost)

### $TERM environment variable

dumb

### Installation

Debian unstable

### How to reproduce the issue

ssh localhost nvim --clean -e ~/.config/nvim/init.vim
" Look at the screen.
:p


### Expected behavior

Expected rendering:

```
:p
" vim: set ts=2 sw=2 sts=2:
```

Neovim is line-buffered and does not start a UI or attempt to use complex cursor movements because `$TERM` is `dumb` and there is no TTY.  (It should not attempt to do those things even when `$TERM` is _not_ `dumb` because those are not appropriate for `ex` mode.) Like Vim (and `nvi -e`), ex mode can be used to edit a file without a TTY present.

Note: `nvim -es` is not suitable for this because when there _is_ a TTY, it exits immediately instead of reading from the standard input.  Also, `vim -e` works just fine without `-s`.

This is actually difficult behavior to get right because ex mode is rarely used interactively, but it is extremely useful in an emergency or when a TTY is not available.  Vim previously did not line-buffer in this case, which I patched, and now it works as expected.

### Actual behavior

Notice that at the beginning, `:ntering Ex mode.  Type "visual" to go to Normal mode.` is printed.  That is, the message is printed and then the prompt is printed over it.  Then, after typing `:p`, the following appears on the screen:

```
:ptering Ex mode.  Type "visual" to go to Normal mode.
" vim: set ts=2 sw=2 sts=2:
:
Entering Ex mode.  Type "visual" to go to Normal mode.
:p
```

It appears that Neovim is trying to do some sort of redrawing of the screen or provide interactive line editing, but that's not going to work since there's no TTY.
Repository: TypeScript
Issue: Extra check in expression cause invalid type narrowing
Labels: Bug,Help Wanted

# Bug Report

Invalid type narrowing seems to bleed out of expressions that includes "useless" checks, such as :  
- checking the existence of a property marked as required
- using optional chaining when the variable is never null

### 🔎 Search Terms

- invalid type narrowing
- extra condition narrowing

### 🕗 Version & Regression Information

Tested in  `4.4.4`, `4.5.4` and `4.6.0-dev.20220107`  
This seems to be the behavior in every version I tried, and I didn't find any relevant point if the FAQ

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/C4TwDgpgBAglC8UDeUCGAuKBnYAnAlgHYDmUAvgNwBQokUAQgsmpjgSRVAEat5GmUqVAPTCoAdXzAAFlACuWCABsIWLFAAGAclRaoRKAA8NVACYQAxktS5oFgPaEcUAG6olciAEZMcAD4M1Dp6Bm4e3lAAZJFQWlwhhK7unl5RMWEpAHRcQbr6iRkR0bHx+UnhqcWFXtmcolAAori49rhC9ZIy8ooqalD2YMD4joTuUBbSqET8ZpbWtuOOzoUATL5QAfRBpaHJECtp5Z4rAPy1VHEJR-uHq7VQ9U0tbUA)

### 💻 Code

```ts
type A = { a: string };
type B = { a: string; b: string };

// With useless `'a' in x`
declare const value1: A | B;
'a' in value1 && 'b' in value1 && value1.b;
'a' in value1 && 'b' in value1 && value1.b; // Error

// With useless optionnal chaining
declare const value2: A | B;
'b' in value2 && value2?.b;
'b' in value2 && value2.b; // Error
```

### 🙁 Actual behavior

In both case, we get the error `Property 'b' does not exist on type 'never'.(2339)`  
The variable is narrowed to `A` after the first expression, which cause the next one to fail.

### 🙂 Expected behavior

No type narrowing should occur outside of the expressions.
Repository: flutter
Issue: [fuchsia] Support upstream buffer collection extension.
Labels: engine,platform-fuchsia,P2,team-engine,triaged-engine

Fuchsia tree has updated to support the upstream Khronos version of its buffer collection extension, and we will remove the transitional FUCHSIAX extension. All clients should move to the upstream extension instead.

Parent bug: fxbug.dev/90828

@akbiggs @arbreng FYI
Repository: storybook
Issue: VueJS v2 w/ TSX - Storybook only acknowledges the JSDoc @slot block when it's inside/on the render function
Labels: bug,help wanted,vue

**Describe the bug**
When rendering a slot (default or otherwise) outside of a `render` function, the slot is not represented in the "Slots" section of the docs and any description added is ignored.

**To Reproduce**
Environment:
- Vue 2.16.2
- TypeScript 4.2.2
- storybook/vue 6.3.6
- TSX-based Vue components (w/ `render` functions instead of templates)

Simplified example of a Vue component w/ a slot that does not render in the Storybook output:
```
// foo-bar.tsx
import Vue from 'vue';

export const Link = Vue.extend({
  name: 'foo-bar',

  computed: {
    renderedElement(): JSX.Element {
      const Element = 'div';

      return (
        <Element>
          {
            /**
             * @slot Default The content (usually text).
             */
            this.$slots.default
          }
        </Element>
      );
    },
  },

  render(): JSX.Element {
    return this.renderedElement;
  },
});
```

```
//foo-bar.stories.ts
// (c) 2022 Cofense Inc.
import { Meta, Story } from '@storybook/vue';
import { FooBar } from '.';

export default {
  title: 'FooBar',
  component: FooBar,

  argTypes: {
    // Slots
    default: {
      control: 'text',
    },
  },

  args: {
    // Slots
    default: 'Test',
  },
} as Meta;

const Template: Story = (args, { argTypes: { default: slot, ...props } }) => ({
  components: { FooBar },
  props: Object.keys(props),
  template: `
    <foo-bar v-bind="$props">${args.default}</koi-link>
  `,
});

export const All = Template.bind({});
```

This produces storybook output of:
<img width="1007" alt="Screen Shot 2022-01-07 at 3 30 29 PM" src="https://user-images.githubusercontent.com/593312/148610122-d39e6ad5-7036-445a-a1e1-badb3cd8b1b7.png">

Notice how the slot is represented as a prop and the description from the component is ignored.
Repository: go
Issue: runtime: traceback throw from VDSO reachable via raw asmcgocall
Labels: NeedsFix,compiler/runtime

This split from https://github.com/golang/go/issues/49182#issuecomment-996242310.

On 386, `__kernel_vsyscall` is reachable from [`cgo_start_thread`](https://cs.opensource.google/go/go/+/master:src/runtime/proc.go;l=2255;drc=9b0de0854d5a5655890ef0b2b9052da2541182a3), which is called via `asmcgocall`.

The signal handler won't properly detect raw `asmcgocall` calls as cgo calls because `sighandler` checks [`g.m.incgo`](https://cs.opensource.google/go/go/+/master:src/runtime/signal_unix.go;l=690;drc=master), which is only set in `cgocall`.

I believe the correct approach here is to push `g.m.incgo` (and probably `g.m.ncgo`) adjustments from `cgocall` to `asmcgocall`.
Repository: pytorch
Issue: Skip LSTM quantization by default in get_default_qconfig_dict and get_default_qat_qconfig_dict
Labels: oncall: quantization,low priority,triaged

### 🐛 Describe the bug

Looks like LSTM is not supported right now, we should skip this in the get_default_qconfig_dict function. There was some PR before from @z-a-f that tries to enable this by default, but it's probably not landed.

### Versions

master

cc @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @jerryzh168
Repository: PowerToys
Issue: [Run][New Plugin] Have the ability to draft Outlook invites
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Imagine you type something into the Run box that’s like “schedule a meeting for 2pm tomorrow with Brian,” and it automatically will be able to parse the request and create an Outlook invite draft. Ultimately, it would be cool to make this even more extensible and do it for any generic "intent."

### Scenario when this would be used?

Currently, the flow to create new drafts is open Outlook --> Go to calendar page --> Click on "New Appointment" --> Select a time --> Add attendees, whereas with this UI flow, it could be a single line command.

### Supporting information

_No response_