sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: inductor guards on 32 bit indexing even when generated code would be the same
Labels: triaged,oncall: pt2,module: inductor

I'm trying out some example compiled snippets to see what "32-bit indexing guards in the backward" will look like. One thing I noticed is that in this simple example:
```
import torch

class MyFunc(torch.autograd.Function):
    @staticmethod
    def forward(ctx, x):
        return x

    @staticmethod
    def backward(ctx, grad_x):
        return grad_x + grad_x

def f(x):
    return MyFunc.apply(x)


f_compiled = torch.compile(f, dynamic=True)

x_ref = torch.randn(4, 5, device='cuda', dtype=torch.float16, requires_grad=True)
x_test = x_ref.clone().detach().requires_grad_()

out_ref = f(x_ref)
out_ref.sum().backward()

out_test = f(x_test)
out_test.sum().backward()

x_ref2 = torch.randn(47000, 47001, device='cuda', dtype=torch.float16, requires_grad=True)
x_test2 = x_ref2.clone().detach().requires_grad_()

out_ref2 = f(x_ref2)
out_ref2.sum().backward()

out_test2 = f_compiled(x_test2)
out_test2.sum().backward()
```

we generate 32 bit indexing guards [here](https://github.com/pytorch/pytorch/blob/c35b9535319b9ba0b0a0c759759bfce2ff387e01/torch/_inductor/codegen/simd.py#L1200) during inductor compilation. But when I re-run with inputs that invalidate the guards and check the generated inductor code, it looks identical.

Is there a reason we unconditionally generate these guards, and would it be possible to figure out how to only generate them when they would cause inductor to actually generate different code?

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: flutter
Issue: [google_maps_flutter] `setAndGetScrollPosition` failing on iOS
Labels: team,platform-ios,p: maps,package,team-ecosystem,P2,c: disabled test,c: flake,triaged-ecosystem

I'm seeing persistent, but seemingly slightly flaky in how it manifests, failures in `setAndGetScrollPosition` in `webview_flutter` and `webview_flutter_wkwebview` in post-submit, closing the tree. It's showing up in [this commit](https://github.com/flutter/packages/pull/7599), but since presubmit past, while postsubmit failed four times in a row, it seems like maybe it's OOB rather than from the roll? Or it's flake and presubmit was just lucky.

I'm going to disable these test for now to re-open the tree. /cc @bparrishMines
Repository: TypeScript
Issue: function members of primitives/builtins are not read-only
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

builtin number string member readonly

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about "Common Bugs that arent Bugs"


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.5.4&ssl=6&ssc=1&pln=1&pc=1#code/DYUwLgBAHhC8ECYDcAoKA6AbgQ2AVxAHkAzOCACgQEotcCTUVRIBPMgIgAsRhgB7dqhboAxp2wAnAIKR4wsZJmogA

### 💻 Code

```ts
let x = 2;
x.valueOf = (2).valueOf;

let y = "hello";
y.charAt = y.charAt;
```


### 🙁 Actual behavior

Code compiles just fine, even with `--strict` enabled.
Executing JavaScript fails: 
```
can't assign to property "valueOf" on 2: not an object 
```

### 🙂 Expected behavior

Should be rejected by tsc as read-only assignment.

### Additional information about the issue

Seems similar in nature to https://github.com/microsoft/TypeScript/issues/49113
Notably, array.length is allowed (because its legal in JS) but string.length is not (because it is illegal in JS). Since assigning to builtin functions is also illegal, this should be flagged by tsc.
Repository: neovim
Issue: Windows: log reports os_set_cloexec errors
Labels: bug,platform:windows,complexity:low,system

### Problem

Error message in `stdpath('state')/log`:

```text
ERR 2024-09-06T14:02:44.657 nvim.4691.0 os_set_cloexec:493: Failed to get flags on descriptor 3: Bad file descriptor
ERR 2024-09-08T17:28:53.165 nvim.7615.0 os_set_cloexec:493: Failed to get flags on descriptor 3: Bad file descriptor
ERR 2024-09-08T17:34:26.677 nvim.7727.0 os_set_cloexec:493: Failed to get flags on descriptor 3: Bad file descriptor
ERR 2024-09-08T20:50:49.236 nvim.15229.0 os_set_cloexec:493: Failed to get flags on descriptor 3: Bad file descriptor
ERR 2024-09-08T21:30:31.562 nvim.15321.0 os_set_cloexec:493: Failed to get flags on descriptor 3: Bad file descriptor
ERR 2024-09-09T00:42:07.227 nvim.15536.0 os_set_cloexec:493: Failed to get flags on descriptor 3: Bad file descriptor
```

### Steps to reproduce

not applicable

### Expected behavior

does not report error

### Neovim version (nvim -v)

0.10.1

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

not applicable

### Operating system/version

WSL2 Ubuntu 22.04

### Terminal name/version

Windows Terminal 1.22.2362.0

### $TERM environment variable

xterm-256color

### Installation

appimage
Repository: vscode
Issue: Support for Inline Diff view in addition to Side by Side
Labels: feature-request,notebook-diff

This feature is requrest in [jupyterlab,](https://github.com/jupyterlab/jupyterlab-git/issues/1076) and I find it useful in jupyter for vscode as well, so I paste it here. 

It would be great to be able to switch to an inline diff view in addition to the default side by side diff view.

Here is an example of this feature implemented in VS Code. Thanks!

![image](https://github.com/user-attachments/assets/d4db6168-2ea5-4042-b2b9-9f29bb32caa8)
Repository: ui
Issue: [bug]: Mixed indentations in the same file
Labels: bug

### Describe the bug

When you follow the instructions and install the library, `tailwind.config.{js,ts}` file you're getting at the end has both space and tab indentations in the same file, even on the same line. Which causes linters/checkers go crazy. 

<img width="493" alt="image" src="https://github.com/user-attachments/assets/0389b1a2-f7fd-4a5a-82f1-cefdf8d3bdcf">


### Affected component/components

tailwind.config.{js,ts}

### How to reproduce

```bash
$ npx shadcn@latest init
npm warn exec The following package was not found and will be installed: shadcn@2.0.5
✔ The path /Users/gokaygurcan/projects/test is does not contain a package.json file. Would you like to start a new Next.js project? … yes
✔ What is your project named? … my-app
- Creating a new Next.js project. This may take a few minutes.
✔ Creating a new Next.js project.
✔ Which style would you like to use? › Default
✔ Which color would you like to use as the base color? › Neutral
✔ Would you like to use CSS variables for theming? … no / yes
- Writing components.json.
✔ Writing components.json.
- Checking registry.
✔ Checking registry.
- Updating tailwind.config.ts
✔ Updating tailwind.config.ts
- Updating app/globals.css
✔ Updating app/globals.css
- Installing dependencies.
✔ Installing dependencies.
- Updating files.
✔ Created 1 file:
  - lib/utils.ts

Success! Project initialization completed.
You may now add components.
```

### Codesandbox/StackBlitz link

https://codesandbox.io/p/devbox/3r49z4?file=%2Fmy-app%2Ftailwind.config.ts

### Logs

```bash
N/A
```


### System Info

```bash
OS: macOS 14.6.1 23G93 arm64
Shell: zsh 5.9
Terminal: Apple_Terminal

NPM: v10.8.2
Node: v20.17.0
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: tauri
Issue: [bug] Mouse Back/Forward buttons dont work on macOS
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

This is related to https://github.com/tauri-apps/tauri/issues/4019

Special mouse buttons like back/forward are not working on macOS. They work fine on Windows and Linux

### Reproduction

Start a new app `npm create tauri-app@latest -- --rc` and add this:

```ts
window.addEventListener("mousedown", console.log)
```

### Expected behavior

It should log something on macOS, like it does on Windows and Linux, but it doesn't

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.6.1 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 22.4.0
    - pnpm: 8.6.12
    - yarn: 1.22.19
    - npm: 10.8.1
    - bun: 1.1.6

[-] Packages
    - tauri 🦀: 2.0.0-rc.10
    - tauri-build 🦀: 2.0.0-rc.9
    - wry 🦀: 0.43.1
    - tao 🦀: 0.30.0
    - @tauri-apps/api : 2.0.0-rc.4
    - @tauri-apps/cli : 2.0.0-rc.12

[-] Plugins
    - tauri-plugin-dialog 🦀: 2.0.0-rc.5
    - @tauri-apps/plugin-dialog : 2.0.0-rc.1
    - tauri-plugin-log 🦀: 2.0.0-rc.2
    - @tauri-apps/plugin-log : 2.0.0-rc.1
    - tauri-plugin-os 🦀: 2.0.0-rc.1
    - @tauri-apps/plugin-os : 2.0.0-rc.1
    - tauri-plugin-fs 🦀: 2.0.0-rc.3
    - @tauri-apps/plugin-fs : 2.0.0-rc.2
    - tauri-plugin-shell 🦀: 2.0.0-rc.3
    - @tauri-apps/plugin-shell : 2.0.0-rc.1
    - tauri-plugin-updater 🦀: 2.0.0-rc.3
    - @tauri-apps/plugin-updater : 2.0.0-rc.2
    - tauri-plugin-window-state 🦀: 2.0.0-rc.3
    - @tauri-apps/plugin-window-state : not installed!

[-] App
    - build-type: bundle
    - CSP: default-src 'self' data:; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval';; connect-src ipc: http://ipc.localhost
    - frontendDist: ../dist
    - devUrl: http://localhost:5173/
    - framework: SolidJS
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ui
Issue: [bug]: Getting no import alias found for Adonis Inertia Project(mistakenly recognize as Remix project)
Labels: bug

### Describe the bug

I'm encountering an error with the import alias configuration in my `tsconfig.json` file on an https://github.com/adonisjs/inertia-starter-kit project. The message shown is:
`No import alias found in your tsconfig.json file. Visit https://ui.shadcn.com/docs/installation/remix to learn how to set an import alias.`


Here is my current `tsconfig.json` file:

```json
{
  "extends": "@adonisjs/tsconfig/tsconfig.app.json",
  "compilerOptions": {
    "rootDir": "./",
    "outDir": "./build",
    "baseUrl": "./",
    "paths": {
      "@/*": [ "./src/*" ] // Should always point to src
      // "@/*": [ "./inertia/*" ] --> This doesn't work
    }
  },
  "exclude": [
    "./inertia/**/*",
    "node_modules",
    "build"
  ]
}
```
It seems like the issue could be related to this [lines](https://github.com/shadcn-ui/ui/blob/f4ca57a79cf2d56f9c55021242a55cf0e1018b72/packages/shadcn/src/utils/get-project-info.ts#L31) of code in 


### Affected component/components

project initialization

### How to reproduce

1. npm init adonisjs@latest
2. setup tailwind as per docs
3. npx shadcn@latest init

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Ubuntu 22.04 node 22
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: Godot crash when trying to return project window (Linux, Nvidia driver 560 regression)
Labels: bug,platform:linuxbsd,topic:rendering,needs testing,crash

### Tested versions

Engine version: Godot Engine v4.3.stable.official (77dcf97d82cbfe4e4615475fa52ca03da645dbd8)

### System information

Godot v4.3.stable - Kubuntu 24.04.1 LTS 24.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 - Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 Threads)

### Issue description

After opened any project couldn't return to projects list

### Steps to reproduce

1. Open godot.
2. Open any project.
3. Select Project -> Exit to projects list.

Get error in console:
```
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.3.stable.official (77dcf97d82cbfe4e4615475fa52ca03da645dbd8)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x45320) [0x7e4ba2645320] (??:0)
-- END OF BACKTRACE --
================================================================
```

### Minimal reproduction project (MRP)

[bugproject.zip](https://github.com/user-attachments/files/16933423/bugproject.zip)
Repository: tensorflow
Issue: Wheels have different metadata on different platforms
Labels: stat:awaiting tensorflower,type:build/install,subtype:cpu-intel,TF 2.15

Hi! Some resolvers in Python such as poetry and uv try to create lockfiles from the user's requirements that work an any platform. For example, you could create a universal lockfile on linux and use it to install the project on windows.

For this, both poetry and uv read the `METADATA` file of a single wheel on the index (in this case, pypi) and assume its metadata applies to all other platforms, too. For tensorflow, there is currently different metadata for windows and for linux/mac. For windows, the `requires-dist` excluding the cuda packages is:

```
Requires-Dist: tensorflow-macos ==2.15.1 ; platform_system == "Darwin" and platform_machine == "arm64"
Requires-Dist: tensorflow-cpu-aws ==2.15.1 ; platform_system == "Linux" and (platform_machine == "arm64" or platform_machine == "aarch64")
Requires-Dist: tensorflow-intel ==2.15.1 ; platform_system == "Windows"
```

While for linux and mac it is:

```
Requires-Dist: absl-py (>=1.0.0)
Requires-Dist: astunparse (>=1.6.0)
Requires-Dist: flatbuffers (>=23.5.26)
Requires-Dist: gast (!=0.5.0,!=0.5.1,!=0.5.2,>=0.2.1)
Requires-Dist: google-pasta (>=0.1.1)
Requires-Dist: h5py (>=2.9.0)
Requires-Dist: libclang (>=13.0.0)
Requires-Dist: ml-dtypes (~=0.3.1)
Requires-Dist: numpy (<2.0.0,>=1.23.5)
Requires-Dist: opt-einsum (>=2.3.2)
Requires-Dist: packaging
Requires-Dist: protobuf (!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.20.3)
Requires-Dist: setuptools
Requires-Dist: six (>=1.12.0)
Requires-Dist: termcolor (>=1.1.0)
Requires-Dist: typing-extensions (>=3.6.6)
Requires-Dist: wrapt (<1.15,>=1.11.0)
Requires-Dist: tensorflow-io-gcs-filesystem (>=0.23.1)
Requires-Dist: grpcio (<2.0,>=1.24.3)
Requires-Dist: tensorboard (<2.16,>=2.15)
Requires-Dist: tensorflow-estimator (<2.16,>=2.15.0)
Requires-Dist: keras (<2.16,>=2.15.0)
```

That means depending on whether we read a windows wheel or a unix wheel, we get a different lockfile.

Would it be possible for tensorflow to write the same METADATA for all platforms and gate the platform specific entries with `platform_system` markers?

For uv, we've considered reading the METADATA files for all wheels, but this has major drawbacks: We have to make 17 network requests for pypi instead of 1 for each version we try, slowing resolution down. There is also no perfect mapping between environment markers (which usually tell us which dependencies to install on which platform) and wheel tags, so when METADATA can be different between wheels we'd also have to capture this in lockfiles.

I hope I explained good enough why identical METADATA files across all wheels of a version are important for us, I can add more details about how the resolver works if you have more questions.

This is similar to the problem discussed at https://github.com/tensorflow/tensorflow/issues/62346#issuecomment-1798633528.
Repository: vscode
Issue: Expose Walkthrough Media in Accessible view.
Labels: feature-request,getting-started

> @meganrogge for walkthroughs steps which include markdown, should we consider exposing the markdown content in the accessible view also? 

 _Originally posted by @bhavyaus in [#226642](https://github.com/microsoft/vscode/issues/226642#issuecomment-2332487868)_


For: Image and SVG, expose ALT text in the accessible view.
For Markdown, expose contents of markdown in accessible view.
Repository: kubernetes
Issue: Standardize a label to exclude Pods from Node drain
Labels: sig/node,kind/feature,sig/cli,sig/architecture,needs-triage

### What would you like to be added?

I would like to have a standardized annotation to exclude Pods from Node drains.

This annotation should be implement by kubectl drain, but other tools like e.g. Cluster API would also be able to implement this annotation.


### Context

Today there is no standard way to exclude Pods from `kubectl drain`.

There is a set of Pods that are already excluded today:
* Pods belonging to an existing DaemonSet (orphaned DaemonSet Pods are evicted as well)
* Mirror Pods, i.e. Pods with the `kubernetes.io/config.mirror` annotation (usually static Pods managed by kubelet, like kube-apiserver)

So basically the best available option to exclude a Pod from drain would be adding the `kubernetes.io/config.mirror` annotation. But this is pretty bad (and also has unknown side effects).

Would it be possible to support an annotation like e.g. `node.kubernetes.io/exclude-from-drain`
Repository: vscode
Issue: Editor goes berserk and start scrolling on mouse movements
Labels: bug,editor-scrollbar

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.93.0
- OS Version: Manjaro Linux

Steps to Reproduce:

1. Use VSCode for many many consecutive hours (I have no idea what triggers the issue)

Sometimes, randomly, the IDE seems to go completely berserk and it will start "following" the mouse cursor with scrolling.
Meaning that when I move the mouse cursor up, the editor will scroll up, when I move the mouse cursor down, the editor will scroll down. A dotted non-blinking caret is visible at all times at the end of the line at whose height the mouse cursor is; this is besides the normal blinking text cursor.

With this, the IDE becomes completely unusable.

Restarting stops this madness.
Repository: ui
Issue: [bug]: new CLI default tailwind config
Labels: bug

### Describe the bug

Here for center the value has to be true in boolean but after new CLI installation it is adding inn string format like below.

![image](https://github.com/user-attachments/assets/3ae172ea-b488-48ea-8cc5-0bdb6f888ab8)


### Affected component/components

tailwind.config.ts

### How to reproduce

pnpm dlx shadcn@latest init

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Arc browser
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Collapsible functions in merge editor views
Labels: feature-request,merge-editor

<!-- ⚠️⚠️ 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. -->
I think that it'd be helpful to be able to collapse functions in the merge editor views

![image](https://github.com/user-attachments/assets/c5a51c93-dd89-44d1-a96c-f9cead14def5)

In the same way that you can collapse functions in the regular editor window

<img width="586" alt="image" src="https://github.com/user-attachments/assets/2d193993-f9d5-43a5-b83a-264aad040dd6">
Repository: rust
Issue: Improve impl Trait 2024 capture rules compiler output
Labels: A-diagnostics,T-compiler

### Code

```Rust
struct Foo;

impl Foo {
    fn get(&self) -> impl Sized {
        ()
    }

    fn mutate(&mut self) {}
}

fn bar(_: impl Sized) {}

fn test() {
    let mut foo = Foo;

    let x = foo.get();
    foo.mutate();
    bar(x);
}
```


### Current output

```Shell
Compiling example v0.1.0 (/tmp/example)
error[E0502]: cannot borrow `foo` as mutable because it is also borrowed as immutable
  --> src/main.rs:19:5
   |
18 |     let x = foo.get();
   |             --- immutable borrow occurs here
19 |     foo.mutate();
   |     ^^^^^^^^^^^^ mutable borrow occurs here
20 |     bar(x);
   |         - immutable borrow later used here

For more information about this error, try `rustc --explain E0502`.
error: could not compile `example` (bin "example") due to 1 previous error
```


### Desired output

I can't produce nice looking example, but to put it simply I would like a `note` section that would point to the definition of `Foo::get` and pointed that `impl Sized` implicitly captured `&self`. And another note could point out that if this is unwanted, then I could add `+ use<>` bound to disable capturing of this lifetime.


### Rationale and extra context

Firstly, if this is already tracked then I'm sorry for posting a duplicate. I don't know how to grep for that kind of issues.

I was playing with new impl Trait capture rules and have written an invalid example, that fails to compile. In function `Foo::get` returned opaque type `impl Sized` captures lifetime of `&self`. However compiler error is not as helpful, as it could be. It points to the error on the call side, but does not show an additional context on the declaration site.

I have no idea how easy or how hard this reasoning would be to implement, but this surely would be helpful information. Especially that this code compiles in Edition 2021.

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.83.0-nightly (9c01301c5 2024-09-05)
binary: rustc
commit-hash: 9c01301c52df5d2d7b6fe337707a74e011d68d6f
commit-date: 2024-09-05
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
```


### Anything else?

_No response_
Repository: neovim
Issue: [remote ui] termguicolors not checked on first remote TUI attach
Labels: bug,ui,channels-rpc,ui-extensibility,remote

### Problem

Starting a headless nvim instance, then attaching to it with `--remote-ui --server` bypasses the `termguicolors` check in `_defaults.lua`, causing the TUI to display with reduced colors unless `termguicolors` is manually set.

### Steps to reproduce

nvim --headless --listen /tmp/nvim.sock -u NORC
(switch to another terminal)
nvim --remote-ui --server /tmp/nvim.sock


### Expected behavior

Ideally, `termguicolors` would be handled per-TUI client, but this seems like a herculean effort for not much payoff.

However, I do think the *first* TUI to attach should maybe try to determine the initial value of `termguicolors`. Though that may run counter to the not that long ago decision to move the `termguicolors` check from Neovim core code to `_defaults.lua`.

This is very much a nitpick, so feel free to close with wontfix, though it might be good to track a list of remote-ui 'caveats' somewhere.

### Neovim version (nvim -v)

NVIM v0.11.0-dev-738+g2aa64df0d

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

N/A

### Operating system/version

Arch Linux

### Terminal name/version

wezterm

### $TERM environment variable

xterm-256color

### Installation

Build from repo